HTTP 429 Too Many Requests

Client error code, RFC 6585

What it means

You sent too many requests in a given time. The server limits how fast you may go.

A real response

This is the request and the answer our test server gave when we asked it to return 429.

GET /c/429 HTTP/1.1
Host: example.com

HTTP/1.1 429 Too Many Requests
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Retry-After: 120
Content-Length: 11

<p>demo</p>

If you run the site

RFC 6585 defines this code for rate limiting and says the response may include Retry-After; it also says such responses must not be stored by a cache. Say in the body what the limit is. Clients should wait the number of seconds in Retry-After, then try again, and slow down.

If you are a visitor

Wait a few minutes and try again. If it keeps happening, you may be using a program or extension that sends many requests.

A common mistake

Retrying immediately in a loop, which makes the limit last longer.

Registered in the IANA HTTP Status Code Registry as Too Many Requests, defined in RFC 6585.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.