Skip to the content

429 Too Many Requests

You have sent more requests in a given time than the server allows. A Retry-After header, if present, says how long to wait.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 6585

What it looks like

HTTP/1.1 429 Too Many Requests
Retry-After: 60

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When a rate limit is exceeded: too many API calls a minute for your key, too many login attempts, a script that fetches pages faster than the site likes. Limits can count per key, per account or per IP address, so on a shared network the traffic of someone else can use up the allowance.

What to do about it

Stop and wait. If there is a Retry-After header, wait at least that long. Without one, wait a little and double the wait after every further 429. Trying again at once makes it worse and can get a key or an address blocked.

Then lower your rate: cache answers, ask for more items per request, spread the work out. Many APIs report the limit, and what is left of it, in headers of every response.

Not to be confused with

503 Service UnavailableThe server as a whole is overloaded, whoever is asking.
403 ForbiddenBlocked outright, not for a limited time.

How Google treats it

Google treats a 429 like a server error: its crawler slows down, and pages that keep returning it are dropped from the index in the end.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12