Smart Home & Tech
HTTP 429 Too Many Requests: What It Means and How to Fix It
Wait for Retry-After, then try once. Stop scripts. Do not restart the router to fetch a new address.
HTTP 429 means the server applied a rate limit to this request. It may count by account, credential, address, resource, or another rule; the status alone does not identify which limit fired. The server is telling you to slow down. It is defined as a rate limit, not as a broken page. Wait. Do not refresh in a burst, and do not change networks to fetch a new address so the limit misses you. A login failure is 401. A refusal of one page is 403. A server that is overloaded for everyone is often 503. Those are not invitations to try harder.
Step 1: Wait as long as the page asks
- If the page or the response says how long to wait, wait at least that long. A Retry-After value is that instruction. It may be a number of seconds or a time.
- If nothing tells you a duration, wait a few minutes. This guide will not pretend there is one official pause. Then try the action once.
- Close extra tabs that keep reloading the same site. A tab that refreshes itself counts.
Step 2: Stop anything you automated
If a script, a browser extension, or a download tool is hitting the site, stop it. The limit may be per account, per key, or per address. Read the site’s own limit page if you were using their API on purpose. Follow that page. Do not add extra clients, extra keys, or a pool of addresses to stay under the radar. That is how a normal integration becomes abuse. A shopping page you refreshed twenty times is the same idea at a smaller scale: one try after the wait.
Do not clear every cookie as the fix. A new sign-in is another burst of requests. Clear site data only if the site’s own help says a bad session is retrying in the background, and only for that site.
Step 3: A shared network is not a puzzle to evade
An office, a school, or a VPN exit can share one public address. Other people may have used up the limit. Waiting still works. Restarting the router to obtain a new address, switching to a phone hotspot, or turning a VPN off and on until the 429 disappears is an attempt to dodge the limit. Do not do that. If the limit blocks real work on a shared office line, tell the site what you were doing and the time. They can see a shared address in their logs. You do not need to hide it.
A personal VPN you use for privacy can be left on. Disconnecting it once tells you whether that exit is the crowded one, but only so you can report it. Turn it back on. Do not shop for a quieter exit country.
Step 4: One extension check
A tool that prefetches every link can create the traffic that tripped the limit. In a private window, which usually has extensions off, open the site once after you have waited. If that single load works, disable the prefetch or shopping extension in the normal window and leave it off for this site. Do not install a second tool that claims to bypass rate limits.
Step 5: If one careful try still fails
You waited, you stopped the script, and one reload still returns 429. Stop. The window may be longer than a few minutes, or the account may be blocked until support clears it. Contact the site with the time and what you clicked. Do not rotate addresses while you wait for them. If you operate an app that calls their API, their dashboard is the place to read the quota. Header names vary by vendor. This page will not list a set of headers to spoof.
What you should be able to point at
- Any Retry-After instruction followed, or a few quiet minutes if none was shown.
- One retry, not a burst. Auto-refresh tabs closed.
- Scripts and download tools stopped.
- No router restart, hotspot, or new VPN region used to get a clean address.
- No bypass tool installed.
Example: the product page that was refreshed
A shopper refreshes a product page again and again during a sale and gets 429. They close the extra tabs, wait the two minutes the page names, and load it once. The page opens. They do not reboot the router and they do not switch the laptop to a phone hotspot. A script that was checking stock every second would have been stopped first. Waiting would not have helped while the script kept running.
Related guides
Last updated: October 28, 2026
Last reviewed October 22, 2026. Suggest a correction
Questions readers ask
Can I get a new IP address and continue?
No. The limit is the site’s rule. Changing address to step around it is not a fix this guide will describe.
Is 429 the same as the site being down?
No. The server is up and refusing more requests from this client for a while. A 503 is the code that more often means the service cannot handle traffic at all.
I did not click that many times.
A shared address, a prefetch extension, or a tab left refreshing can spend the budget. Stop those, wait, and try once.
Should I clear cookies?
Not as the first step. It can force a new login and more requests. Wait first.
I am building an app and I keep seeing 429.
Stop the loop, honor Retry-After, and follow the provider’s published quota. Do not add keys or machines to multiply the limit.
Sources and methodology
Claims that depend on an outside authority are tied to the references below. Product details change. Confirm the current specification sheet before you buy or install anything.
- RFC 6585: 429 Too Many Requests — RFC Editor (standard), accessed October 28, 2026. Primary HTTP or DNS specification for the status or response behavior discussed in this article.
- MDN: 429 Too Many Requests — Mozilla Developer Network (documentation), accessed October 28, 2026. Technical explanation of this HTTP response status and its normal meaning.
- RFC 9110: Retry-After — RFC Editor (standard), accessed October 28, 2026. Primary HTTP or DNS specification for the status or response behavior discussed in this article.
Information on this site is for general educational purposes and is not professional advice.
Parent topic: Smart Home & Tech