A rate limit decided you have sent too many requests too quickly. It is the server protecting itself — from bots, from scrapers, or from a script of your own — and it usually says how long to wait. For a site owner, the question is whether the limit is catching the right traffic.
429 Too Many Requests nginx
How 2 other clients word the same error
Apache
Too Many Requests The user has sent too many requests in a given amount of time.
curl -I
HTTP/2 429
| Error | 429 Too Many Requests |
| Usually fixed by | Either side |
| Status | 429 (RFC 6585 §4) |
| Retry-After | Seconds, or a date, to wait before trying again |
| Treats 429 as a server error and slows its crawling |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
A 429 answers “too many requests in a given amount of time”. It may carry a Retry-After header saying when to try again. Google treats it like a 5xx error: it crawls the site more slowly, and pages that keep answering 429 for days can be dropped from its index.
Why it happens
- A rate limit in the web server, a security plugin, the host or the CDN, reached by a bot, a scraper, or a burst of real traffic.
- A limit set too low for pages that load many resources at once.
- A script or integration of your own calling an API faster than it allows.
How to fix it
- Find which layer sends it: the response headers (server, Retry-After) and the logs of the server, the plugin and the CDN.
- Set limits for the traffic you mean to stop — login pages, search, bots — rather than for every page.
- Let known crawlers through, and for your own scripts, wait the Retry-After time and back off between retries.
If you are visiting the site
- Wait a minute before reloading. On a shared network or a VPN, other people’s requests may count against the same address.
See it for yourself
curl -sI https://example.com/ | grep -iE '^HTTP|retry-after|server'
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 6585 — rfc-editor.org
- How HTTP Status Codes Affect Google’s Crawlers — developers.google.com
- Module ngx_http_limit_req_module — nginx.org