429 Too Many Requests — Causes & Fix
HTTP 429 (Too Many Requests) means the client has sent too many requests in a given time — you have hit a rate limit.
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include exceeding an API rate limit, aggressive scraping/refreshing, or shared-IP traffic tripping a limit. HTTP status 429 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "429 Too Many Requests"
- Access blocked temporarily; a Retry-After header may be present
How to fix it
- 1
Slow down and wait
1. As a user: wait a bit and retry — respect any "Retry-After" time.
- 2
Back off (developers)
1. Implement exponential backoff and honour the Retry-After header. 2. Cache responses to reduce request volume.
Frequently asked questions
How long until 429 clears?
Usually a short cooldown — check the "Retry-After" header if present. Reduce your request rate to avoid tripping the limit again.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.