Client error · 429

429 Too Many Requests

A 429 Too Many Requests means a limit on this client, this IP, or this API key has been used up. The server is deliberately refusing more work for a while. It is not a crash.

HTTP status codes explained · the longer reference on the blog.

What 429 means

The response should tell the caller when to try again. A Retry-After header, in seconds or as an HTTP date, is the standard way. Some APIs put the same information in a JSON body or in X-RateLimit-Remaining. When those are missing, the only safe move is to slow down.

Two different people see this code. A visitor or API client is calling too fast. Or your own uptime check is the traffic that tripped a very tight limit. Those need different fixes. Slowing the monitor down does not help real users who are already being limited, and speeding a monitor up can create a 429 that users never see.

Common causes

  • A real client exceeded the published limit

    A script without a backoff, a mobile app that retries in a tight loop, or a shared NAT where many users exit from one IP. The limit is doing its job.

  • The limit is tighter than real traffic

    A CDN rate rule, an API gateway plan, or a WordPress security plugin set to a handful of requests per minute. Normal browsing, especially with assets on the same host, can trip it.

  • Retries amplified a short failure

    A 500 caused clients to retry immediately, the retry storm tripped the limiter, and the public status became 429. The original fault is hidden under the limit.

  • A monitor or health check is counted

    The homepage checker allows 5 checks per hour from one network, which is our limit, not yours. Your server has its own limit. A monitor on a 5-minute schedule sends about 288 GETs a day to that one URL. A limit of one request per minute will 429 that monitor.

How to fix it

  • Honor Retry-After

    Wait at least as long as the header says, then retry once. Tight retry loops are how a limit becomes an outage for that client.

  • Find which key or IP is limited

    Gateway logs name the bucket: IP, API key, or user. A single runaway job is a different fix from a limit that is too low for all users.

  • Raise the limit only to match legitimate traffic

    Count a normal page view, including assets, before you change the number. Keep a limit in place. Removing it hides abuse and does not fix a retry storm.

  • Give monitors a path that is allowed

    If the public page must stay strict, exempt a /health URL or lengthen the monitor interval. Free monitors can run every 10 minutes or slower, up to every 12 hours. Use a slower interval when the endpoint asks you to.

Is it your site, or just you?

Load the page in a private window on cellular data. If that works and your office IP is limited, the site is up and that IP is in cooldown. If every network gets 429, visitors are being turned away.

The homepage checker uses a different IP from your browser. If it reports 429 as well, the limit is broad. If it reports 200, your browser or IP is the one being limited. The checker’s own hourly cap returns an error from ismysiteup, not a 429 from your site.

How to monitor for 429

Expect 200 on a URL that should serve visitors. A 429 then alerts you that real checks are being refused. If only the monitor is limited, lengthen its interval so you stop adding to the bucket, and confirm from a browser before you treat the site as down. Do not point extra checks at an endpoint that is already returning 429.

The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.

Compare Free, Pro, and Business

Related status codes

FAQ

Is 429 an outage?

The process is up and choosing to refuse. For the people who are limited, the site is unusable until the window resets or the limit changes. For everyone else, it can look healthy.

What should I do with Retry-After?

Wait that long before you try again. If the header is missing, wait and reduce the call rate. Hammering the URL keeps the limit open.

Will ismysiteup keep requesting a URL that returns 429?

A monitor keeps its schedule. Slow the interval if your server is rate-limiting the check. The free plan’s fastest interval is 5 minutes. The separate homepage checker stops after 5 checks an hour from the same network.