Why session length matters
Any multi-step flow (login, cart, checkout, paginated search) needs the same IP from start to finish. If the IP changes midway, the site may log you out, reset the cart or challenge you. The longer and more reliable a sticky session, the more you can do in one flow. Background in sticky vs rotating sessions.
How each provider does it
| Webshare | Geonode | |
|---|---|---|
| How to request a session | Session number in the gateway username | Session ID in the username, with configurable lifetime |
| Published maximum | Not published as a fixed duration | Up to 24 hours |
| Rotation alternative | Rotate suffix for a new IP per request | Rotating mode |
| Fixed-IP alternative | Datacenter or static residential IPs in direct mode | ISP proxies |
Webshare uses a session suffix on its backbone gateway; see Webshare sticky sessions. Geonode documents custom session IDs and lifetimes, with sticky sessions of up to 24 hours on residential traffic.
The residential caveat
On any residential network, a session is tied to a real device. If that device goes offline, the IP leaves the pool and the session ends, however long the provider allows. Long maximums help, but you still need to handle drops:
- Check the exit IP at key points in long flows.
- Restart cleanly with a new session if it changes.
- Keep flows as short as the job allows.
When you need guaranteed stickiness
Use static IPs instead of residential sessions:
These never change, which suits accounts and daily logins. See ISP proxies compared.
Proxy tip: If you need managed scraping rather than raw proxies, Geonode also sells a Scraper API with a free monthly allowance, which Webshare doesn't offer. More in our complete Geonode guide.
Designing flows on each
| Flow | Webshare | Geonode |
|---|---|---|
| Paginated scraping | Session per listing | Session per listing |
| Login plus a few actions | Session, kept short | Sticky session |
| Hours-long browser task | Static residential IP | Sticky session up to 24 hours, or ISP |
| Daily account management | Dedicated static residential | ISP proxy |
Verdict
- Geonode for long residential sessions, thanks to its published 24-hour maximum and configurable lifetimes.
- Webshare for short sessions alongside cheap static IPs for long ones.
- Either for paginated scraping and short flows.
Measuring session stability
Run 100 sticky sessions per provider and check the exit IP every minute for 30 minutes:
| Metric | What it shows |
|---|---|
| Share of sessions with no change | Stability over the period |
| Median time to first change | Typical session life |
| Error rate during sessions | Connection quality |
Run it in the country and at the time you'll actually work; stability varies with device churn.
Designing for drops
- Keep a flow's state (cookies, step reached) so you can resume or restart cleanly.
- Detect IP changes and restart from a safe point.
- Use static IPs for anything that can't tolerate a change.
Budget tip: Many teams end up using both: Webshare for cheap per-IP datacenter and static residential lists, Geonode for per-GB residential traffic that doesn't expire. Start with Webshare sticky sessions.
Session IDs at scale
Generate unique IDs per flow and per worker, and log them. When something goes wrong, the session ID lets you correlate requests across your logs on either provider.
A real-world example
A team automating multi-step insurance quote checks needs each flow (about 12 minutes long) to stay on one residential IP. Their logs show occasional mid-flow IP changes on both providers due to device churn. Using Geonode with a session lifetime set comfortably above the flow length, plus a restart on IP change, gives the fewest interruptions. For a few flows that must never change IP, they use static ISP IPs instead.
For the bigger picture beyond these two providers, read our best proxies buyer's guide, and see cheap proxies for ways to cut cost per successful request.
Key takeaways
- Geonode advertises sticky residential sessions up to 24 hours with configurable lifetimes.
- Webshare holds sessions through a session number on its gateway.
- Residential sessions can end early on any network when devices go offline.
- Use static IPs from either provider for guaranteed stickiness.
- Detect IP changes and restart flows cleanly.
FAQ
What is the longest sticky session on Geonode?
Geonode advertises sticky residential sessions of up to 24 hours.
How long do Webshare sessions last?
Webshare doesn't publish a fixed maximum. Treat residential sessions as short-lived and use static IPs for long ones.
Why did my sticky session change IP early?
The residential device went offline. Build in retries and session restarts.
Can I set a custom session length?
Geonode documents configurable session lifetimes; Webshare holds sessions through a session number.
Do sticky sessions work with SOCKS5?
Yes, on providers that support both; set the session in the username.
How many sticky sessions can I run at once?
Practical limits depend on plan and concurrency; ramp up and monitor errors.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.