The best rotating proxies give you a fresh IP when you want one and keep the same IP when you need one, without you managing a list. Almost every provider advertises rotation, so the useful question is how it's controlled and how well it holds up under real load. This guide explains the rotation models, the features that matter and a script you can run against any rotating proxy to check repetition and session stability.
How Rotating Proxies Work
You connect to one gateway address. For each new connection or request, the gateway picks an exit IP from its pool and forwards your traffic through it. You never see the pool; you just see a different IP on the other side. For a deeper explanation, read what is a rotating proxy and what is a backconnect proxy.
Rotation Models You'll Run Into
- Per-request rotation: every request gets a new IP. Best for scraping many independent pages.
- Timed sticky sessions: the same IP for a set number of minutes, then a new one. Best for logins, carts and multi-step flows.
- Session-id control: you choose an id; same id means same IP, new id means new IP. Gives you full control in code.
- Rotation on demand through an API or a link: common with dedicated mobile modems.
The most flexible setups combine per-request rotation as the default with session ids for sticky behaviour. Our rotating vs sticky proxies tutorial shows both in Python and Playwright.
What to Look For
Pool size relative to your volume
A big pool means less chance of getting the same IP twice in a row, and less chance that someone else just burned it on your target. What matters is the pool available in the countries you target, not the global headline number.
Control in the credentials
Rotation and stickiness should be controlled in the username or a parameter, so you can switch per request in code without changing endpoints.
Session stability
A sticky session that changes IP after two minutes when you asked for ten will break logins. Test it.
IP type
Rotation doesn't fix a bad IP type. Rotating datacenter IPs still look like datacenter IPs. For protected sites you want rotating residential or mobile.
Test Rotation Yourself
This script sends 50 requests without a session and reports how many unique IPs came back, then holds a sticky session and checks it stays on one IP:
import time
import requests
USER = 'USERNAME'
PASS = 'PASSWORD'
HOST = 'global.nodeproxies.xyz:8080'
def ip_via(username):
proxy = 'http://%s:%s@%s' % (username, PASS, HOST)
r = requests.get('https://api.ipify.org', proxies={'http': proxy, 'https': proxy}, timeout=30)
return r.text.strip()
# 1. per-request rotation
ips = [ip_via(USER + '-country-us') for _ in range(50)]
print('rotating: %d unique IPs out of %d' % (len(set(ips)), len(ips)))
# 2. sticky session: same id should return the same IP
sticky = USER + '-country-us-session-test42-time-10'
seen = set()
for _ in range(10):
seen.add(ip_via(sticky))
time.sleep(30)
print('sticky over 5 minutes:', seen)A healthy rotating residential network should return close to 50 unique IPs out of 50 and one IP for the sticky session. The rotation troubleshooting guide covers what to check if IPs don't change.
Choosing a Rotation Strategy for Your Job
- Scraping product or search pages: rotate per request.
- Paginated results tied to a cookie: one session id per crawl of a listing, a few minutes long.
- Managing your own accounts: one session id per account, long enough to cover your work, same country every time.
- Checkout or form testing: one session per test run.
A practical pattern is generating session ids from what you're doing, for example session-shop-run-17 or session-acct-anna. If a session's IP gets blocked, change the id to get a new one.
Rotation Mistakes That Cost You Money
- Reusing one session id across all threads. Every thread then shares one IP, which defeats rotation and concentrates rate limits.
- Setting very long sticky times for scraping. If an IP gets blocked mid-session, every request until the timer ends is wasted. Use short sessions or none.
- Rotating mid-login. A login followed by requests from a different IP can invalidate the session or trigger security checks.
- Keeping HTTP keep-alive connections open and expecting new IPs. Some clients reuse the same tunnel; if IPs don't change, disable connection reuse or start a new client.
Rotating Proxies From NodeProxies
NodeProxies residential (90M+ IPs, 195+ countries), mobile (1M+ carrier IPs) and datacenter plans all rotate per request by default. Add -session-{id}-time-{minutes} to the username to keep an IP, and -country-xx to choose the country. Build usernames with the proxy username builder. Residential starts at $0.65/GB with no subscription, or use unlimited residential at $3.90/hour. See the pricing page.
FAQ
What is the best rotating proxy type?
Rotating residential for most uses. It combines a large pool with IPs that look like normal home users.
How often do rotating proxies change IP?
It depends on the setup. On NodeProxies the default is a new IP on every request; a sticky session keeps one IP for the minutes you specify.
Can I keep the same IP with a rotating proxy?
Yes, with a sticky session. Use the same session id and the gateway returns the same IP until the session time runs out.
Are rotating proxies good for social media?
Use sticky sessions, not per-request rotation, for logged-in accounts. Changing IP on every click looks unusual to platforms.
