Definition
HTTP 429 Too Many Requests means the client has sent too many requests within a period defined by the responding service. The response asks the client to reduce its request rate and may include Retry-After.
The limit may identify more than an IP
MDN notes that rate limiting can apply at different scopes, including a resource or server, and may identify users or authorized applications as well as client addresses. A 429 therefore does not establish that changing a proxy exit will remove the limit.
In a path containing a forward proxy and destination infrastructure, identify which service returned the response before choosing an action. Account limits at a proxy and resource limits at a destination are different policies.
Read the wait instruction
A Retry-After field may indicate how long to wait before making another request. Its presence provides retry guidance, not a promise that all later requests will succeed. If it is absent, consult the service’s documented rate policy and use a bounded delay strategy.
For an illustrative client sending a tight loop of requests, the useful correction is to slow that loop and control parallel work. Simply increasing worker count or rapidly retrying multiplies the load that triggered the response.
Preserve a valid workload
Count retries alongside initial attempts. Coordinate limits across workers when they share an account or destination budget. Otherwise, each worker can appear locally conservative while their combined traffic exceeds the service’s allowance.
Do not use proxy rotation as a substitute for permission to exceed a limit. Resume only within the permitted workload and verify the returned content. An HTTP 200 after a wait should still be checked against the actual task’s success criteria.
Sources
Sources checked on November 18, 2026. Examples are illustrative, not measurements of a live proxy service.
Related concepts
Frequently asked questions
Is a 429 always an IP-based limit?
No. Limits can be associated with users, applications, resources, or broader service scope.
Is Retry-After always present?
No. It may be included. If absent, consult the service’s documented policy and avoid immediate repeated requests.
Should I add more concurrent workers after a 429?
No. Reduce pressure and coordinate the permitted rate; more workers can make the problem worse.