The short answer
A timeout is your software giving up. You set (or inherit) a limit such as 30 seconds; if the proxy cannot connect, or the site does not finish answering, in that time, the request fails.
Common causes and fixes
- Slow or far-away IP: pick a proxy location closer to the target website.
- Home device went offline (rotating residential): retry with a new IP.
- Too many parallel requests on one proxy: lower concurrency.
- Timeout too short: 10 to 30 seconds is typical for residential; datacenter can be tighter.

Also known as
Connection timed out, read timeout, gateway timeout (HTTP 504).
Learn more
- Common proxy errors
- Proxy speed test
- Sneaker proxy speed
- What does 502 Bad Gateway mean?
- RFC 9293, TCP
- RFC 9110, HTTP semantics (status 504)
- Python's urllib.request (timeouts and proxies)
- The curl manual (--connect-timeout, --max-time)
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.