A rotating proxy gives you a different IP address as you work, either on every request or after a set interval. Instead of one address carrying all of your traffic, the load spreads across a pool, so no single address accumulates the request volume that makes a site take notice.
This article covers how rotation actually works, what backconnect means, and how to configure both.
How Rotation Works
You do not manage a list of addresses. You connect to a single gateway endpoint, and the provider assigns an address from the pool for each request. From your scraper’s point of view nothing changes between requests. From the target’s point of view, each request arrives from a different visitor.
There are two rotation modes, and choosing between them is the main configuration decision.
Per-request rotation issues a new address every time. Maximum spread, no continuity. Use it for independent fetches: product pages, search results, directory listings, availability checks. Nothing carries between requests, so nothing breaks when the address changes.
Sticky sessions hold one address for a fixed window, commonly 1 to 30 minutes. Use them whenever requests depend on each other: paginating through a cursor, anything after a login, multi-step forms and checkouts.
You choose between them in the credentials, not in your code. Providers encode the session in the username, so a typical configuration looks like this:
# per-request rotation: a new IP for every request
curl -x gate.shifter.io:8080 -U "customer-USER:PASS" https://example.com
# sticky session: same IP for the life of session id abc123
curl -x gate.shifter.io:8080 -U "customer-USER-session-abc123:PASS" https://example.com
# sticky, geo-targeted to Germany
curl -x gate.shifter.io:8080 -U "customer-USER-country-de-session-abc123:PASS" https://example.comChange the session id and you get a new address. Keep it and you keep the address until the window expires. The exact parameter names vary between providers, so check the documentation for the service you use, but the mechanism is consistent.
What Happens to a Session Mid-Rotation
This is the part most explanations skip, and it is the cause of most rotation-related failures.
A logged-in session is a cookie the site issued to a browser at a particular address. If the next request arrives with the same cookie from a different country, the site sees a session that teleported. Depending on how careful the site is, you get re-authentication, a security challenge, or the session invalidated entirely.
Rotation does not know or care that you are logged in. It is your responsibility to hold an address for as long as the session needs one. If a flow takes four minutes, a five-minute sticky window covers it. If an operation runs for hours, rotation is the wrong tool and an ISP proxy with a permanent address is the right one.
Backconnect Proxies
Backconnect is the gateway architecture that makes rotation possible. Rather than giving you a list of addresses to manage, the provider gives you one endpoint that connects backwards into the pool on your behalf.
It is worth being precise, because this is commonly stated incorrectly, including in an earlier version of this article: backconnect is not a synonym for residential. Backconnect describes how addresses are delivered to you. Residential describes where the addresses come from. They are independent, and backconnect gateways exist for datacenter and mobile pools as readily as for residential ones.
What backconnect gives you in practice:
- One endpoint to configure. Your scraper points at a single host and port for the life of the project, regardless of how the pool changes behind it.
- Automatic replacement. A dead or blocked address is dropped from the rotation without your code noticing.
- Targeting through parameters. Country, city and ASN selection happens in the credentials rather than by maintaining separate address lists.
- No pool management. You never build, test or refresh a proxy list.
The alternative, a static list of individual addresses, means handling all of that yourself, which is why backconnect became the standard delivery model for pools of any size.
What Rotation Is Good For
These are the benefits of rotation specifically, as distinct from the benefits of residential IPs generally.
- Defeating per-IP rate limits. A limit of 60 requests an hour per address becomes effectively unlimited across a large pool. This is rotation’s single clearest win.
- Sustaining large collection jobs. Volume that would burn one address is invisible when divided across thousands.
- Surviving individual blocks. When an address gets blocked, the next request simply uses another one. Nothing to detect, nothing to fix.
- Sampling many locations cheaply. Checking prices or ads across 20 countries needs no per-country purchase, only a parameter change per request.
- Reducing pattern signals. A single address making a request every 10 seconds around the clock is a machine. The same traffic spread across a pool is not.
What rotation does not do is make untrusted addresses trusted. Rotating datacenter IPs against a site that classifies address ownership fails on every address in the pool. Rotation is about distributing volume, not about earning trust.
When to Use Rotation, and When Not To
Use rotating proxies for: web scraping and price monitoring, SERP and rank tracking, ad verification across regions, availability and stock checks, and large-scale data collection for AI training or grounding.
Use static or ISP proxies for: account management, anything logged in for long periods, ad platform access, and any operation where being recognised as the same visitor is the point.
The two articles worth reading next depend on which side of that you land. For the full comparison, static vs rotating proxies covers the trade-off in detail. For choosing a proxy type by target, see web scraping proxies.
Conclusion
Rotation is a session-length setting, not a product category. Per-request rotation spreads independent traffic across a pool and is the right default for collection. Sticky sessions hold an address as long as your flow needs it. Backconnect is the gateway that delivers both from a single endpoint.
Get the rotation interval right for the work and most block problems disappear. Get it wrong in either direction and you either break sessions or concentrate traffic where it gets noticed.
Shifter’s residential proxies support both modes with country, city and ASN targeting, and current rates are on the pricing page.