Networks · Residential
Residential proxies: how the pool behaves and how to work with it.
Household IPs from consumer ISPs in 199 countries, rotating or sticky, billed per GB from $2.45 with no expiry.
At a glance#
- Endpoint
res.proxshift.comon 9000 (HTTP/HTTPS) and 9001 (SOCKS5)- Exits
- Real devices on consumer connections, with the owner's consent, in 199 countries
- Rotation
- A new exit on every new connection, or one exit held with
-sid-for up to 24 hours - Targeting
- Country everywhere, US state, city where listed, ASN
- Billing
- Per GB at the tier of the purchase, from $2.45 to $0.95; traffic never expires
- Concurrency
- Unlimited connections and sessions
How the pool works#
Each request enters the gateway, which selects a device matching your parameters and relays the connection through it. The target sees the device's address, its ISP and its city. Devices join and leave the pool as their owners connect and disconnect, which is why a sticky session can end before its lifetime and why very narrow targeting sometimes finds nobody online.
Rotation and sticky sessions#
The default is rotation: every new connection to the gateway gets a different exit. Add -sid- to hold one exit and -ttl- to say for how long (default 10 minutes, maximum 24 hours). Multi-step flows such as search then paginate, or login then act, belong on a sticky session; independent fetches belong on rotation. Details and examples on Targeting & sessions.
Targeting levels#
| Level | Parameter | Coverage | Typical use |
|---|---|---|---|
| Country | -cc- | 199 countries | Localized content, geo-blocks, per-market pricing |
| State | -state- | United States only | State-specific pricing, compliance and ads |
| City | -city- | Where the country page lists cities | Local SERPs, store availability, delivery rules |
| Provider | -asn- | Any AS with devices online | Reproducing a given ISP's audience, provider-level tests |
What you pay for#
Metered traffic is every byte that crosses the gateway in both directions: request and response, headers and TLS records included. Connections that fail before reaching the target are not billed. The rate is set by the size of the purchase: 100 GB bought at once cost $1.54 per GB, and that rate applies to the whole purchase. Traffic stays on the account until used; there is no monthly reset. The full ladder is on Wallet & billing.
Performance expectations#
- Throughput is that of a household line: fine for pages, APIs and media, below a wired datacenter link for bulk transfer. Give clients a connect timeout of at least 10 seconds and a read timeout of 30.
- Latency includes the hop to the device. Expect a few hundred milliseconds more than a direct request, more for distant countries.
- A small share of connections fail because a device went offline mid-request. Retry once on a connection error or a
502; with rotation the retry already uses a different exit.
Best practices#
- Match the exit to the market: scrape the German store from
-cc-de, not from a nearby country. - Keep sticky sessions as short as the flow needs. Long lifetimes lower success rates because devices come and go.
- Pace per domain. There is no cap on your side, and a polite request rate keeps the pool clean for everyone, including your next job.
- Block images, fonts and trackers in headless browsers; HTML is a small fraction of a page and you pay per GB.
- Use the country pages to check the cities and providers available before you narrow a job.