Rotating residential proxies that don't get blocked.

Every request through a proxy user with sticky switched off leaves from a different IP in the pool. There's nothing to schedule and no rotation interval to configure — send a thousand requests and they exit from a thousand addresses. Turning sticky on adds a sessid token that pins one exit until the session expires.

Rotating gives you a new IP per request, which is what you want for crawling, monitoring and anything you can run in parallel. Sticky holds one IP for a set duration so a login, a cart or a multi-step form doesn't break halfway through. Sticky sessions last up to 30 minutes, set on a slider in your client area. For anything longer, you want a static ISP proxy instead.

Targeting is set on the proxy user and encoded in the username it generates. A country-wide user reads customer-yourID-cc-US; narrowing to a city gives you customer-yourID-city-washington. Pick the country first, then choose one narrowing rule — city, state or ISP, depending on what's offered for that country. Every plan includes every level.

HTTP and HTTPS. SOCKS5 isn't supported on the residential network — it's something we're working on. Note that the residential endpoint runs on port 7777, which isn't a SOCKS port despite what the number might suggest elsewhere: point an ordinary HTTP proxy client at it. If your tool needs SOCKS5 specifically, our ISP and dedicated IPs support it.

It's the share of requests across the network returning a 2xx response, measured over a rolling 30 days. Failures caused by the target site or by the client — malformed requests, a site that's down, a URL that 404s — are excluded, so the figure measures the proxy layer and nothing else.

Yes. It's a standard HTTP proxy with username and password authentication, so anything that accepts a proxy URL works without an SDK or wrapper library — Scrapy, Selenium, Puppeteer, Playwright, Octoparse, Multilogin, GoLogin and the rest. There are copy-paste examples for Python, Node, cURL, Scrapy and Puppeteer further up this page.

As many as your infrastructure can open. There's no thread cap, no connection limit and no throttle that kicks in at a usage threshold — and that's true on Starter, not just on Pro. Bandwidth is the only thing your plan meters.

You're billed on total bytes through the proxy, request and response together, including images, fonts, scripts and anything else the page pulls. The biggest saving is usually blocking media and stylesheets in a headless browser, since a page that renders in 2 MB often carries under 100 KB of the HTML you actually parse. Requesting APIs directly rather than rendering pages saves more again.

City and ISP assignments come from the IP registry data the target sites themselves rely on, so what you select is what a geolocation lookup reports. Where a city has thin coverage at a given moment you may get an exit elsewhere in the same country rather than a failed request — worth checking against a lookup service on your first run if street-level accuracy matters to the job.

Almost always something above the IP layer. Check that your headers and TLS fingerprint look like a real browser, that you're not hitting the site faster than a person could, and that you're not reusing one sticky session across requests that should look independent — a residential IP behaving like a bot still reads as a bot. If the target is a major social platform, residential may be the wrong tool — mobile proxies carry a higher trust score. Support will look at the actual failures with you.

Slower than a datacenter IP, and faster than most people expect. Every exit is a real home connection, so latency depends on that household's line and how far it sits from your target — any provider quoting one number is averaging over a lot of variance. In practice, what decides how long a job takes isn't per-request latency, it's how many requests you have to send twice. If you need guaranteed throughput on a fixed address, static ISP proxies run up to 1 Gbps.

Every IP belongs to a real device whose owner opted in and is compensated for sharing bandwidth, under GDPR-aligned agreements. Using proxies to collect publicly available data is legal in most jurisdictions; what you do with them is on you. Our terms prohibit fraud, unauthorised access and anything that would breach a site's own terms of service.

Rotating residential for collecting data at volume across many locations. Static ISP when one account needs the same IP for weeks or months. Mobile for the hardest targets, where carrier IPs carry the highest trust of any type. There's a full comparison further up this page, and if you're unsure, ask us before you buy rather than after.