CheckWebsiteNow

Client errors (4xx)

429 Too Many Requests

Too many requests were sent in a short time.

Quick answer

A 429 means the website limits how often it can be asked (rate limiting). It is online but wants you to slow down. The response may say how long to wait.

When to wait: Usually yes: wait a few minutes up to an hour, then try once.

If you are visiting the website

  1. Stop reloading Each new try can count as another request and restart the limit. Leave the page alone for a moment.
  2. Wait before trying again Wait a few minutes, then try once. If the page says how long to wait, follow that time.
  3. Close extra tabs and auto-refresh tools Many open tabs of the same site, auto-refresh extensions or download managers can send lots of requests in the background. Close them, then wait.
  4. Switch network If you share an office, school or public network with many people, the limit may count all of you together. Try another connection, such as mobile data instead of Wi-Fi.
  5. Turn off your VPN briefly A VPN (a service that routes your traffic through its own servers) shares one address among many users. Test once without it, then turn it back on.
  6. Slow down apps and scripts If you use an app, script or API (an interface for programs), lower its request rate. Respect the Retry-After header and wait longer after each failure.
  7. Contact the site if it lasts If you stay blocked for hours while browsing normally, contact the site with the time and address. Your network may be caught by a limit meant for bots.

If you run the website

  1. Review your rate limits Compare your limits with real visitor behaviour, such as pages per minute during a normal visit. Make sure real people are not blocked by limits meant for bots.
  2. Send a Retry-After header Add Retry-After with a number of seconds (for example Retry-After: 120) or an HTTP date. Well-behaved clients and crawlers wait that long before trying again.
  3. Count by more than the IP address Offices, schools and mobile carriers put many people behind one address. Where possible, limit per account or session as well as per IP address.
  4. Remember crawlers and monitors Google treats 429 as a sign of server overload and slows its crawling. Make sure your own uptime monitors are not counted against tight limits.
  5. Show a clear message Explain in plain words that too many requests arrived and when the visitor can try again. A bare error code leaves people guessing.

Is the website down?

No. A 429 comes from a working server that wants you to slow down. It is a speed limit, not an outage.

The limit may count only your device, or everyone on your network or VPN.

How 429 differs from 403 and 503

A 403 is a refusal that waiting does not fix. A 429 is about speed, so it usually clears after a pause.

A 503 means the whole server is too busy or in maintenance for everyone. A 429 targets the requests from one source.

For developers: handling 429 in code

Read the Retry-After header if it is present and wait that long. If it is missing, wait longer after each failed try (exponential backoff) and add a little randomness.

Never retry in a tight loop. That keeps the limit active and can lead to a longer block.

Common questions

How long does a 429 block last?

It depends on the site. Many limits reset after minutes, some after an hour or a day. A Retry-After value in the response is the site's own answer.

Did I do something wrong?

Usually not. Shared networks, VPNs, extensions or a very busy page can push you over the limit without you noticing.

Will clearing cookies fix a 429?

Usually not, because many limits count your network address. Waiting is the reliable fix.

Should I switch VPN servers to get past the limit?

No. Changing addresses to dodge a limit can break the site's rules and lead to a harder block. Wait, or contact the site.

Likely causes

  • Common Many requests came from the same network address, for example a shared office or VPN. (Your side)
  • Common The site has strict limits against bots. (Website side)
  • Sometimes An app or script repeats requests too fast. (Either side)

What to avoid

  • Do not keep reloading; it can make the block last longer.

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: