DeviceFarm
Glossary
Proxies & network

ISP proxy

Also called: static residential proxy, static resi

An ISP proxy is an IP address registered to a consumer internet provider but hosted in a datacenter. It combines the residential registration that makes an address look ordinary with the stability and speed of server infrastructure, and it is normally sold per IP rather than per gigabyte.

ISP proxies exist because the two properties people want usually come apart. Residential addresses look right but come from consumer devices that go offline. Datacenter addresses are fast and always up but announce their hosting origin. An ISP proxy is an address an internet provider has registered as residential, operated on hardware that never sleeps.

How the address keeps its residential registration

Two arrangements produce them. A proxy provider leases a block from an internet provider and announces it from its own network, leaving the registry record naming the ISP. Or the ISP itself sells static blocks to hosting customers and keeps them registered under its own organisation. In both cases the WHOIS org says consumer ISP while the route is announced by an autonomous system that belongs to a hosting network.

That gap is the weak point, and it is checkable. Look up the WHOIS organisation, then look up the origin AS actually announcing the prefix in the global routing table. When the registered holder and the announcing network disagree, the address is an ISP proxy and any classifier comparing the two can label it. Providers who lease from the ISP and let the ISP announce the route do not have this discrepancy, which is a real quality difference between two products sold under the same name.

What you get

  • A fixed address you keep for as long as you pay for it — no rotation to manage.
  • Datacenter-grade speed and uptime, without the residential pool’s variability.
  • Flat per-IP pricing — commonly a few dollars per address per month at the time of writing — which makes cost predictable regardless of traffic volume.
  • Full session control, because nothing changes underneath you mid-task.

Subnet clustering, the mistake nobody sees coming

Bulk ISP addresses are allocated contiguously. Order a hundred and you are likely to receive a hundred sequential addresses inside one or two /24 blocks. A hundred accounts on a hundred consecutive addresses is a cluster that surfaces the moment anyone sorts by IP — the accounts are individually clean and collectively obvious. Treat a /24 as a single unit of reputation: split purchases across providers, autonomous systems and countries, and never let one subnet carry more accounts than a single household plausibly would.

The limitation

The address is static, so it accumulates history in both directions. That is exactly what you want for an account meant to live in one place for months — and exactly what you do not want once the address picks up a bad reputation, since you cannot walk away from it the way you can from a rotating pool. Availability is also narrower: at the time of writing, ISP ranges are concentrated in the United States, the United Kingdom, Germany, the Netherlands and a handful of other markets, and thin to nothing elsewhere.

How to verify one

  • Compare the WHOIS organisation against the announcing autonomous system, as above.
  • Query the neighbouring addresses in the same /24. If every one of them classifies as a proxy, you are buying into a block that is already known as one.
  • Run a sustained latency test — an ISP proxy should behave like server infrastructure, with stable round trip and negligible packet loss. Jitter that looks residential means it probably is, which changes what you are actually paying for.
  • Read the reverse DNS. A genuine consumer allocation usually carries a PTR in the ISP’s own naming convention; a block that answers with a hosting provider’s generic hostname has already told you where it lives.

Diversity is the other thing to buy deliberately. Fifty addresses from one provider in one country typically means one or two autonomous systems, and an ASN is as much a cluster as a subnet. Spreading across two or three providers costs a little more in administration and removes a single point of correlation, as well as a single point of failure when one provider’s range is actioned wholesale.

For a fleet, ISP proxies suit long-lived accounts that log in from the same place every day, while rotating residential suits shorter or higher-volume work. One more rule holds without exception: when an address has been burned, retire it. The history follows the address, not the account you put on it next.

Related terms