ISP Proxy

An ISP proxy is a static IP address registered to a consumer internet service provider's ASN but hosted on server hardware in a data center. IP intelligence databases classify addresses mostly by who owns the range, so the lookup a target site performs returns residential, while the machine answering the request sits on a rack and has a rack's bandwidth. Most vendors sell the same product under the name static residential.

Three properties decide how they behave in production. The address is statically assigned, so it does not change between requests and a target can accumulate a history against it, for better or worse. Throughput and latency are datacenter grade, usually several times better than a residential peer routed through someone's home broadband. And the pool is finite. A provider holds specific blocks, so when a target flags a range, every address in it degrades together and retrying does not bring it back.

They are sold per IP per month rather than per gigabyte, which inverts the cost model against rotating residential. Webshare's pricing page, read on 2026-07-27, lists static residential from $0.30 per proxy per month on a 20 proxy plan, with bandwidth described as unlimited subject to a fair usage policy, while its rotating residential is metered at $3.50 per GB against a $7.00 regular rate. Prices move constantly, so treat those as a snapshot of the shape rather than a quote. Fixed cost scales with how many addresses you hold, not with how many bytes you pull through them. A job that moves heavy volume against a small set of targets is cheap on ISP and expensive on metered residential, and the reverse holds just as reliably.

Reach for ISP when the work needs a long lived logged in session against a target that checks network reputation but is not running the most aggressive behavioral defenses. The static address keeps the session coherent and the bytes are not billed twice. Size the block so a burn is survivable: spread purchases across several /24s and, on targets that matter, across more than one provider, because subnets get flagged as units. A single burned /24 should cost you a slice of capacity, not the whole job. Keep a few addresses idle in reserve so there is somewhere to fail over to on the day it happens.