Skip to content
OSULZER.AT

Is my website down?

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.

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.

  1. Wait a moment

    A 429 is temporary. After a few minutes, or the time given in Retry-After, the site should respond again.

  2. 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.

  3. 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.

  4. Allow your own services

    Add monitoring, your own integrations and office locations as trusted so they aren't throttled.

  5. 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.

  6. 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.

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

4xx: Client errors

5xx: Server errors

No status code: connection errors

New project?

Contact.

Tell me briefly about your project - I'll get back to you personally.

Your data is used solely to handle your inquiry. More in the privacy policy.