One line first: sticky ≠ static
A sticky session is an option on rotating residential: within the console-allowed window, consecutive requests try to reuse the same exit. A static residential IP is a different product line: a predictable fixed exit for the subscription term (then shared or dedicated).
Both can feel like “do not change IP for a while,” but stability length, bill unit, and cost of buying wrong are different. If you have not separated rotating vs static as classes, read Rotating vs static residential first. Below: when sticky is enough, and when you must buy static. Lawful, authorized use only. Not supported for use in mainland China.
What sticky session is (short stability on rotating)
Sticky hangs on the rotating / dynamic product: you still consume a residential exit pool by traffic; console or client params ask to reuse one exit inside a session window.
Boundaries to keep in mind:
- “Try” is not “guaranteed never change.” After the window ends, node changes, disconnects, or backend scheduling, the exit may still change. Window length and param names are console / Docs sourced—this page invents no “always XX minutes unbroken” number.
- Billing usually stays rotating (per GB). Turning sticky on does not auto-convert the bill to “per IP / month.” Bill units: Billing GB vs IP; list prices: Pricing and console (rotating published about $0.40/GB; large tiers on pricing).
- Fits short flows: post-login checkout / multi-step forms, a single creative or landing preview path, any task that needs a short same exit but not a monthly fixed address.
Product entry: Rotating residential. Smoke test: Docs EN quickstart. Scene examples that often use sticky for one path: Ad verification, Localization testing.
What static IP is (term-long fixed exit)
Static residential IP is a separately ordered exit: a fixed address facing you for the subscription term. Shared vs dedicated differ in isolation and price—detail: Shared vs dedicated static; product: Static residential.
Versus sticky, static emphasizes:
- Time scale is the subscription term (often monthly), not “one session window.” Expiry, renewals, and stock are console-sourced.
- Billing is per IP × month. Published about shared $1.50/IP/month, dedicated $5/IP/month—always confirm in console.
- Fits: when, under lawful authorization, you need the same exit for days through the whole term (e.g. authorized store or backend long connections). Do not treat static as “unlimited sticky,” and do not use it for unauthorized access.
Sticky vs static: side-by-side
| Dimension | Sticky session | Static residential IP |
|---|---|---|
| Product class | Session option on rotating residential | Static residential product line |
| Exit stability | Same exit as far as possible inside the window; may still change after window / node change | Fixed exit for the term (shared / dedicated rules differ) |
| Typical duration | Short flow (window from console) | Monthly (or term shown in console) |
| Billing | Usually still per GB (rotating) | Per IP × month |
| Published list (console wins) | Rotating ~$0.40/GB; large tiers on pricing | Shared ~$1.50/IP/month; dedicated ~$5/IP/month |
| Fits | Checkout / multi-step forms, single preview path, short same exit | Authorized connections that must keep one address for the term |
| Do not treat as | “Already bought static” / “guaranteed never rotate” | “Free unlimited sticky” |
Choose by task
| Your task | More common pick | Next step |
|---|---|---|
| Large-scale public collection / multi-region sampling | Rotating pool | Rotating |
| Short post-login flow, checkout / forms, single ad preview path | Rotating + sticky | Rotating; params from console |
| Same exit required for the subscription term | Static (then shared / dedicated) | Static + Shared vs dedicated |
| Still unclear on rotating vs static class | Read selection guide first | Rotating vs static |
When to upgrade to static
Self-check in order:
- Only a multi-step flow inside a window (forms, checkout, single preview) → enable sticky on rotating; smoke-test with console params.
- Same exit required for days or the whole term → buy Static; do not expect sticky to stretch into monthly fixed.
- Multi-store or stronger isolation → after choosing static, read Shared vs dedicated static for the tier.
- Sampling, collection, multi-region rotate only → rotating pool is usually enough; do not force sticky, and do not buy static “to look safer.”
How sessions are named and configured: console + Docs EN quickstart. This page does not publish an expiring param table.
How this ties to billing and product pages
Enabling sticky does not change the bill unit from GB to IP × month. Static does not reprice as traffic just because an exit “sometimes changed”—your console product line and order record win.
When estimating real cost, count retries and failed page-weight traffic—method: Billing GB vs IP; confirm tiers on Pricing. Payment context: USDT/USDC available; Visa/Mastercard applying / pending (not live).
FAQ
Can sticky session replace static IP?
Not as a long-term fixed-exit substitute. Short multi-step flows can validate on rotating + sticky first; once you need a stable same address for the subscription term, buy static—do not lengthen sticky expectations.
What is sticky session? Will the exit never change?
Sticky is a session option on rotating: reuse the same exit as far as possible inside the console-allowed window. After the window, node, or network change, the IP may still change. Window and change behavior are console-sourced—do not assume “sticky set = never rotate.”
Do sticky and static differ on billing?
Yes. Rotating + sticky usually still bills per GB; static bills per IP × month. Published list in the table above and on Pricing; console wins before order.
When should I buy static instead of enabling sticky?
When, under lawful authorization, the business requires the same exit for days through the whole term. Short checkout, forms, or a single preview path → prefer sticky first.
After choosing static, do I still pick shared vs dedicated?
Yes. Shared and dedicated differ on price, neighbor noise, and isolation. After “I need static,” continue with Shared vs dedicated static, then order on Static.
Where are sticky params set? How long is the window?
In the console (or client / API fields described in Docs). Available windows can differ by order, region, and stock—console and Docs return win; this page publishes no fixed minutes.
How does this relate to the rotating-vs-static selection guide?
Rotating vs static covers product-class overview; this page deepens the “sticky ≠ static” section so buyers and support spend less time on wrong purchases. Read both.
Where do prices come from? Can I use this in mainland China?
Plans and list prices: Pricing; console is source of truth. All proxy services on this site are not supported for use in mainland China.
Next steps
- Use the two tables: short same exit → sticky; term-long fixed exit → static.
- Rotating path: open Rotating, configure session in console, smoke-test with Docs EN quickstart.
- Static path: open Static; when needed, read Shared vs dedicated.
- Still unclear on class → Rotating vs static; estimate bills → Billing GB vs IP + Pricing. Localization / ad single-path examples: Localization, Ad verification.
Unsure? On-site support or [email protected]. Sticky is short same-exit as far as possible; static is a fixed exit for the term—do not substitute one for the other.