How ISP proxies work
A provider partners with a consumer ISP (or operates under a sub-allocation from one) and gets a block of IPs announced under the ISP's ASN. The IPs physically live in the provider's datacenter, but BGP announcements and WHOIS records list the consumer ISP as the operator. To any anti-bot doing ASN lookup, the IP looks like a Comcast or BT residential connection — not a datacenter IP.
Because the IP is static and the provider controls the hardware, there is no rotation by default. You lease a specific IP for a fixed term (monthly, annually) and it is yours alone, or shared among a small pool, for that period.
Why Akamai scoring rewards ISP static
Akamai's Bot Manager scores sessions multi-request: trust accumulates as the same client makes consistent successful requests. The _abck cookie flips from ~-1~ to ~0~ after the first successful sensor.js POST and stays trusted as long as the session looks consistent. Rotating residential IPs mid-session resets this trust — Akamai treats it as a fresh, untrusted client. Static ISP IPs preserve the accumulation across hours or days, which matches how a real consumer browses.
For account-tied scraping (logged-in workflows, persistent shopping carts), ISP static is also the only sensible choice because session cookies need to survive on a stable identity.
When to use ISP vs residential vs mobile
ISP static: long sessions, Akamai, account-tied scraping, anything where multi-request trust accumulation matters.
Rotating residential: high-volume independent requests where each request is its own session — search scraping, SERP collection, listing snapshots.
Mobile: hardest DataDome and PerimeterX targets where IP reputation alone determines the outcome.
Cost-wise: ISP at ~$2/IP/month for hundreds of long-lived sessions is much cheaper than rotating residential GB pricing for the same workload.
