My requests are blocked or I see a CAPTCHA
The proxy works; the site's anti-bot rules reacted to how your scraper behaves.
Checked against the product on October 16, 2026
A 403, a 429 or a CAPTCHA means the request went through the proxy and the target site decided it looks automated. These changes help most.
Keep one IP for a flow
A new IP on every request looks odd to sites that expect one visitor. Add -session-<id> to the username to keep one IP for logins, pagination and other multi-step flows. Session docs.
Send realistic headers
Send the User-Agent of a current Chrome or Firefox, never your HTTP library's default, and set Accept-Language and Referer as a browser would.
Slow down
Add a random pause of a few seconds between requests. A high request rate is the fastest way to get blocked.
Try another location
Some sites are stricter with some countries. Try -country-<code> near the site's own market.
Use mobile IPs for the hardest sites
Social platforms and travel sites trust mobile IPs most. Create a mobile proxy for those targets.
We do not solve CAPTCHAs. Residential and mobile IPs make them appear less often.
Related articles
Still have a question?
Talk directly to the engineers who built the product. No chatbots, no first-level support scripts.