ISP vs residential proxies: static or rotating?
ISP proxies are static IPs you rent one by one and keep while you pay; rotating residential proxies send your requests through a gateway that assigns exit IPs, rotating or held for a sticky session. They differ in how you get the IP, how you pay for it and how long you keep it.
- Category
- Fundamentals
- Published
- Updated
- Reading time
- 6 min
ISP vs residential proxies is mostly a choice between static and rotating. An ISP proxy is a fixed address that's yours for as long as you rent it. A rotating residential proxy is a gateway: you send requests to one host, and it routes them through exit IPs on home connections, either changing or held for a sticky session. The choice comes down to how you get the IP, how you pay for it and how long you need it.
Two models, two buying decisions
With ISP proxies, you buy addresses: how many, in which locations, for how long. Your code picks an address and keeps using it.
With rotating residential proxies, you buy traffic: how many GB, used through a gateway, with the exit country and session behavior chosen per request in the username. You never handle individual addresses.
Everything else follows from that difference.
What an ISP proxy is
Providers generally use "ISP proxy" or "static residential proxy" for a static IP address that's hosted on server infrastructure but associated with an internet service provider's network rather than a cloud host's. You rent specific addresses, usually per IP per billing period, and connect to each one directly. The address stays the same until you stop renting it, which suits work where a system should see the same client over days or weeks.
What "associated with an internet service provider" means in practice varies by provider, so ask which networks a provider's ISP addresses belong to before you buy. The netdash ISP (static residential) proxies page lists the locations, billing and current availability of ours.
What a rotating residential proxy is
A rotating residential proxy gives you a gateway instead of addresses. You authenticate to one host and port, and the gateway forwards your traffic through an exit IP on a home connection in the country you ask for. In rotating mode the exit IP isn't pinned. With a sticky session, reusing a session ID keeps one exit IP for the lifetime you set, while that IP stays available.
You don't manage addresses, and you can change the exit country by changing the username. netdash residential proxies work this way, with three plans that share one username and password.
Assignment: a fixed list or a gateway
Static IPs arrive as a list. Each line is one address with its port and the credentials for that order:
203.0.113.10:PORT:USERNAME:PASSWORD
203.0.113.11:PORT:USERNAME:PASSWORD
203.0.113.12:PORT:USERNAME:PASSWORDYour code chooses a line and keeps it for as long as it needs the same IP. (The addresses above are documentation examples.)
A rotating residential network has one endpoint per region, and the options travel in the username:
scale-us.netdash.io:2000 USERNAME-cc-US rotating, exit in the United States
scale-eu.netdash.io:2000 USERNAME-cc-DE-session-a1b2c3d4-ttl-30 sticky for 30 minutes, exit in Germany-cc- sets the exit country with an ISO code, and -session- plus -ttl- (in minutes) make a session sticky. The proxy format reference lists every host, port and option.
Billing: per IP or per GB
ISP proxies are billed per IP per period. Your cost depends on how many addresses you hold and for how long; ask any provider whether traffic through each address is capped or metered. netdash ISP IPs are billed per IP every 30 days, with no per-GB charge.
Rotating residential proxies are billed per GB. Your cost follows the traffic you transfer, whichever exit IPs carried it. On netdash, residential GB are one-time purchases with graduated pricing per order, and purchased GB never expire.
As a rule of thumb, heavy, steady traffic through a few addresses favors per-IP billing, and light or bursty traffic spread over many sites and countries favors per-GB billing.
Sessions
With an ISP proxy, the session is the address. Keep using the same line from your list and the website sees the same IP until you stop renting it. Long-lived sessions are where static IPs are strongest.
With a residential proxy, you choose per task. Rotating mode suits independent requests. A sticky session holds one exit IP for the lifetime you set, and the netdash dashboard offers presets from 15 minutes up to 7 days. Because a home connection can go offline, a sticky session lasts only while its exit IP stays available, so long jobs should be ready to start a new session. Static vs rotating proxies covers session choices workload by workload.
ISP vs residential proxies by workload
| Attribute | ISP (static) | Rotating residential |
|---|---|---|
| Same IP for days or weeks | Good fit: the address does not change while you rent it | Not designed for it: a sticky session lasts for its TTL and only while the exit IP stays available |
| A system you control accepts known IPs only | Good fit: add the address to its rules | Poor fit: exit IPs change |
| Exits in many countries | Limited to the locations the provider offers | Choose the exit country per request with an ISO code |
| One multi-step task | Works: use one address from your list | Good fit: one sticky session per task |
| Independent fetches of public pages | Works, but you pay for addresses whether you use them or not | Good fit: rotating mode, billed by traffic |
| Heavy, steady traffic | Billed per IP, with no per-GB charge | Billed per GB, so cost grows with traffic |
To see netdash's residential, mobile, ISP and datacenter networks side by side, compare proxy types. For the datacenter side of the same decision, read residential vs datacenter proxies.
Responsible use
Static or rotating, the same rules apply
Respect robots.txt and each site's terms, keep request rates reasonable and back off when a site slows you down, don't collect personal data without a lawful basis, and don't access content behind logins or paywalls without authorization. netdash doesn't solve CAPTCHAs or other challenges, and your code shouldn't try to get past them: if a site rate-limits or challenges your requests, slow down, check its terms, or use its official API. Read how we expect netdash to be used.
FAQ
Providers use both names for the same kind of product: a static IP you rent and keep, described as associated with an internet service provider's network. netdash calls its product ISP (static residential) proxies.
You can ask for a long sticky session (the longest dashboard preset is 7 days), but the session keeps its exit IP only while that IP stays available. If an address must not change, a static ISP IP is the better fit.
Self-serve checkout for ISP proxies is paused. Contact sales for availability. Residential plans are self-serve and start from a 1 GB order.
Related
- Static vs rotating proxies
Which session type fits logins, monitoring, testing and data collection.
- Residential vs datacenter proxies
IP origin, billing model and consistency compared, with a decision table.
- What is a residential proxy?
How residential IPs route your requests, and what to ask a provider about sourcing.
Spotted something out of date? Tell us.