# amplitude event dropped exceeds quota 429 error

## TL;DR
The 429 means Amplitude is refusing volume: quota exceeded or rate limited. Check usage versus plan in Amplitude's settings, find the noisiest events in the data table, and cut or sample the low-value ones. Add batching and exponential backoff on 429 in the client, and upgrade or request a quota increase only for legitimate volume.

```text
amplitude event dropped exceeds quota 429 error
```

## Use this when

- Amplitude returns 429 and events are dropped
- Usage dashboard shows the project at or over quota
- Drops spike during deploys or traffic surges

## Not for this skill when

- 400 invalid API key errors (authentication, not quota)
- Events rejected for schema or property issues (different error)
- Events missing in charts but no 429 in sight (check filters first)

## Steps

### Step 1: Check quota usage

Open Amplitude's settings and compare current event or MTU usage against the plan limit. Expected: you know exactly how far over quota the project is.

### Step 2: Find the noisiest events

Use the data table or governance views to rank events by volume. Expected: a short list of high-volume, low-value events to cut.

### Step 3: Cut or sample noisy events

Drop debug and redundant events, and sample high-frequency ones. Expected: daily volume falls well under quota.

### Step 4: Add backoff on 429

Implement client-side batching and exponential backoff when Amplitude returns 429. Expected: bursts degrade gracefully instead of dropping everything.

### Step 5: Right-size the plan

If the remaining volume is legitimate product telemetry, upgrade the plan or request a quota increase. Expected: quota covers real usage with headroom.

## Tool compatibility

Amplitude analytics (HTTP API and SDKs); Amplitude project settings and usage dashboards; event governance views.

## Variant phrasings

### Variant 1

amplitude 429 too many requests events dropped

### Variant 2

amplitude event quota exceeded what to do

### Variant 3

amplitude rate limit 429 backoff

## Why it happens

Amplitude enforces quotas because event ingestion is metered infrastructure, and the 429 is the enforcement signal. Teams usually arrive here through accidental volume: a duplicated SDK initialization double-firing every event, a development build pointed at production, or a well-meaning engineer tracking every mouse move. The quota error then looks like an Amplitude outage, but the provider is correctly refusing to ingest more than the plan allows. Cutting volume is the real fix; upgrading without cutting just buys time until the same growth hits the next tier. Backoff matters because even under quota, burst spikes get rate limited.

## Edge cases / pitfalls

- Duplicate SDK initialization is the most common accidental multiplier; audit for double init.
- Development and staging traffic counts against quota; route it to a separate project.
- Sampling must be documented per event or analysts will misread the resulting numbers.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_UXFIywz_lEi_Cv5M1f8xzA