# What does the HTTP 429 status code mean?

> HTTP 429 Too Many Requests means the user has sent too many requests in a given amount of time, which RFC 6585 calls rate limiting.

*A 429 response may include a Retry-After header that tells the client how long to wait, as a date or a number of seconds, before it makes a new request.*

- Type: Explainer
- Section: Tech
- By: Tech Desk
- Published: 2026-11-13T05:45:48-05:00
- Updated: 2026-11-13T05:45:48-05:00
- Checked: 2026-11-13T05:45:35-05:00
- URL: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/

## Key facts

- HTTP 429 Too Many Requests means the user has sent too many requests in a given amount of time, which RFC 6585 calls rate limiting. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc6585.html). Confirmed 2026-11-13T05:45:08-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/#http-429-too-many-requests-means-the-user-has-sent-too-many
- RFC 6585 says a 429 response should explain the condition and may include a Retry-After header indicating how long to wait before making a new request. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc6585.html). Confirmed 2026-11-13T05:45:08-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/#rfc-6585-says-a-429-response-should-explain-the-condition
- RFC 6585 says responses with the 429 status code must not be stored by a cache. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc6585.html). Confirmed 2026-11-13T05:45:08-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/#rfc-6585-says-responses-with-the-429-status-code-must-not-be
- RFC 9110 says a Retry-After value can be either an HTTP-date or a number of seconds to delay after receiving the response. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-13T05:45:09-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/#rfc-9110-says-a-retry-after-value-can-be-either-an-http-date
- The IANA HTTP Status Code Registry lists code 429 with the description Too Many Requests and the reference RFC 6585. Source: [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml). Confirmed 2026-11-13T05:45:35-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/#the-iana-http-status-code-registry-lists-code-429-with-the

The HTTP 429 (Too Many Requests) status code means that the user has sent too many requests in a given amount of time, which [RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html), the IETF standard that defines the code, calls rate limiting. In the words of [Section 4 of RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4), "The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting")."

## What a 429 response should contain

[RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) says the response representations should include details explaining the condition, and may include a Retry-After header indicating how long to wait before making a new request. Its own example response carries the header `Retry-After: 3600` and a page that tells the user the site allows 50 requests per hour per logged in user.

A 429 is a client error. The [4xx (Client Error) class in RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-client-error-4xx) indicates that the client seems to have erred, and except when responding to a HEAD request, the server should send a representation explaining the error situation and whether it is a temporary or permanent condition.

## How the Retry-After header works with a 429

[Section 10.2.3 of RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-retry-after) says servers send the Retry-After header field to indicate how long the user agent ought to wait before making a follow-up request, and that its value can be either an HTTP-date or a number of seconds to delay after receiving the response. The two forms look like this:

| Form | Example | How to read it |
| --- | --- | --- |
| Seconds | 3600 (the RFC 6585 example) | Wait 3,600 seconds, or one hour, after receiving the response |
| Seconds | 120 (an RFC 9110 example) | Wait 120 seconds, which RFC 9110 calls 2 minutes |
| HTTP-date | Fri, 31 Dec 1999 23:59:59 GMT (an RFC 9110 example) | Wait until that moment, in UTC |

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-retry-after) says a delay-seconds value is a non-negative decimal integer, and its [date and time section](https://www.rfc-editor.org/rfc/rfc9110.html#name-date-time-formats) says an HTTP-date value represents time in Coordinated Universal Time (UTC). The header is optional on a 429: [RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) says the response "MAY" include it.

## How the server counts requests is up to the server

[RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) does not define how the origin server identifies the user, nor how it counts requests. It gives examples: a server can count requests per resource, across the entire server, or even among a set of servers, and it might identify the user by authentication credentials or by a stateful cookie.

## A server does not have to send 429

The [security considerations of RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-7.2) say that when a server is under attack or receiving a very large number of requests from a single party, answering each one with a 429 consumes resources. So servers are not required to use the code, and when limiting resource usage it may be more appropriate to just drop connections or take other steps. The [introduction to RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-1) also says its status codes are optional and servers cannot be required to support them.

## How 429 compares with 503, 413 and 431

Other codes also come up when a server limits what it will accept. This table summarizes each definition and what it says about Retry-After.

| Code | What its definition says | Retry-After in the definition |
| --- | --- | --- |
| 429 Too Many Requests | The user has sent too many requests in a given amount of time | The response may include it |
| 503 Service Unavailable | The server cannot handle the request now because of a temporary overload or scheduled maintenance | The server may send it |
| 413 Content Too Large | The request content is larger than the server is willing or able to process | The server should send it if the condition is temporary |
| 431 Request Header Fields Too Large | The request's header fields are too large | Not named |

The 429 and 431 rows come from [Sections 4](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) and [5 of RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-5), the 503 row from [Section 15.6.4 of RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-503-service-unavailable) and the 413 row from [Section 15.5.14 of RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-413-content-too-large). The codes sit in different classes: [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes) puts 4xx codes such as 429, 413 and 431 in the Client Error class and 5xx codes such as 503 in the Server Error class. A separate page explains [503 Service Unavailable](/tech/what-does-the-http-503-status-code-mean/).

## What happens when a client does not know 429

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes) says a client must understand the class of any status code, as shown by its first digit, and treat an unrecognized code as equivalent to the x00 code of that class. An older client that does not know 429 therefore handles it as a [400 Bad Request](/tech/what-does-the-http-400-status-code-mean/). The [introduction to RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-1) relied on the same rule, saying clients treat unknown codes as a generic error of the same class, so the new codes can be safely deployed by existing servers.

## Can a 429 be cached?

No. [RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) says responses with the 429 status code must not be stored by a cache, and it sets the same rule for 428, 431 and 511.

## What changed and when

[RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html) was published in April 2012 as a Standards Track document that updates RFC 2616, and it added four codes: 428 Precondition Required, 429 Too Many Requests, 431 Request Header Fields Too Large and 511 Network Authentication Required. Its introduction says the codes were added to improve interoperability and avoid confusion when other, less precise status codes are used. [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), published in June 2022 on the Standards Track, obsoletes RFC 7231 and is now where Retry-After is defined, in Section 10.2.3; it does not define 429 itself and points to RFC 6585 for additional status codes related to capacity limits. The [IANA registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) lists 429 Too Many Requests with the reference RFC 6585 and shows its last update as September 15, 2025.

## Sources

1. [RFC 6585: Additional HTTP Status Codes](https://www.rfc-editor.org/rfc/rfc6585.html), RFC Editor (Internet Engineering Task Force), 2012-04 (primary source)
2. [RFC 9110: HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110.html), RFC Editor (Internet Engineering Task Force), 2022-06 (primary source)
3. [Hypertext Transfer Protocol (HTTP) Status Code Registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml), Internet Assigned Numbers Authority (IANA), 2025-09-15 (primary source)

## Asked next

- [Cloudflare makes Kitesurf, its browser engine for AI agents, open source under Apache 2.0](https://factsdesk.com/tech/cloudflare-kitesurf/): Cloudflare made Kitesurf, its browser for AI agents that runs on Workers, open source on Nov. 13, 2026, under the Apache 2.0 license.
- [What does the HTTP 503 status code mean?](https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/): HTTP 503 Service Unavailable means the server cannot handle the request now due to a temporary overload or scheduled maintenance, under RFC 9110.
- [What does the HTTP 400 status code mean?](https://factsdesk.com/tech/what-does-the-http-400-status-code-mean/): HTTP 400 Bad Request means the server cannot or will not process a request because of something it perceives to be a client error, under RFC 9110.
- [What does the HTTP 403 status code mean?](https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/): HTTP 403 Forbidden means the server understood the request but refuses to fulfill it, as defined in RFC 9110, the HTTP Semantics standard.
- [What does the HTTP 504 status code mean?](https://factsdesk.com/tech/what-does-the-http-504-status-code-mean/): HTTP 504 Gateway Timeout means a server acting as a gateway or proxy did not get a timely response from an upstream server, under RFC 9110.
- [What does the HTTP 502 status code mean?](https://factsdesk.com/tech/what-does-the-http-502-status-code-mean/): HTTP 502 Bad Gateway means a server acting as a gateway or proxy received an invalid response from an inbound server, under RFC 9110.
