| Previous | Next |
| HTTP_STATUS_PRECONDITION_REQUIRED | HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2 |
HTTP_STATUS_TOO_MANY_REQUESTS
The limit may apply to an account, IP address, token, endpoint, or shared resource. A response can include Retry-After, but its absence does not mean immediate repeated retries are safe.
Implement bounded backoff, honor documented quotas, and avoid concurrent retry storms. Server logs or rate-limit headers are needed to identify the exact scope of the limit.
RFC 6585: Additional HTTP Status Codes
Operational meaning of HTTP 429 for HTTP_STATUS_TOO_MANY_REQUESTS
HTTP 429 (HTTP_STATUS_TOO_MANY_REQUESTS) is a client-error response. AllStat records its meaning as “429 Too Many Requests”. For HTTP_STATUS_TOO_MANY_REQUESTS, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_TOO_MANY_REQUESTS
- Treat HTTP_STATUS_TOO_MANY_REQUESTS as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_TOO_MANY_REQUESTS, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_TOO_MANY_REQUESTS, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 429, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.