Error 429 "Too Many Requests": what it means and how to fix it
"429 Too Many Requests" means a website or app received more requests from you than it allows in a short time, and is asking you to slow down. The site isn't down and nothing is broken: you've hit a rate limit. It usually clears by itself within minutes. Here's why it happens, how to get past it as a visitor, and how to handle it if you're building an app or running the site.
What error 429 means
429 is a standard HTTP status code, defined in RFC 6585, that servers use for rate limiting: capping how many requests one visitor can make in a given window, such as 60 per minute. The limit is usually tied to your IP address, or to your account or API key if you're signed in.
The response often includes a Retry-After header telling you how long to wait, either as a number of seconds (for example Retry-After: 120) or as a date and time. Websites use rate limits to protect themselves from bots, password-guessing attacks, scrapers and overload, which keeps the site fast for everyone else.
Because the server is answering, CheckIfSiteDown will show the site as Up: a 429 is about your requests, not the site's health.
Why you're seeing it
- Refreshing or retrying a lot, for example during a ticket sale, a sneaker drop or when a page loads slowly.
- Too many login or password-reset attempts in a row.
- A shared IP address. On a VPN, at school or work, on public Wi-Fi, or on mobile networks that share addresses between customers, other people's requests count against the same limit as yours.
- Browser extensions or tabs that auto-refresh, prefetch or scrape pages in the background.
- Busy AI tools, social apps and game launchers that limit how many messages, posts or requests you can make per hour.
- Scripts and apps calling an API faster than its plan allows.
How to fix error 429 as a visitor
- Stop refreshing and wait. Most limits reset within a minute to an hour. Every extra refresh can restart the clock, so give it a proper break. If the page shows how long to wait, wait that long.
- Close duplicate tabs of the same site, and pause extensions that auto-refresh or prefetch pages.
- Sign out and back in, or clear that site's cookies, if the error started after many login attempts.
- Switch networks. If you're on a VPN, turn it off; if you're on shared Wi-Fi, try mobile data. A fresh IP address isn't sharing a limit with anyone else. (On a VPN, switching to a different server can do the same.)
- Check whether it's a usage cap. Some services limit free accounts to a number of actions per hour or day; the error page or help centre will say so, and the only fix is waiting or upgrading.
If none of that helps and the error lasts for hours, the site may have flagged your IP by mistake. Contact its support and mention the time and your network.
If your app or script gets 429s
- Honour
Retry-After. If the response includes it, wait at least that long before the next request. - Back off exponentially, with jitter. Without a
Retry-After, wait 1 second, then 2, 4, 8 and so on, adding a little randomness so many clients don't retry at the same moment. Retrying instantly in a loop makes the problem worse and can get you blocked for longer. - Read the rate-limit headers. Many APIs send headers such as
X-RateLimit-RemainingandX-RateLimit-Reset(or the newerRateLimitheaders), so you can slow down before hitting the limit. - Make fewer requests: cache responses you've already fetched, batch calls where the API allows it, and queue background jobs instead of firing them all at once.
- Check your plan. Higher API tiers usually come with higher limits.
If your own visitors are hitting 429s
Rate limits are healthy, but limits that catch real people cost you visitors. Review your rules in your firewall, CDN or server configuration: allow more requests for pages people reload often, set separate limits for logged-in users, make sure legitimate search-engine crawlers aren't throttled, and always send a Retry-After header so browsers and apps know when to come back.
429 vs 403 vs 503
| Code | What it's telling you |
|---|---|
| 429 Too Many Requests | "Slow down." Temporary, and about how often you are making requests. |
| 403 Forbidden | "You're not allowed." Usually permission, location or bot protection, and waiting won't fix it. |
| 503 Service Unavailable | "We're overloaded or in maintenance." The problem is the site, for everyone. See 502 vs 503 vs 504. |
More codes are explained in our HTTP status codes guide.
The short version
Error 429 means you've made too many requests too quickly. Stop refreshing, wait a few minutes (or as long as Retry-After says), close extra tabs, and try another network if you're on a VPN or shared Wi-Fi. If you're writing code, respect Retry-After and back off exponentially. The site itself is up the whole time.