ISP Proxy

An ISP proxy — also sold as a static residential proxy — is an IP address registered to a consumer internet provider but hosted on datacenter hardware. Websites look it up and see a residential ISP; the connection itself runs at server speed and never changes.

It is the deliberate middle of the market. Residential proxies have trust but are slow and rotate. Datacenter proxies are fast and stable but transparently not homes. An ISP proxy takes the useful half of each.

What actually makes an address "residential"

Nothing physical. Every address belongs to a block registered to an organisation and identified by an ASN, and anti-bot systems check that registration in milliseconds. An address registered to Verizon reads as a household; one registered to a hosting company reads as a server. Where the machine physically sits is not part of the check.

ISP proxies exploit precisely that gap. The provider obtains addresses registered to an ISP, then announces and hosts them from its own infrastructure. The lookup returns "Verizon" while the packets come from a rack.

Where the addresses come from

Providers either lease IPv4 blocks directly from internet service providers or hold their own ranges registered through an ISP relationship. Both are ordinary commercial arrangements — no household is involved and no bandwidth-sharing app is required, which is why ISP pools sidestep the sourcing questions that follow residential networks.

It also explains the pricing. Supply is capped by how many ISP-registered blocks a provider can secure, so these are sold per address per month rather than per gigabyte.

Static is the entire point

The address does not change until you cancel it. That sounds unremarkable until you need it, and then nothing else will do.

• Account management — a platform that sees the same account arrive from the same address every day treats it as a normal user. The same account arriving from a new country every hour does not survive long.
• Long sessions — no mid-task rotation to invalidate a login or empty a basket.
• IP whitelisting — you can register the address with an API or a partner, which is simply impossible with a rotating pool.
• Unmetered bandwidth — most ISP plans include generous or unlimited traffic, so heavy pages do not inflate the bill.

The limits worth knowing before you buy

Pools are small. A provider may hold a few hundred thousand ISP addresses against tens of millions of residential ones, and the geographic choice is correspondingly narrow — typically the US, the UK, and a handful of European countries.

Those addresses also cluster. Buy ten and you may receive ten consecutive IPs inside one /24, which defeats the purpose against a site that blocks by range: a single flagged address takes its neighbours with it. Ask for subnet diversity explicitly if you are buying more than a few.

And because each address is yours alone and unchanging, its reputation is entirely your own doing. A residential address you burn is rotated away within minutes. An ISP address you burn is the one you keep paying for every month.

Choosing between the three

• ISP — one identity, held long term, on a trusted address. Accounts, whitelisted APIs, long sessions.
• Residential — many identities, high trust, rotating, billed by traffic. Volume work against protected targets.
• Datacenter — many identities, low trust, fast and cheap. Volume work against permissive targets.

A useful rule: if the task has a name and a password attached to it, you want ISP. If it has a row count attached to it, you probably want one of the other two.