Published 2026-10-06
Proxy errors 407, 403 and 429
Three status codes explain most failed proxy requests. Each points to a different place to look.
407: the proxy rejected you
The proxy wants credentials and did not accept the ones sent. Check the username, password, host and port, and whether your source address needs to be allowlisted. The request did not reach the target.
403: the target rejected the address
The target understood the request and refused it. That often means it recognised the address range, for example a hosting range, or the request looked automated. Try a different line, slower requests or realistic headers.
429: too many requests
You reached a rate limit on one address. Slow down, add a delay between retries, and spread requests over more addresses. On metered traffic, immediate retries add cost.
Which of these cost money
On metered traffic any response body that crosses the proxy counts. A 403 or 429 page is smaller than the real page, but it is not free. Count retries in your estimate.
Frequently asked questions
Is a 403 always a proxy problem?
No. It can be a rule on the target’s side that has nothing to do with the proxy. Test the same request from your own connection.
Try it for $5
Minimum top-up is $5. Run your own target through it before you scale.