Explained
An ISP proxy combines the two properties operators actually want: an IP address registered to a real ISP (so it carries residential-grade trust with anti-bot systems) and datacenter-grade hosting (so it's fast, stable, and stays the same across sessions). The provider partners with a consumer ISP to obtain blocks of IPs registered under the ISP's name, then hosts those IPs in datacenter infrastructure for performance.
The practical effect is that an ISP proxy looks like a residential IP to the destination site, but behaves like a datacenter proxy in terms of latency and uptime. Unlike residential proxies, which assign a fresh IP per request from a pool of consumer devices, an ISP proxy gives you one fixed IP you keep for as long as you need it.
This makes ISP proxies the preferred choice for any workflow that needs a stable session: managing multiple accounts on the same platform, running bots that maintain login state, scraping behind authentication, and any task where mid-session IP changes break the workflow. They're also commonly called 'static residential' or 'dedicated residential' proxies.
How It Works
When you connect through an ISP proxy, your traffic exits through one specific IP address that's registered with a real consumer ISP (Comcast, AT&T, Verizon Business, etc.) but physically hosted on the proxy provider's datacenter infrastructure. The destination site does an ASN lookup on the IP, sees a consumer-ISP record, and treats your request as residential traffic.
Because the IP is fixed and dedicated to you (or a small group of users), it doesn't rotate across requests. Sessions, cookies, and any IP-bound authentication state stay intact across as many requests as you make. Operators typically use one ISP proxy per account or per workflow they want to keep clean.