Sticky Residential Proxies

Same label.
Same exit.

Reuse a session label to keep the same residential exit. Each successful new connection restarts a 60-minute timer, so an active session can keep its exit for longer than an hour.

A layered black-paper landscape with one uninterrupted route to a residential exit

Why sticky

Stability, without giving up residential.

Sessions that persist

Reuse the same alphanumeric session label to keep one residential exit while its Packeter stays online. Each successful new connection restarts the 60-minute timer.

A stable location

Keep a consistent country-targeted vantage point for localized QA, multi-step testing, and monitors that check in at least once an hour.

Check the exit

Each exit is a real home connection. Before a step that must use the same IP, check the exit IP your session is using.

Sticky, not static

A sticky session is not a static IP.

Static residential proxies, also called ISP proxies, give you one fixed IP for days or months. PacketStream does not sell them. Every exit is a real home connection, so it is there only while its Packeter is online.

  • Same exit, new connections. Every new connection with the same session label goes to the same exit. If that exit goes offline, connections fail until it comes back. The label never moves to another IP.
  • Rolling 60-minute timeout. Each successful new connection restarts the timer. After 60 minutes with no successful connection, the label gets a new exit.
  • Check before key steps. When a step must use the same IP, check the exit IP first.
  • Same price. Sticky and rotating traffic both cost $1.00/GB.

Read the sticky session docs →

1# Add a session label to your auth key2curl -x "https://proxy.packetstream.io:31111" \3  -U "USER:AUTH_KEY_session-catalog42" \4  "https://ipinfo.io"56# Run it again: same label, same exit

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 connect at least once every 60 minutes.
  • 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

One session.
One residential exit.