Amplitude 429 Throttling Errors

Share
Workaround available Web, server Updated November 13, 2026Based on 2 user reportsHow we research

Quick answer

429 errors appear in the Ingestion Monitor when request volume per second spikes. Batch events, lower replay sample rate or ask Support to raise the threshold.

Most likely fix: Reduce request rate

How to fix it

Try these in order — the most common fix is first.

  1. 1. Reduce request rate

    1. Lower the Session Replay sample rate
    2. Increase batch size and flush interval
    Did this fix it?
  2. 2. Ask Support

    1. Contact Amplitude Support before a planned spike to adjust the throttle threshold
    Did this fix it?

Symptoms

Dropped or delayed events and short replays during traffic peaks.

Why it happens

  • Traffic or campaign spike
  • High Session Replay sample rate
  • Many small requests

This guide also covers

  • amplitude 429 error
  • amplitude throttling
  • amplitude rate limit

Still not working?

If Amplitude keeps failing, you're not alone. See every Amplitude problem users report or the alternatives people switch to.

Done fighting Amplitude? Our small team builds your own Amplitude alternative, or any software you need: web, mobile, games, desktop. Price agreed together.

Talk to us
Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Amplitude errors