Multi-step flows finish as one visitor
A login, a cart, a checkout and a multi-page form all read as one person because they leave from one address. A rotating IP breaks that at the first step that checks.
Sticky Proxies
The same exit IP stays yours for as long as you set. Sticky sessions keep logins, carts, and multi-step flows on one identity.
- Configurable 1–60 Minute TTL
- One Exit IP for the Whole Session
- Residential & 4G/5G Mobile Pool
- Country / City / State / ASN Targeting
- Antidetect Browser Compatible
- HTTPS & SOCKS5 Protocol Support
Which products hold a session?
ISP Proxy
Static by design: the IP never changes, so no TTL is needed.
Datacenter Proxy
Static too — one dedicated address for the whole term.
Residential Proxy
Sticky sessions of 1 to 60 minutes on real home IPs.
Mobile Proxy
Sticky sessions on 4G/5G carrier IPs, the highest trust score.
Gaming Proxy
Static low-ping IPs, held for the whole rental.
Why Proxynet sticky proxies?
One IP until the session ends. Configurable TTL, session IDs and geo-targeting.
The same pool as rotating, chosen per session
Sticky is not a separate product but a session model over the same residential and mobile pools. The same account can rotate one job and pin another, without buying twice.
Per GB, and your balance sets the rate
You pay for the traffic you move, not for a seat or a subscription, and the more you keep in your wallet the lower the per-GB price gets.
A high trust score and a low ban rate
Sessions run on real home and carrier connections, which is the kind of address a target site is least likely to challenge in the middle of a checkout.
HTTP, HTTPS and SOCKS5
All three protocols come with the plan and switch from the panel, so a browser automation and a native client can share one session pool.
Instant delivery, no order to wait on
Sessions are available the moment your balance is topped up. There is no provisioning queue and no approval step between paying and connecting.
Pin a session in the country and city the flow belongs to. Each country has its own page with the carriers and coverage behind it.
Sessions are brokered by servers in TIER 3+ data centres under continuous monitoring, so pinning an IP costs you nothing in speed.
KVKK and GDPR compliant
Personal data is processed under KVKK and GDPR. What we collect, why, who sees it and for how long is set out in the privacy policy.
1–60 minute TTL with session ID control
Set the TTL anywhere from 1 to 60 minutes through a duration parameter, and give each parallel workflow its own session ID — different IDs bind to different exit IPs, so profiles never bleed into one another.
One exit IP for the whole session
Every request goes out through the same exit until the TTL expires. The IP you signed in with is the IP you finish on — the identity never changes mid-flow.
Country, city, state and ASN targeting
Decide where the pinned IP comes from: 194 countries, thousands of cities, plus state and carrier (ASN) level targeting at no extra cost.
Residential and 4G/5G mobile pool
Sticky sessions draw on genuine home-user lines and mobile carrier NAT blocks. Both sources leave no datacenter footprint and run under one account.
Single backconnect endpoint
No proxy list to maintain — you connect to one host:port. The gateway handles session lifetime, so your application needs no extra code.
USER:PASS or IP whitelist auth
Pass session duration, session ID, and location as username parameters, or whitelist your server IP for passwordless connectivity.
Proxies in 194 countries worldwide
City, ASN and carrier targeting on the Residential, ISP, Datacenter and Mobile plans. These are the deepest pools; each country has its own page with its ISPs, carriers and coverage.
Session Persistence & TTL Architecture
What is a Sticky Proxy?
A sticky proxy holds the exit IP assigned to you for a duration you choose. That duration is the TTL (time to live), configurable from 1 to 60 minutes in the Proxynet dashboard. Every request you send goes out through the same IP until the TTL expires; then the gateway assigns a fresh IP from the pool and the timer restarts.
Sticky vs. Rotating: A Rotating Proxy changes identity on every request, which suits stateless, high-volume crawling. A sticky proxy does the opposite and pins the identity. In any flow that continues after a sign-in, an IP change mid-session drops the session or trips a security check on the target — sticky mode removes that failure mode entirely.
Which Products Offer Sticky Sessions? Session persistence is available on the Residential Proxy and 4G/5G Mobile Proxy pools, because both draw on dynamic IP sources that need session management. With ISP Proxy and Datacenter Proxy plans the IP is already dedicated to you for the full term, so persistence is the product itself rather than a setting.
Choosing between residential and mobile depends on how sensitive the target is: the residential pool gives you the widest geographic spread across 194 countries, while 5G mobile proxies carry the highest trust score thanks to carrier-grade NAT. On either pool you can open the session over HTTP & HTTPS or SOCKS5, with free country, city, state, and ASN targeting.
Session Duration (TTL)1 – 60 minutes
Exit IPPinned for the session
TargetingCountry / City / ASN
Sticky Session Tunnel
One endpoint · One exit per session
Residential Pool
160M+ IP
Mobile Pool
20M+ IP
194 countries · Residential & MobileHTTPS & SOCKS5
PX-STICKY-GATESticky Proxy Session
Session Pinned
Renews when the TTL expires
Session Flow & TTL Lifecycle
How Does a Sticky Proxy Work?
When your antidetect browser, bot, or application opens a sticky session, the lifecycle runs through four phases:
- Declaring a Session ID and TTL: You append a session ID and a duration parameter to your username. Requests carrying the same session ID bind to the same exit; different IDs bind to different exits.
- Selecting and Pinning the IP: The gateway picks a residential IP or 4G mobile proxy IP matching your country, city, state, and ASN filters, then pins that IP to your session.
- Identity Consistency Through the TTL: Sign-in, cart, form, and confirmation steps all travel over the same IP. Because the identity the target sees never changes mid-session, you avoid extra verification and dropped sessions.
- Expiry and Renewal: When the TTL expires the gateway assigns a fresh exit and the timer resets. You can also force renewal at any moment by changing the session ID, or switch to rotating proxy mode for stateless workloads.
Choosing a sticky proxy: what to look at
A sticky session is a length of time and a pool. Four questions set both.
How long should the session last?
Long enough for the flow to finish and no longer. A login and a cart are minutes; a form-heavy onboarding can be twenty. A TTL far past the work keeps an address busy that another job could have used, and the panel takes anything from 1 to 60 minutes.
A login, or collection?
If the target counts a session — a cart, an account, a rate limit tied to a visitor — sticky is the answer. If it counts requests, rotating spreads the same volume over many addresses and finishes sooner for the same money.
Sticky or static?
Sticky holds an address for up to an hour; static holds it for the whole rental. Anything that has to be recognisable tomorrow — a logged-in account, a whitelisted integration — wants static, on ISP or datacenter.
Residential or mobile?
Residential is the larger pool and the cheaper GB, and it is enough for most session work. Mobile carries the trust of a real 4G/5G carrier address and is worth its price where a target is strict about who it lets keep a session.
How to buy a sticky proxy
Three steps, a few minutes end to end.
Top up your balance
Add funds to your wallet first: on ISP, datacenter, residential, mobile and gaming the balance you hold also sets your unit price — the higher it is, the less you pay per IP or per GB.
Create your proxies
Pick the product and where it exits: a quantity of IPs on the per-IP products, one gateway on the per-GB ones. Either way it is live at once, with no order to wait on.
Connect and manage
Authenticate with user:pass or whitelist your server's IP, then point your tools at what the panel gives you: an exported list of addresses, or the gateway's single host:port.
Rotating, sticky and static compared
Three session models over the same network. The question is not which is best, but how long one IP has to stay yours: one request, one flow, or the whole rental.
| Property | Rotating | Sticky | Static |
|---|---|---|---|
| When the IP changes | On every request | When the session TTL runs out | Never, for the whole rental term |
| How long you keep it | One request | 1 to 60 minutes, chosen by you | The term you bought |
| Pools it runs on | Residential and 4G/5G mobile | Residential and 4G/5G mobile | Static ISP, datacenter, IPv6 and gaming |
| Billing | Per GB, pay as you go | Per GB, pay as you go | Per IP, for the term |
| Traffic | Metered by the gigabyte | Metered by the gigabyte | Uncapped on every static pool |
| Targeting | Country, city, state and ASN, free | Country, city, state and ASN, free — chosen per session | Country and city, chosen when you order |
| What it is for | High-volume collection, price and SERP monitoring, many parallel threads | Logins, carts and multi-step forms — anything that has to finish as one visitor | Account management, whitelisted integrations, long sessions, gaming |
| When it is the wrong choice | Anything that has to stay logged in | Work that needs the same address tomorrow | Collection that has to spread load over many addresses |
| Where it sits at Proxynet | The rotating residential and mobile plans | The same plans, with the session TTL set in the panel | The ISP, datacenter, IPv6 and gaming plans |
Use Cases
Sticky Proxy Industry Use Cases
From account management and checkout flows to authenticated dashboards and end-to-end testing — every workload that needs session integrity.
Give every AdsPower, GoLogin, Dolphin Anty, or Multilogin profile its own session ID. One profile locks to one IP, and profiles never carry each other's trace.
Queueing, seat selection, and payment have to finish under one identity. A sticky session keeps the queue system recognising you from start to finish.
Ad platforms, seller consoles, and analytics tools bind the session cookie to an IP. Session persistence keeps the long panel sessions market research depends on from dropping.
Frequently Asked Questions.
Everything you need to know about Sticky Proxies.
Have a different question, or need infrastructure for many parallel sessions? Our expert team is available 24/7.
No, they are different products. A sticky proxy pins an IP chosen from the residential or mobile pool to your session for the TTL you set (1 to 60 minutes); once it expires, the IP changes. A static proxy is a dedicated IP on the ISP or datacenter pool that stays yours for the whole rental term instead of minutes. Choose sticky for short-lived session integrity, and static when you need a permanent, recognisable identity — see the session-model comparison table on this page for the full picture.
TTL (time to live) is the session lifetime that determines how long the pinned IP stays yours. It is freely configurable from 1 to 60 minutes in the Proxynet dashboard. Short TTLs suit quick verification and crawling passes; longer TTLs suit account management and multi-step checkout flows. When the timer expires the gateway assigns a new IP automatically.
A rotating proxy uses a different exit IP on every request and is built for stateless, high-volume work: scraping, SERP tracking, price monitoring. A sticky proxy pins the identity instead and is meant for work that needs session integrity: signing in, cart and checkout flows, account management. Both modes run in parallel under one account — you simply change the username parameter per job type.
Decide by how sensitive the target is. Residential sticky sessions give you the widest geographic spread across 194 countries plus city-level targeting, which is enough for general account management and e-commerce flows. 4G/5G mobile sticky sessions carry the highest trust score thanks to carrier-grade NAT, a clear advantage on targets that verify aggressively, such as social platforms.
There is no cap on concurrent sessions. Give each workflow its own session ID and run as many parallel pinned sessions as you need — different session IDs bind to different exit IPs from the pool. That is what lets you operate dozens of antidetect browser profiles in complete isolation from one another.
Yes. The moment you change the session ID in your username, the gateway assigns a fresh exit IP and the TTL counter restarts. This lets you move on to the next account with a clean identity as soon as you are done, instead of waiting for the current IP to expire on its own.
Sticky sessions are a usage mode of the residential and mobile plans rather than a separate product, and carry no surcharge. Residential plans run $1.50 – $3.30 per GB and mobile plans $3.00 – $5.50 per GB depending on the tier. You pay for traffic consumed, not for session count or number of IPs.
Because the pinned IP is a genuine home or cellular line, it can occasionally drop when the line owner goes offline. If that happens the gateway assigns a new IP matching the same targeting criteria. The session on the target site may drop with that change; for critical flows we recommend a shorter TTL plus retry logic on your side.