Residential, ISP or datacenter: picking the line for the job
Updated 2 min read
Residential is coming soon and cannot be ordered yet. ISP and datacenter are on sale now; the residential column below shows how it works.
Pick by what the target checks, not by price. If it accepts server traffic, datacenter is enough. If it scores traffic by network type and you want breadth, use residential. If the address itself has to stay the same, use ISP.
| Residential | ISP | Datacenter | |
|---|---|---|---|
Where the IP lives |
Consumer home connections |
Registered to a consumer provider, hosted on servers |
Hosting networks |
Does it change? |
Rotates: the pool picks each exit |
Static for the term you buy |
Static for the term you buy |
Location choice |
None: exits come from the whole pool |
Country, region and city where stock allows, plus the provider by name |
Country, region and city where stock allows |
Billed |
Per GB of traffic |
Per IP, for a term |
Per IP, for a term |
Smallest order |
One gigabyte |
One IP |
One IP |
Quick rules
- Wide collection at volume (catalogues, marketplaces, search results): residential, once it opens.
- Logins, allowlists on partner systems, sessions that last hours: ISP.
- Uptime checks, internal tools, APIs that allowlist your address, tolerant targets: datacenter.
- A job that must leave from a named country or city: ISP or datacenter. Residential has no location selection.
- The target starts challenging your datacenter IPs: move the job to ISP.
Not sure? Start small: a single static IP is a complete order, so you can point it at your real targets before committing to volume. The free proxy checker shows how a target sees the address you are using.
Each line has its own page with the details: Residential proxies: rotating IPs, billed by the gigabyte, ISP proxies: static IPs on a carrier you name, Datacenter proxies: fixed addresses for tolerant targets. Prices for each are on the pricing page.