Error 429: Too Many Requests
Is a limit slowing your site down? Check right here whether it responds normally from the outside or returns 429.
Checks the status code, every redirect, the variants with and without www and over http and https, the SSL certificate and the response time.
Free, no sign-up - no data about you is stored.
Result
Technical finding without guarantee. The check runs once from a server in Germany. If your website is only unreachable from certain networks or countries, the result may differ.
What does Error 429 mean?
A 429 Too Many Requests means too many requests came from this address or program in a short time, and the server temporarily won't accept more. It's a protective measure, not a crash. Often the server includes a Retry-After header saying how many seconds to wait.
It's meant to stop bots, scrapers and attacks that flood a site with requests. If it hits regular visitors, search engines or your own services like uptime monitoring and APIs, the limit is too strict or set up wrong.
Common causes.
Server rate limit
Web servers and hosts limit requests per IP address and time window. Loading lots of pages quickly in a row runs into it.
Bot protection and CDN
Cloudflare, security plugins and firewalls throttle traffic that looks automated. Tools and crawlers then get 429 too.
Login brute-force protection
Many login attempts in a short time trigger a block, often with 429 or 403.
Shared IP address
In company networks, schools or VPNs, lots of people share one IP address. To the server it looks like a single, very busy visitor.
Limits of external services
If your website calls an external API too often, for reviews, maps or payments, that API responds with 429. Your site then shows errors or empty sections.
With WordPress and hosting.
On WordPress, 429s often come from security plugins with rate limiting or from the host throttling aggressive traffic to wp-login.php, xmlrpc.php or search. Page builders and shops also send many background requests to admin-ajax.php or the REST API. With several dashboard tabs open, that can trip a limit.
With Cloudflare, rate limiting rules and bot protection are the usual sources. The security events log shows which rule fired. And the other way round: if a plugin schedules lots of tasks at once, like image compression or syncs, your site may hit the limits of external services.
How to fix it.
Wait a moment
A 429 is temporary. After a few minutes, or the time given in
Retry-After, the site should respond again.Check from the outside
If the checker above returns 200, the limit only affects you or your network. If it returns 429, others are hit too.
Find the source of the limit
Look in your security plugin, hosting panel and Cloudflare, if you use it, for rate limiting rules and blocked addresses.
Allow your own services
Add monitoring, your own integrations and office locations as trusted so they aren't throttled.
Adjust limits instead of disabling them
Loosen an overly strict limit specifically for the affected areas, such as search or the shop. Turning it off entirely leaves the site more exposed to attacks.
Make fewer calls to external services
If the 429s come from a third-party API, caching results and spreading scheduled tasks over a longer period helps.
Impact on Google.
Google treats 429 like a server error: Googlebot crawls the site more slowly. Briefly, that is no problem and even a legitimate way to reduce load. But if Google gets nothing but 429 for a longer period, more than a day or two, it may drop the affected URLs from its index.
If you use bot protection, make sure verified search engine bots are excluded. The crawl stats in Search Console show whether Google has been throttled.
Help from a developer
I can take care of it.
The check shows where things go wrong. I am happy to fix it, once or on an ongoing basis.
Good to know
Questions about Error 429?
The most common questions, answered briefly.
Questions about Error 429
How long does a 429 block last?
That depends on the limit, usually seconds to a few minutes. If the response includes Retry-After, that sets the wait time. Blocks after failed logins can last hours.
Is 429 the same as DDoS protection?
It's one part of it. Rate limiting slows down individual senders. Large, distributed attacks also need protection in front of the server, for example a CDN.
Does a 429 hurt my rankings?
Not in the short term, Google just crawls more slowly. If it lasts for days, Google may remove pages from the index.
All status codes at a glance.
2xx: Success
- 200OKAll good: the server understood the request and delivers the page.
- 201CreatedThe request succeeded and created something new, for example a record via an API.
- 204No ContentSuccessful, but the response has no body. Typical for APIs and background requests, not for regular pages.
3xx: Redirects
- 301Moved PermanentlyPermanent redirect: the page now lives at a new address. Search engines switch to the new URL.Causes and fixes →
- 302FoundTemporary redirect: the page is currently available at another address, the original URL stays valid.Causes and fixes →
- 303See OtherRedirect to another page that is fetched with GET, typically after submitting a form.
- 304Not ModifiedThe page has not changed since the last visit, so the browser uses its cached copy. Not an error.
- 307Temporary RedirectTemporary redirect like 302, but the request method (such as POST) is guaranteed to stay the same.
- 308Permanent RedirectPermanent redirect like 301, but the request method (such as POST) is guaranteed to stay the same.
4xx: Client errors
- 400Bad RequestThe server can't process the request because it is malformed, for example due to oversized cookies or a broken URL.Causes and fixes →
- 401UnauthorizedThis page requires you to log in, for example via server-side password protection. No valid credentials, no access.Causes and fixes →
- 403ForbiddenThe server understood the request but refuses access, for example because of file permissions, a firewall or a block.Causes and fixes →
- 404Not FoundThere is no page at this address. It was deleted, moved, or the URL is misspelled.Causes and fixes →
- 405Method Not AllowedThe address exists but doesn't accept this kind of request, such as a POST where only GET is allowed.
- 408Request TimeoutThe server waited too long for the complete request and closed the connection, often on a slow connection.
- 410GoneThe page was removed deliberately and permanently and won't come back. A clearer signal than 404.Causes and fixes →
- 429Too Many RequestsToo many requests in a short time: a rate limit or bot protection is temporarily slowing down access.
- 451Unavailable For Legal ReasonsThe page is blocked for legal reasons, for example by an official order or a country block.
5xx: Server errors
- 500Internal Server ErrorGeneric server error: something went wrong while building the page. With WordPress it is usually a plugin, theme or PHP issue.Causes and fixes →
- 501Not ImplementedThe server doesn't know or support the request method. Rare on regular websites.
- 502Bad GatewayA server in front (proxy, nginx, CDN) didn't get a usable response from the actual server, often because PHP crashed.Causes and fixes →
- 503Service UnavailableThe server is temporarily unavailable due to maintenance or overload. Try again later.Causes and fixes →
- 504Gateway TimeoutA server in front waited too long for the actual server to respond and gave up.Causes and fixes →
- 520Web Server Returned an Unknown ErrorCloudflare error: the server behind Cloudflare sent an empty, invalid or unexpected response.
- 521Web Server Is DownCloudflare error: the server behind Cloudflare refuses the connection, so it is down or blocking Cloudflare.
- 522Connection Timed OutCloudflare error: Cloudflare couldn't establish a connection to the server behind it in time.
- 523Origin Is UnreachableCloudflare error: the server behind it can't be reached, often because of a wrong IP address in the DNS records at Cloudflare.
- 524A Timeout OccurredCloudflare error: the connection to the server works, but it didn't respond in time (100 seconds by default).
- 525SSL Handshake FailedCloudflare error: the encrypted connection between Cloudflare and the server behind it could not be established.
- 526Invalid SSL CertificateCloudflare error: the SSL certificate on the server behind Cloudflare is invalid or expired (with SSL mode "Full (strict)").
No status code: connection errors
- ×Server not found (DNS)There is no server for this domain: it has expired, is misconfigured, or the record with the IP address is missing.Causes and fixes →
- ×Connection refusedThe server is known but doesn't accept connections. The web server isn't running or a firewall is blocking.
- ×TimeoutThe server didn't answer in time. It is overloaded, stuck, or not reachable at all.
- ×Certificate error (SSL)The SSL certificate has expired, doesn't cover this domain, or the certificate chain is incomplete. Browsers show a warning.Causes and fixes →

