429 Too Many Requests
Rate limited. Send Retry-After, and clients: honour it with backoff.
429Client error
- What it means
- Rate limited. Send Retry-After, and clients: honour it with backoff.
- In practice
- You hit a rate limit. The fix is pacing, not retrying harder: honour the Retry-After header when present, and back off exponentially when it is not — hammering a 429 usually extends the ban. If you run the server, include Retry-After and scope limits so one busy client cannot exhaust another’s budget (an expensive lesson; ask this site’s logo tool).
- Whose problem is it?
- The request. Retrying it unchanged will get the same answer.