ISP proxy
A datacentre-hosted address registered to a consumer ISP. Datacentre speed with residential registration, billed per IP.
An ISP proxy — sometimes called a static residential proxy — is hosted on datacentre infrastructure but uses an address registered to a consumer internet provider. It is a deliberate hybrid.
#What the hybrid buys you
| Property | Behaves like |
|---|---|
| Speed and uptime | Datacenter |
| Network registration | Residential |
| Billing | Per address per month, not per gigabyte |
| Address stability | Static — the same address every time |
#When it is the right choice
Work that needs a consistent identity over time: maintaining a logged-in session, managing an account, or any task where an address that changes every request would itself look wrong. Because billing is per address rather than per gigabyte, ISP proxies also suit high-bandwidth work that would be expensive on a residential plan.
#The limitation
Volume. A residential pool can offer very large numbers of addresses; an ISP allocation is a fixed list you are renting, and burning those addresses through careless use is expensive.
#The two properties it combines
| Property | Comes from | Effect |
|---|---|---|
| Registration to a consumer ISP | The address allocation | Classified like a home line |
| Hosting in a datacentre | The physical location | Short, stable network path |
| Exclusive assignment | The purchase model | No inherited history from other users |
The third row is the one people overlook. Because the address is yours alone, its reputation reflects only your own traffic. That makes behaviour the variable you can actually control.
#Where the hybrid stops working
An ISP proxy gives you a small number of stable addresses. That is the opposite of what wide crawling needs. If the work requires many distinct addresses, or addresses in many places, the model does not stretch; a residential pool does. Use ISP addresses where you need the same identity to persist, and residential where you need breadth.