A rotating proxy is a proxy service that gives you a different IP address as you work, either on every request or after a time you set. You connect to one gateway, and the provider picks the exit IP from a large pool, so your traffic spreads across many addresses instead of piling up on one.
The most common version is rotating residential proxies, where every exit IP belongs to a real home connection. Websites see a stream of ordinary visitors in the locations you choose, rather than one busy server making thousands of requests.
This guide explains how rotation works, how sticky sessions fit in, what a backconnect gateway is, and when rotation is the right tool for your business.
How a rotating proxy works
With a rotating proxy you do not manage a list of IP addresses. You point your scraper, browser or HTTP client at a single host and port. Each time a request arrives, the provider’s gateway chooses an IP from its pool, forwards the request through it, and sends the response back to you.
From your code’s point of view, nothing changes between requests. From the website’s point of view, each request comes from a different visitor.
That simple setup solves the main problem of collecting public web data at scale: per-IP limits. Most websites count how many requests each IP sends in a given time. One address that sends a request every few seconds, day and night, looks like a machine. The same volume divided across thousands of addresses looks like normal traffic.
Rotation vs. sticky sessions
Rotating proxies usually support two session modes. Choosing between them is the most important setting you will make.
Per-request rotation
You get a new IP on every request. This gives you the widest possible spread and no continuity at all. It suits work where every request stands on its own:
- product and category pages
- search result pages
- directory and listing pages
- stock and availability checks
Nothing carries over from one request to the next, so nothing breaks when the IP changes.
Sticky sessions
A sticky session keeps the same IP for a period you choose. Use it whenever requests depend on each other:
- logging in and working inside an account
- adding items to a cart and checking out
- paging through results with a cursor or session cookie
- multi-step forms
Set the sticky window to the shortest time that covers the whole flow. Too short, and the IP changes in the middle of the task. Too long, and you concentrate more traffic on one address than you need to.
Why sessions break when the IP changes
This is the cause of most rotation problems, and it is easy to miss.
When you log in, the website gives your browser a session cookie tied to the visit. If the next request carries the same cookie but arrives from a different city or country, the site sees a user whose location jumped in a fraction of a second. Depending on the site, you get asked to log in again, hit a security check, or lose the session completely.
The proxy does not know you are logged in. It is up to you to keep the same IP for as long as the session needs it. If a flow takes four minutes, a sticky window of a few minutes more covers it with room to spare. If the work runs for days on the same accounts, rotation is the wrong tool. ISP proxies are a better fit there, because they stay in the city and on the ISP (ASN) you choose for the billing period.
Setting up rotation with Shifter
Shifter delivers both modes through one gateway, p.shifter.io:443, with username and password authentication over HTTP(S) or SOCKS5. You control rotation, sticky sessions and targeting in the username, not in your code.
# Per-request rotation: a new US residential IP on every request
curl -x http://p.shifter.io:443 \
-U "customer-USERNAME-country-us:PASSWORD" \
http://ip-info.com/json
# Sticky session: keep the same IP for session abc123 for 600 seconds
curl -x http://p.shifter.io:443 \
-U "customer-USERNAME-country-us-sid-abc123-ttl-600:PASSWORD" \
http://ip-info.com/json
# City targeting with a sticky session
curl -x http://p.shifter.io:443 \
-U "customer-USERNAME-country-us-city-new_york-sid-abc123-ttl-600:PASSWORD" \
http://ip-info.com/jsonRun the first command a few times and the IP in the response changes each time. Without a session ID, the IP rotates on every request. Add sid-<id> to hold an IP, and ttl-<seconds> to set how long the session lasts. Change the session ID and you get a fresh IP.
Targeting works the same way. Add country-us for a country, region-california for a region, city-new_york for a city, or asn-7922 for a specific internet provider network.
Shifter offers three residential pools, so you can match the pool to the job:
- Full Geo: country, region, city and ASN targeting.
- Country Geo: country targeting only.
- Non-Geo: no targeting, for work where location does not matter.
What a backconnect proxy is
The single gateway described above is often called a backconnect proxy. Instead of handing you a list of addresses, the provider gives you one endpoint that connects back into the pool for you.
Backconnect is not another word for residential. Backconnect describes how IPs are delivered. Residential describes where they come from. The two are independent, and backconnect gateways exist for datacenter and mobile pools too.
In practice, a backconnect gateway gives you:
- One endpoint to configure. Your tools point at the same host and port for the life of the project.
- Automatic replacement. IPs that go offline drop out of rotation without your code noticing.
- Targeting through parameters. Country, city and provider selection happen in the credentials.
- No list management. You never build, test or refresh a proxy list yourself.
Benefits of rotating proxies for your business
These are the benefits of rotation itself, separate from the benefits of residential IPs in general.
- Getting past per-IP rate limits. A limit of a few dozen requests per hour per address stops mattering when your requests are divided across a large pool.
- Running large collection jobs. Volume that would get one address blocked becomes unremarkable across thousands.
- Recovering from blocks without effort. If one IP gets blocked, the next request simply uses another one.
- Checking many locations. Comparing prices, ads or search results across many countries needs only a change in the username, not a separate setup per market.
- Fewer pattern signals. Traffic spread across many visitors does not show the steady rhythm of a single bot.
Pool size matters here, but only the part of the pool that is online when you need it. Shifter’s residential network covers 205M+ IPs in 195+ countries, and in our 7 October 2026 benchmark it had the largest live US residential pool of the 16 networks we measured, with 212,212 live US IPs seen in 250,000 requests.
Rotation has limits. It spreads volume, it does not make untrusted IPs trusted. Rotating datacenter IPs against a site that blocks server ranges fails on every IP in the pool. Request patterns, headers and browser fingerprints still matter as well. Rotation improves the network side, and good scraping practice covers the rest.
When to use rotating proxies, and when not to
Use rotating proxies for:
- web scraping and large-scale public data collection
- price and stock monitoring across retailers and marketplaces
- SERP and rank tracking by country or city
- ad verification across regions
- collecting training and grounding data for AI systems
Use sticky sessions or ISP proxies for:
- account management and long logged-in work
- social media and ad platform accounts
- any task where being recognised as the same visitor is the point
For a deeper look at this choice, read our comparison of sticky vs. rotating residential proxies.
Summary
A rotating proxy changes the IP behind your requests, either on every request or after a time you set, through one gateway. Use per-request rotation for independent requests, and sticky sessions for flows that depend on one IP. Backconnect is the gateway model that delivers both from a single endpoint.
Get the session setting right for the job and most blocking problems go away. Get it wrong in either direction and you either break sessions or concentrate traffic where websites notice it.
The quickest way to find the right setting is to test it on your own targets. Shifter’s free trial gives you 100 MB of Residential Proxies over 3 days, with both rotating and sticky sessions.