The target site, or a rate limiter in front of it.

429 — Too Many Requests

You have exceeded a request quota. The counter is usually per IP, sometimes per account or per API key, and a Retry-After header often tells you exactly how long the door stays shut.

A proxy fixes this. When the limit is per IP — which it usually is for anonymous traffic — spreading requests across a rotating pool is the direct fix. Confirm the key first: a per-account limit is untouched by any number of IPs.

Get residential IPs →Web Unblocker

Why it happens

Too many requests per second from one address.

A burst that was fine on average but exceeded a short-window limit — many limiters count per second, not per minute.

The limit is per account rather than per IP, in which case rotating addresses changes nothing.

Shared infrastructure: someone else on the same datacenter range spent the quota first.

How to fix it

  1. Honour Retry-After if it is present. Ignoring it turns a temporary limit into a longer block on most platforms.
  2. Spread the load across IPs so no single address exceeds the per-address budget.
  3. Add jitter. Perfectly even request spacing is itself a bot signal, and it also synchronises your retries into new bursts.
  4. Check whether the limit is keyed to your account. If it is, more IPs will not help and you need a higher tier or fewer calls.

FAQ

What does 429 mean?›
You have exceeded a request quota. The counter is usually per IP, sometimes per account or per API key, and a Retry-After header often tells you exactly how long the door stays shut. The target site, or a rate limiter in front of it.
Why am I getting 429?›
Too many requests per second from one address. A burst that was fine on average but exceeded a short-window limit — many limiters count per second, not per minute. The limit is per account rather than per IP, in which case rotating addresses changes nothing. Shared infrastructure: someone else on the same datacenter range spent the quota first.
How do I fix 429?›
Honour Retry-After if it is present. Ignoring it turns a temporary limit into a longer block on most platforms. Spread the load across IPs so no single address exceeds the per-address budget. Add jitter. Perfectly even request spacing is itself a bot signal, and it also synchronises your retries into new bursts. Check whether the limit is keyed to your account. If it is, more IPs will not help and you need a higher tier or fewer calls.
Will a proxy fix 429?›
When the limit is per IP — which it usually is for anonymous traffic — spreading requests across a rotating pool is the direct fix. Confirm the key first: a per-account limit is untouched by any number of IPs.

Going deeper

How to get past this block →Let the Unblocker handle it

Other errors

407403401502503504400408451405413421

Stop getting 429

Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.

Get residential IPs →