The core difference is exit stability, not IP reputation
A rotating residential pool assigns a new exit IP on each request or after a configured lifetime window. A Static ISP proxy assigns one fixed IP to your credential line and keeps it there regardless of how much traffic you run through it.
Both types use IPs registered to residential ISPs. The distinction is not about how the IP looks to a target — it is about whether the exit changes between requests. If your workflow depends on the same IP being present across multiple requests, rotating residential breaks it. If your workflow does not care which IP it exits from, static is extra bookkeeping you do not need.
Account-bound work needs a fixed exit
If a workflow involves an authenticated session — logging in, reading account state, submitting authorized operations — and the target checks IP consistency between requests, exit churn produces verification prompts or session drops. This is the correct use case for Static ISP.
The failure mode is specific: the dashboard works once, then asks for re-verification. The IP from the first request does not match the IP from the second. Cookies can still be wrong and the browser profile can still be dirty, but a changed exit is a separate, measurable variable. Check the exit first by looking at the IP logged in the dashboard before assuming the session state is the problem.
On a Proxynade residential pool, the lifetime-<minutes> token in the expanded username sets how long one exit is held before cycling. For a workflow that needs fifteen minutes on one IP, lifetime-15 delays the problem but does not eliminate it. For workflows that need the same IP across days, Static ISP is the correct answer.
Public collection does not need a fixed exit
Product pages, marketplace listings, SERPs, and directories do not authenticate. The target does not know or care whether request twenty comes from the same IP as request one. A rotating residential pool handles this well: exit churn helps spread load, and Volume Residential at $0.89/GB is priced for high-volume reads.
Start on Volume Residential for public collection. Check the usage logs for latency and outcome after a test run. Switch to Premium Residential at $5.00/GB only when logs show the Volume pool is actually producing the failures — not as a precaution.
The bandwidth math favors Static ISP at roughly 2 GB per assigned route
Proxynade pricing: Volume Residential is $0.89/GB. Static ISP is pay-per-IP with unlimited bandwidth on assigned lines. At $0.89/GB, a single static line paying less than that becomes the cheaper option once the same assigned route transfers more than roughly 2 GB in a billing period.
That breakeven assumes all 2 GB flows through one consistently used IP. If those 2 GB are spread across unrelated reads with no need for exit consistency, the pool is still the right choice — a fixed IP adds no value for work that does not require it.
| Scenario | Monthly transfer | Better fit |
|---|---|---|
| Account-bound session, one IP required | Any amount | Static ISP |
| Public reads, no exit requirement | Under ~2 GB per route | Volume Residential ($0.89/GB) |
| Public reads, no exit requirement | Well over 2 GB on a fixed route | Static ISP (bandwidth cost drops to zero) |
| High-block-rate targets | Any amount | Test Premium Residential ($5.00/GB) first |
Static ISP is stable, not invisible
A fixed IP is easier to observe than a rotating one — for both you and the target. Request timing, headers, browser fingerprint, and target policy still apply. One workflow per assigned IP is easier to audit and explain than multiple sessions sharing one line.
If a target rate-limits by IP, a static line that hits it repeatedly from the same address will trip the limit faster than a rotating pool would. Static ISP removes IP-churn as a variable; it does not remove the other variables.
Usage logs close the gap between app counters and actual cost
The Proxynade dashboard network logs show host, outcome, latency, and byte totals per request. The app-level counter is usually lower than the logged bytes: redirect chains, failed TLS handshakes, blocked response bodies, and retried requests all move bytes at the proxy layer without surfacing in application code.
After a test run, compare the local counter against the dashboard CSV export. If Usage Log rows are missing entirely, the client probably bypassed the proxy. If a Static ISP line shows a different IP than the one listed in the dashboard, check the generated line before opening a support ticket — mismatched credentials are the common cause.
Routing on the pool gateway
The Proxynade pool gateway is http://proxynade.net:2555 with username and password auth. The expanded username carries routing options: base username plus a required plan token (volume, premium, or datacenter), an optional lowercase country code (country-us), and an optional rotation lifetime in minutes (lifetime-30). Datacenter lines skip the lifetime token. Static ISP lines are assigned directly — no pool token needed.
# Residential pool — Volume plan, US exit, 30-minute sticky window
http://proxynade.net:2555
username: rt97db6958d9-plan-volume-country-us-lifetime-30
password: <your-password>
# Residential pool — Premium plan, no country preference
http://proxynade.net:2555
username: rt97db6958d9-plan-premium
password: <your-password>
# Static ISP — fixed IP assigned to this line
# Use the generated host:port from the dashboard directlyResidential vs Static ISP FAQ
When does Static ISP cost less than residential? At Proxynade pricing, a Static ISP line costs less than Volume Residential ($0.89/GB) once the assigned route moves more than roughly 2 GB per month. Below that threshold, paying per GB is cheaper.
Does a static IP make target blocks less likely? Not by itself. Static ISP removes IP churn as a variable, but request timing, headers, and target policy still apply. A consistent IP is easier to observe than a rotating one — for both you and the target.
Why does my usage log show more bytes than my app counter? The proxy meter counts redirect chains, failed TLS attempts, blocked responses, and retried requests that never surface in app-level logs. The gap is normal.
What does the lifetime token control in a residential username? The lifetime-<minutes> token sets how long the pool gateway holds one exit IP before cycling. Datacenter lines skip this token.
Can I mix Static ISP and residential for the same workflow? Yes. A static line for the account-bound leg and a residential pool for the public-read leg is a common pattern, billed separately by type.
Decision checklist
- Job breaks when exit changes → Static ISP.
- Job is public reads, exit irrelevant → residential pool.
- High transfer volume on one fixed route (>2 GB/month) → Static ISP saves on bandwidth cost.
- High block rate on Volume pool → test Premium before buying static.
- Usage log bytes exceed app counter → expected; check for missing rows before assuming billing error.
- Static line shows wrong IP → verify generated line credentials before opening a ticket.