Plain-language meaning
What HTTP code 429 means
RFC 6585 defines HTTP 429 as a response for too many requests in a given amount of time. The response may include a Retry-After header indicating how long to wait before making another request. RFC 6585 says the response representation should explain the condition, and it notes that a server is not obligated to use 429 at all — it may instead drop connections when defending against a request flood.
Keep the code in its namespace
What this code does—and does not—tell you
A 429 describes request rate, not a permanent account ban. The response may explain the limit, and the server is not required to include a retry time. RFC 6585 also states that 429 responses may be stored by a cache under the usual HTTP caching rules, so a repeated 429 can be served from cache rather than reflecting a fresh rate check.
Conservative next step
Where to check next
Check the response for Retry-After and honor the service's documented rate limit. If you are a regular visitor, stop repeated refreshes and retry later; if you maintain the client, reduce request frequency rather than trying to evade the limit.
Primary source
Read the official reference
This explanation is scoped to the linked IETF / RFC Editor material, checked September 28, 2026. The original source takes priority and may change its instructions.
RFC 6585, Section 4: 429 Too Many RequestsSame code system
More HTTP error codes
403 error code: HTTP Forbidden
The HTTP 403 Forbidden status means the server understood the request but refuses to fulfill it; the status alone may not explain why.
Read this code guide HTTP · 500500 error code: internal server error
HTTP 500 Internal Server Error is a general server response for an unexpected condition; it does not name a specific cause.
Read this code guide HTTP · 503503 error code: service unavailable
HTTP 503 Service Unavailable means a server is temporarily unable to handle a request, such as during overload or scheduled maintenance.
Read this code guide