ISP proxies
ISP proxies are static residential IPs sourced from ISP-owned subnets — they look residential to target sites but are hosted on premium datacenter infrastructure, so they're fast like datacenter and trusted like residential.
Unlike Residential and Mobile, ISP proxies are not delivered through a gateway. After purchase, you get a list of static IPs that you address directly.
At a glance
Delivery model
Per-IP list, ip:port:user:pass
Billing
Per IP, per month
Pool size
The IPs you purchased — fixed, dedicated to your account
IP stability
Permanent — same IP across reboots, weeks, months
Geo targeting
Country (and city in select markets) — chosen at order time, not per request
Rotation
Client-side — you pick the next IP from your list
Speed
High (1 Gbps+ per IP)
Protocols
HTTP, HTTPS, SOCKS5
Authentication
User+password (per-IP credentials) or IP whitelist
KYC required
Not by default (may be requested based on risk)
Credential format
Each IP in your list is delivered in the standard four-tuple:
ip:port:user:passExample:
Same user/password across the whole batch you ordered — the IP+port pair is what distinguishes them. Full reference: Proxy list format.
The
helo_prefix in the username is not the gateway grammar — ISP usernames carry no-type-/-region-segments. They are just user identifiers.
When to use ISP
Account-bound workflows — login flows where the site binds anti-bot signals to IP for hours/days
Sneaker / drop / ticket purchases — speed + residential reputation
Long-running monitors — checkers that must stay on the same IP for stability
High-bandwidth scraping where residential per-GB billing gets expensive
Geo-locked services where IP and city must remain consistent
If you need to rotate IPs aggressively per request, residential is a better fit. ISP shines when stability is the requirement.
Five-second example
(Substitute one of the IPs from your list.)
On this page
Quick start — order, download list, first request
Proxy list format — the four-tuple in detail
Authentication — password vs IP whitelist
Locations — country and city coverage at order time
Protocols — HTTP / HTTPS / SOCKS5
Client-side rotation — patterns for picking the next IP
IP management — replace dead IPs, refresh batches
Error definitions — what each status code means
Statistics — per-IP usage and the API
Last updated
Was this helpful?