Rotating and sticky sessions
When NyxonProxies gives you a new IP and when it keeps the same one. Session IDs, hold times, which products support them and how tunnels affect rotation.
A rotating line gets a new IP for each new connection. A sticky line keeps one IP across many connections, for as long as the session holds. You switch between the two with the session parameter in the username.
Rotating
This is the default: no session in the username.
USERNAME-country-usEvery new connection through this line can leave from a different IP. Rotating is the right choice for crawling, price checks, search results and any job that sends many independent requests: spreading them over many IPs keeps the load per IP low.
Sticky
Add a session ID, and every connection that sends the same ID uses the same IP:
USERNAME-country-us-session-a1b2c3d4-time-30Use sticky sessions when the website has to see one visitor across several requests: signing in, filling a cart, paging through a checkout, or keeping an account on a consistent IP.
- Same ID, same IP. Run ten requests with
session-a1b2c3d4and they share one exit. - New ID, new IP. Change the ID to switch IP right away, without waiting for the hold to end.
- One ID per identity. Running several accounts or browser profiles? Give each one its own session ID.
Hold time
The time parameter is the number of minutes to keep the IP, up to 120: -time-10 asks for 10 minutes, -time-30 for half an hour. In the proxy generator you choose it under Keep IP for.
Residential, Mobile and Unlimited Residential exits are real home connections and phones. A device can go offline or change networks before the hold ends, and the session then continues on a new IP. Plan for holds of two hours at most, build long flows so they can resume after an IP change, and do not rely on one residential IP for a whole day.
Generator session modes
| Mode | What the lines do |
|---|---|
| Rotating | A new IP on every connection. |
| Sticky | Each line gets its own random session ID, so each line keeps its own IP for the time you choose. |
| Custom ID | Every line uses the session ID you type, so they all share one IP. Left blank, it falls back to a random ID per line. |
New session IDs in the output panel regenerates the random IDs, which gives you a fresh set of IPs.
Products with sessions
| Product | Sessions |
|---|---|
| Residential | Rotating or sticky |
| Mobile | Rotating or sticky |
| Unlimited Residential | Rotating or sticky |
| Residential Budget | Rotating only |
| Datacenter, Shared ISP, IPv6 | Rotating |
Residential Budget is built for rotating, high-volume work at the lowest price per GB. If a job depends on keeping one IP, run it on Residential.
For Datacenter, Shared ISP and the IPv6 products the generator builds rotating lines.
Connections and tunnels
Rotation happens when a connection opens, not inside one. For HTTPS, your client opens a tunnel through the proxy and keeps it open for later requests to the same site, so those requests share an IP even on a rotating line. HTTP clients that reuse connections, such as a Python requests.Session or a browser, do this on purpose.
- For a new IP on every request, open a new connection for each one. In Python, call
requests.getinstead of reusing aSession. - For a guaranteed same IP, do not count on connection reuse. Use a session ID: it holds across new connections too.
Picking a session ID
Any short string of letters and digits works. Random IDs make sure two jobs never share an IP by accident, while readable IDs make logs easier to follow:
USERNAME-session-k3x9q2ma-time-10
USERNAME-session-acct1042-time-30Do not put hyphens or other symbols in the ID. See Username parameters.
Last updated
Still stuck?
People answer the live chat around the clock. Send the proxy line you used (without the password) and the error you see.