The short answer
429 is the website saying "slow down". You have sent more requests than its rate limit allows from your IP, account or session. It may include a Retry-After header telling you how many seconds to wait.
What to do
- Wait and retry with exponential backoff, and honour
Retry-After. - Lower concurrency. Fewer parallel requests per IP.
- Spread the load across rotating proxies so no single IP crosses the limit.
- Cache pages you already have instead of fetching them again.

Also known as
Rate limited, throttled, HTTP 429, too many requests error.
Learn more
- Rate limiting and proxies
- How to avoid IP bans when scraping
- What is rate limiting?
- What is a rotating proxy?
- RFC 6585, which defines 429
- MDN on 429 Too Many Requests
- MDN on the Retry-After header
- The SEC's fair-access rules for automated EDGAR requests
Affiliate disclosure: Team of Monkeys is an affiliate of Geonode, Webshare and Rayobyte. Links and banners marked as sponsored, and links to Geonode, Webshare and Rayobyte in the text, use our referral links, and we may earn a commission if you buy through them, at no extra cost to you. Our explanations and comparisons are written to be useful whichever provider you choose.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.