Guides 4 min read

What Is a Rotating Proxy? How IP Rotation Works in 2026

A rotating proxy hands out a different IP from a large pool, per request or per session, through one address. Here's how it works and how to control it.

A rotating proxy is a proxy service that gives you a different IP address from a large pool, either on every request or after a time you choose, while you keep connecting to the same host and port. You don't manage a list of IPs; the provider's gateway picks one for each connection. It's the default way residential and mobile proxies are sold, because it spreads your traffic across many addresses without any extra code.

How a Rotating Proxy Works

Behind the single address is a gateway, sometimes called a backconnect proxy. When your request arrives, the gateway:

  1. Authenticates your username and password.
  2. Reads any options in the username, such as a country or a session ID.
  3. Picks an exit IP from the pool that matches those options.
  4. Forwards your request through that exit and streams the response back.

With no session option, the next request gets a different exit. With a session ID, the gateway remembers which exit it gave that ID and reuses it until the session expires.

Rotation Per Request vs Sticky Sessions

Per-request rotation

Every request, or more precisely every new connection, gets a new IP. This suits jobs made of independent fetches: product pages, search results, public listings. No single IP sends many requests, so you stay under per-IP rate limits.

Sticky sessions

You keep the same IP for a set number of minutes. Use this whenever a sequence of requests must look like one visitor: logging in, adding to cart, paginating with a session cookie, or a browser session that loads dozens of resources. Switching IP mid-session is one of the most common reasons sites throw challenges. Our rotating vs sticky proxies tutorial has full Playwright examples.

Seeing Rotation in Action

This script fetches your exit IP five times with rotation and five times with a sticky session:

import requests

HOST = "global.nodeproxies.xyz:8080"
USER = "USERNAME"
PASS = "PASSWORD"

def ip(username):
    proxy = f"http://{username}:{PASS}@{HOST}"
    r = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=30)
    return r.text

print("Rotating:")
for _ in range(5):
    print(" ", ip(f"{USER}-country-us"))

print("Sticky:")
for _ in range(5):
    print(" ", ip(f"{USER}-country-us-session-demo42-time-10"))

The first block prints five different US IPs. The second prints the same IP five times. Change demo42 to any other string to get a fresh sticky IP.

A Common Surprise: Keep-Alive

Rotation usually happens per connection, not per HTTP request. If your client reuses a connection (keep-alive, a requests.Session, a browser), several requests can go out over the same tunnel and the same IP. That's often what you want in a browser. If you need a new IP every time in a script, open a new connection per request, or use a fresh session ID each time. If the IP isn't changing when you expect it to, see proxy IP not changing.

Handling Failures in a Rotating Setup

Because every request can land on a different exit, treat a single failure as a property of that IP, not of the whole job. Retry a failed request once or twice; with rotation, the retry automatically goes out through a new IP. If a sticky session fails, abandon that session ID and start a new one rather than hammering the same exit. Log the status codes you get back: a steady stream of 403s or 429s on every IP means the problem is your request pattern, not bad luck with individual addresses.

When to Use a Rotating Proxy

  • Scraping public data at volume. See how to avoid blocks when web scraping.
  • Checking prices, search results or ads from many locations.
  • Any workload where one IP would hit a rate limit long before you're done.

When you need the same IP for hours or days, for example a server allowlist, a rotating pool isn't the right tool. See static vs rotating proxies for that decision.

Rotation Doesn't Fix Everything

  • Sending requests too fast from many IPs still looks like a bot. Keep rates reasonable and respect robots.txt and each site's terms; see are proxies legal.
  • Identical headers and fingerprints across thousands of IPs are easy to cluster.
  • Cookies carried across IPs tie the requests back together. Clear them when you rotate, or use sticky sessions.

Rotating Proxies With NodeProxies

Every NodeProxies residential, mobile and datacenter plan rotates by default through global.nodeproxies.xyz. Add -country-xx to pick a country and -session-{id}-time-{minutes} to stick. Rotating residential proxies start at $0.65/GB and go down to $0.35/GB at volume, with no subscription. For heavy workloads, unlimited residential is billed by the hour instead. Register to get credentials.

FAQ

How often does a rotating proxy change IP?

By default on NodeProxies, on every new request. With a sticky session, after the number of minutes you set in the username.

Are rotating proxies residential?

Rotation describes how IPs are assigned, not where they come from. Residential, mobile and datacenter pools can all rotate.

Can I choose the country with a rotating proxy?

Yes. Add -country-us (or any country code) to the username, and every rotated IP will come from that country.

Why does my rotating proxy keep the same IP?

Usually because your client reuses one connection, or because a session ID is in the username. Open new connections or remove the session option.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account