Rotating proxies vs sticky sessions: how to choose
Rotating proxies request an available exit change under the provider's rotation model, while sticky sessions request reuse of one assigned exit while it remains available. TrueProxies Residential IPv4 supports normal rotation, explicit rotation, and session identifiers through documented username forms; neither mode guarantees a previously unused or permanently assigned address.
Setting up one session per browser profile? See the anti-detect browser setup guides for tested formats, profile settings and best-effort session results.
What are sticky proxies?
A sticky proxy attempts to reuse one assigned exit for requests carrying the same session identifier. Continuity lasts only while that exit remains available, so test the actual workflow instead of assuming a universal duration.
Sticky sessions are worth testing when a permitted login, form, cart, or multi-page flow needs short-term IP continuity. A consistent exit can reduce unplanned location changes, but it does not prevent security checks or guarantee acceptance.
With TrueProxies, sticky sessions are available on both Residential IPv4 Unlimited and Residential IPv4 GB-based plans. Reuse the same session ID to request continuity and monitor whether the assigned exit changes.
What are rotating proxies?
A rotating proxy changes or requests a change to the outbound exit according to a provider's request, connection, timed, or explicit rotation model. Rotation can increase exit diversity, but it does not guarantee a previously unused address or make separate requests look like different people.
Rotation can fit authorized collection where requests are independent. Continue to respect target terms and rate limits, cap concurrency and retries, and measure repeated exits because distribution alone does not prevent blocks or challenges.
On TrueProxies Residential IPv4, rotation is per connection, not per request. HTTP clients reuse connections by default (persistent connections in RFC 9112), and libraries such as Python requests keep a pool of them: “if you're making several requests to the same host, the underlying TCP connection will be reused” (requests documentation). Every request on one kept-alive connection leaves from the same exit; open a new connection to get a new one.
For TrueProxies Residential IPv4, use the base username for normal rotation or add -rotate to select explicit rotation. Do not add a session identifier when the request should rotate. Either form selects from available exits and can return an address observed earlier.
How proxy rotation models differ
Providers use the word rotation for several behaviors. Treat these as general models, then check the exact controls documented for the service you use. A timed or per-connection model offered elsewhere is not automatically a TrueProxies username selector.
| Model | What it means | Important limit |
|---|---|---|
| Per-request rotation | The provider may select an exit for each independent request | A later request can still repeat an exit |
| Per-connection rotation | The exit may change when the client opens a new proxy connection | Connection pooling can affect observed changes |
| Timed provider rotation | The provider may replace an exit after an interval | No customer-controlled timed selector is published; unavailable exits can still change and no interval is promised |
| Sticky session | Reusing one session identifier requests the assigned exit while available | It is not a permanent or fixed-duration static allocation |
The six public Residential IPv4 username forms are base_username, base_username-country-XX, base_username-rotate, base_username-rotate-country-XX, base_username-session-ID, and base_username-session-ID-country-XX. In concrete credentials, use a two-letter country code such as country-us after the rotation or session component. Session IDs must contain 1–32 letters or numbers.
Configure rotating and sticky Residential IPv4 requests
Use the connection host and HTTP port shown on your service with username and password authentication, or add a trusted IP in your dashboard to connect without a password. On the plain HTTP port the client-to-proxy edge is unencrypted, so proxy credentials are not protected by TLS on that hop; use the HTTPS port (8443) where your client supports it, a trusted network, or a trusted IP. HTTPS targets use CONNECT and encrypt target traffic after the tunnel is established. The commands below demonstrate credential syntax only: example.com does not reveal exit identity, rotation, continuity, or country.
curl --proxy "http://YOUR_HOST:YOUR_HTTP_PORT" \
--proxy-user "base_username-rotate:YOUR_PASSWORD" \
"https://example.com/"curl --proxy "http://YOUR_HOST:YOUR_HTTP_PORT" \
--proxy-user "base_username-session-DEMO123:YOUR_PASSWORD" \
"https://example.com/"curl --proxy "http://YOUR_HOST:YOUR_HTTP_PORT" \
--proxy-user "base_username-session-DEMO123-country-us:YOUR_PASSWORD" \
"https://example.com/"Residential IPv4 also exposes SOCKS5 at the YOUR_HOST:YOUR_SOCKS_PORT endpoint shown in the dashboard. The socks5:// versus socks5h:// DNS distinction applies to SOCKS-capable clients; HTTP proxy clients follow their request or CONNECT behavior instead. Confirm the option your client supports. Residential IPv4 cannot reach IPv6-only destination hosts.
See the Residential IPv4 connection reference for the complete username grammar. Use Proxy Checker or another authorized exit-observation endpoint to compare repeated requests; the sample commands themselves do not verify rotation, stickiness, or geography. Proxy Checker is not a throughput test and does not prove target acceptance.
What are the key differences between sticky and rotating proxies?
| Feature | Sticky proxies | Rotating proxies |
|---|---|---|
| IP behavior | Requests the assigned exit while available | Requests an available exit change; repeats remain possible |
| When the exit changes | When the assigned exit stops being available | On each new connection; a reused connection keeps its exit |
| Best for | Permitted logins, carts and multi-page forms | Independent requests: public data collection, monitoring, SERP checks |
| Target acceptance | Measure representative session flows | Measure representative independent requests |
| Client state | Does not maintain login state by itself | Does not reset cookies or application state |
| Cold response time | Measure with reuse enabled | Measure with rotation enabled |
When should you use sticky proxies?
Managing social media accounts your team is authorized to run. Platforms evaluate login IP changes alongside browser, device, account, and behavior signals. A sticky session reduces unplanned IP changes during a working session while the assigned exit remains available; it does not prevent review or restrictions, and each platform's terms still apply.
Multi-step checkout and form filling. A permitted multi-page workflow can benefit from short-term route continuity. An unexpected exit change may interrupt the flow or trigger another target check, so record changes and test the actual destination.
QA of your own multi-step flows. Testing sign-up, cart, or localized checkout pages on sites you run or are authorized to test is easier when one exit carries the whole flow. Record the observed exit with each run.
Long-running browser sessions. For permitted browser workflows that need continuity, reuse a sticky session identifier and monitor whether the observed exit changes.
When should you use rotating proxies?
Web scraping at scale. Rotation can distribute independent requests across the available pool. It does not guarantee a unique address or prevent target rate limits, so measure repeated exits and cap retries.
SERP monitoring and SEO tracking. Rotation can distribute independent ranking checks across available exits. Verify observed geography and repeated-address behavior instead of assuming every request receives a previously unused IP.
Price comparison and monitoring. Network location is one input that can affect price or availability. Keep account, language, device, request parameters, and timing controlled before attributing a difference to geography.
Ad verification. Rotating requests can add network vantage points to placement checks. Publishers can still classify automation and other signals, so record the observed exit, response, creative, and timestamp instead of assuming concealment.
Can you use both at the same time?
Yes. One authorized workflow can use separate credential forms for separate jobs: a sticky identifier for a permitted multi-step session and rotation for independent collection requests. Keep cookies, accounts, and other application state separate because changing the proxy exit does not reset them.
With TrueProxies Residential IPv4, choose the base username or -rotate form for rotation and reuse one valid -session-ID form when continuity is required. The existing Residential IPv4 Unlimited and Residential IPv4 GB-based products share these connection and session controls; choose between them by measured billing and capacity needs, not by expecting different rotation features. There is no separate rotating-proxy product.
Troubleshoot rotation and session continuity
- The sticky exit changed. Confirm every request uses the identical 1–32 character session ID and supported suffix order. The assigned exit can still change when it is no longer available.
- Rotating requests repeat an exit. Repetition is possible because rotation selects from the currently available pool; it does not reserve a previously unused address.
- Authentication fails. Read the reason in the
X-Proxy-Reasonheader of the 407, then recheck the username, password, host and port shown on your service. Targeting options can be given in any order, but each only once. Our guide to proxy errors lists every reason. - The hostname does not resolve as expected. Check whether the client resolves DNS locally or through the SOCKS proxy and whether the destination publishes an IPv4 address.
- The proxy connects but the target challenges the request. Connectivity, target acceptance, cookies, browser fingerprints, account state, rate limits, retries, and bandwidth are separate observations. Test the exact workflow without treating rotation as ban prevention.
Frequently asked questions
What's the difference between sticky and static proxies?
A sticky session attempts to reuse one assigned exit while it remains available. A static proxy is designed as a longer-lived allocation. Exact duration and replacement behavior depend on the provider and product.
How long do sticky sessions last?
Session duration depends on upstream IP availability and the product you use. Reuse the same session ID when you need continuity, and test the duration against your actual workflow because the assigned IP can change when it is no longer available.
Are rotating proxies better for scraping?
Use rotation for independent requests that benefit from exit diversity. Use a sticky session when a login, cart, or multi-page flow needs continuity, and measure both modes against the target rather than assuming one always performs better.
Does TrueProxies support both sticky and rotating?
Both Residential IPv4 products support sticky and rotating request modes. Reuse a valid session ID for continuity, or use the base or explicit -rotate username form for rotation. Test both on the free trial: 1 hour of Residential IPv4 Unlimited at 10 Mbps with 100 open connections and no traffic cap. No card is needed, and it is one per customer.