Sticky Residential Sessions
One exit.
Up to 60 minutes.
Reuse a session ID to keep the same residential exit for up to 60 minutes. If its Packeter disconnects, the request fails instead of switching exits.
Why sticky
Stability, without giving up residential.
Sessions that persist
Reuse the same alphanumeric session ID to keep one residential exit for up to 60 minutes, while its Packeter remains connected.
A stable location
Keep a consistent country-targeted vantage point for localized QA, multi-step testing, and monitors that fit within the session window.
Predictable failure
If the selected Packeter disconnects, the session fails rather than assigning a new exit underneath an identity-sensitive workflow.
Use it for
Workflows that need one consistent exit.
- Localized website QA — inspect a site from one consistent country-targeted vantage point.
- Multi-step testing — preserve one exit while testing stateful journeys on sites you operate or are authorized to test.
- Bounded monitoring — keep one vantage point for workflows that fit within the 60-minute session window.
- Application testing — a reproducible network identity for QA.
sticky session — simulated traffic
200 OKSTICKY · GET /account — session 9d21US · Denver176 ms
200 OKGET /locale-check — same exitUS · Denver188 ms
200 OKGET /catalog — same exitUS · Denver151 ms
200 OKGET /product/42 — same exitUS · Denver267 ms
200 OKGET /availability — same exitUS · Denver132 ms