What Does HTTP Status 429 Mean? (Too Many Requests)
What HTTP 429 (Too Many Requests) Means In Plain English
A 429 status (Too Many Requests) means the server is rate-limiting requests because a threshold was exceeded.
If you want the broader context across all status code families, use the full HTTP Status Codes Guide (2xx, 3xx, 4xx, 5xx).
Quick Navigation
- What HTTP 429 (Too Many Requests) Means In Plain English
- How to Read HTTP 429 in WebsiteDown Results
- Most Common Root Causes
- What to Do Next
- What to Avoid During Triage
- Real-World Examples
- HTTP 429 FAQ
How to Read HTTP 429 in WebsiteDown Results
In checker results, 429 means the site is up but limiting traffic. This can happen during bursts, bot filtering, or defensive controls during incidents.
If you see this code only in one region, compare with official provider status and retest from another network. Mixed regional results often indicate routing, policy, or edge differences rather than full global outages.
For deeper triage, compare this with the HTTP 403 guide, HTTP 503 guide, and the false-positive monitoring guide.
Most Common Root Causes
- Client or bot traffic exceeds API/site request limits.
- Global protective throttles during traffic spikes.
- Missing caching causes avoidable request storms.
- Retry loops amplify load and trigger stricter limiting.
What to Do Next
- Respect `Retry-After` when present and apply exponential backoff.
- Identify noisy clients and reduce unnecessary polling.
- Add caching and request coalescing on hot endpoints.
- Tune rate-limit policies by endpoint and user class.
What to Avoid During Triage
- Do not brute-force retries against 429 responses.
- Do not disable all limits globally without abuse safeguards.
Real-World Examples
- Example: API clients polling every second trigger platform-wide 429.
- Example: scripted retries after 5xx convert brief outage into persistent rate limiting.