A 429 is the target rate-limiting the requesting IP. On a shared pool many users share that budget; on a dedicated endpoint you own the budget, so pacing and backoff solve it.

Rate limits and 429s

Fix 429 Too Many Requests behind a proxy

Quick answer

HTTP 429 means the target site limited requests from the address you are using. Through a proxy, the limit applies to the proxy address - which on a shared rotating pool is a budget strangers spend for you.

Exact error text
Likely causes ranked
Ordered diagnostics
Verified remedy

When this is the right fit

  • Exact error text
  • Likely causes ranked
  • Ordered diagnostics

Who this page is for

Fix 429 Too Many Requests behind a proxy

HTTP 429 means the target site limited requests from the address you are using. Through a proxy, the limit applies to the proxy address - which on a shared rotating pool is a budget strangers spend for you.

Diagnosis tree

429 storms on a rotating pool

Likely causes

  • - Pool-mates exhausted the address's request budget
  • - The same addresses recycle to many users

Verified remedy

Move the workflow to a dedicated static endpoint. The address budget becomes yours alone, and pacing controls it deterministically.

429 on your own dedicated endpoint

Likely causes

  • - Your request rate exceeds the target's threshold
  • - Retry storms amplify the limit window

Verified remedy

Cut concurrency, add exponential backoff honoring the Retry-After header, and resume at the highest rate that holds. Keep the endpoint stable so the target's limit history ages out cleanly.

429 only on one target site

Likely causes

  • - Site-specific limit tuned tighter than others

Verified remedy

Schedule that target's work in its own window with a lower rate. Do not change endpoints to escape a limit you control with pacing.

Final connection check

  1. 1Stop the task loop
  2. 2Read Retry-After from the 429 response
  3. 3Wait at least that long
  4. 4Resume at half the previous rate and increase slowly

Working connection

Requests complete without 429 while the endpoint stays unchanged.

Broken connection

If 429 persists at minimal rates on a dedicated endpoint, the address has inherited a bad reputation: retest from a fresh endpoint and record the incident.

Sources

Facts last reviewed 2026-09-01.

Prevent it recurring

Set per-target rate budgets, honor Retry-After always, and keep one endpoint per profile so limits age out per identity instead of mixing histories.

195+ countries
99.9% uptime guarantee
Unlimited bandwidth
4.9/5 from 127 ratings

Frequently asked questions

Why do I get 429 through a proxy?

The target limits the proxy address, not your device. On shared pools the address's budget is spent by everyone using it; on dedicated endpoints the budget is yours.

Does a dedicated static proxy stop 429 errors?

It makes them controllable: only your traffic shapes the address's reputation, so pacing and backoff work as intended.

Choose one stable proxy for every active profile

Buy self-serve now, or talk with us about a larger agency inventory.