PhantomFundamentals
Sticky vs. Rotating Proxies: Sessions and Examples
The difference between sticky and rotating proxies is how long requests reuse an exit IP. A rotating session asks for a new route on each request; a sticky session asks to keep a route using the same session ID. Choose sticky for connected steps and rotating for independent requests. Neither mode guarantees a particular IP or access to a destination.
Sticky vs. rotating proxy sessions at a glance
An exit IP is the address the destination sees. Both modes connect through the same proxy gateway; changing session behavior does not require buying a different kind of residential bandwidth.
| Behavior | Sticky sessions | Rotating sessions |
|---|---|---|
| Exit IP | Requests reuse a route while available | Requests ask for a newly selected route |
| Configuration | Reuse a session ID and lifetime | Omit the session and lifetime tags |
| Best fit | Multi-step browsing and localization tests | Independent public-page checks and sampling |
| Cookies | Keep the same browser context separately | IP rotation does not clear cookies |
| Lifetime | Requested maximum; a route may end early | No requested sticky lifetime |
| Main tradeoff | Depends on one residential route staying online | Continuity between requests is not expected |
When to choose sticky sessions
Use a sticky session when the next step depends on the last. For example, a localization QA test might open a product page, select a delivery region, and inspect a cart on a site you are authorized to test. Reusing one route removes an unnecessary network change between those steps.
Keep the same browser context or cookie jar as well as the same proxy credentials. A proxy session controls routing; it does not save login state, cookies, local storage, or application data for you.
- Assign one generated sticky session to each independent browser workflow.
- Reuse that complete proxy string throughout the workflow instead of generating a new line for every step.
- Choose a lifetime that covers the test, then handle disconnections explicitly.
When to choose rotating proxies
Use rotation for tasks whose requests are independent, such as sampling permitted public pages or comparing localized responses. A country setting can constrain the pool while leaving the individual route selection to the gateway.
Pool selection can return an address you have already seen. Rotation is not a list of unique, never-repeated IPs. It also does not make a destination accept a request or remove the need for reasonable rate limits and authorization.
Rotating and sticky password examples
In PhantomProxies, the routing settings are attached to the proxy password. These illustrative values show how a country-targeted rotating password differs from a sticky password. PASSWORD is a placeholder; use the actual output from your dashboard.
A sticky identifier has eight alphanumeric characters. Reuse the same identifier, country, and lifetime for connected steps. Generate a new identifier to request an independent session.
Rotating, United States:
PASSWORD_country-us
Sticky, United States, requested 30-minute lifetime:
PASSWORD_country-us_session-a1B2c3D4_lifetime-30m
Separate sticky session with the same settings:
PASSWORD_country-us_session-e5F6g7H8_lifetime-30mHow to test whether your session is working
Start with a neutral IP echo endpoint and a small number of sequential requests. Record the time, selected mode, country, and returned IP. Keep passwords and full proxy URLs out of shared logs.
For a sticky test, reuse one generated string across requests. For a rotating test, remove session and lifetime tags and compare several results. One repeated IP does not establish that rotation is broken. Test your real workflow only after basic connectivity works.
- Confirm the protocol matches the gateway port.
- For sticky mode, confirm your application is not generating a new session ID on every request.
- Keep country settings unchanged during a continuity test.
- Use timeouts and a bounded retry policy so failures do not create an endless loop.
Why did my sticky proxy IP change early?
A residential route depends on a real device remaining available. A requested lifetime is not a reservation of a dedicated static IP: the route can end early if that device disconnects. PhantomProxies lets you request lifetimes up to seven days, subject to route availability.
Before changing settings, check whether your application regenerated the session ID, changed countries, or used a different proxy string. If the workflow truly requires an address that stays fixed for weeks, evaluate a static ISP or dedicated proxy service instead.
Do sticky sessions use less bandwidth?
Session mode alone does not determine bandwidth. Response size, browser assets, uploads, redirects, and retries drive transferred data. A sticky session can reduce repeated setup in some workflows, but it does not make downloaded data free.
Measure the same representative task in the mode you intend to use. Include failed attempts and required assets, then estimate the full run from that sample.