Proxy rotation is a change of the external IP address with no change to the settings on your side: you keep connecting to the same host and port while the target site sees different addresses. It is for anyone who sends many requests to one site (scraping, price monitoring, SERP checks) or runs several accounts and wants to spread them across addresses.
In this article we look at what proxy rotation is technically, what modes exist, how a sticky session differs from per-request rotation, and why rotation is essential for some tasks and must be switched off for others. ProxyFarm's rotating pools start at 1 490 ₽ (≈ $16) a month, a shared mobile channel from 490 ₽ (≈ $5).
Rotating proxies: what they are and how they differ from static ones
A static proxy is a single address assigned to you for the whole rental period. A dedicated IPv4 at 79 ₽ a month is the classic example: whatever address you are issued, you work with it until the paid period ends. The site sees the same IP on every request.
A rotating proxy is a gateway. You connect to a single address like gate.example:9000, and the gateway sends your traffic out through a pool of addresses, changing the exit IP according to a set rule. Nothing changes for your software: same host, port, username and password. What changes is what the target site sees.
The pool can be anything: mobile addresses of one carrier for a mobile proxy, home IPs from 48 countries for a residential one, a set of datacenter IPv4s for rotating proxies at 1 490 ₽ a month. The change rule is what distinguishes one rotation mode from another.
Three rotation mechanisms: how each one works
In practice there are three ways to change an IP, and providers usually support two or all three at once.
| Mode | How it works | Who controls it | Where it is used |
|---|---|---|---|
| By timer | The gateway changes the IP itself at a set interval: 1, 5, 10, 30 minutes. All connections after the change come from the new address | The provider, per your dashboard setting | Background scraping and monitoring where the change frequency is known in advance |
| By link (API) | You send a GET request to a special URL and the IP changes within 3–10 seconds. Until you call it, the address stays put | You or your script | Multi-accounting: change the IP, log into the next account. Scraping that reacts to captchas |
| Per request | Every new TCP connection gets a random IP from the pool. Two requests in a row, two different addresses | Automatic, no settings | Bulk data collection with no sessions or logins |
ProxyFarm's mobile proxies support the first two modes: the timer interval is set in the dashboard, and the change link is issued together with the credentials. Rotating proxies at 1 490 ₽ work in the third mode. Residential proxies work in the third mode or in sticky-session mode, described below.
IP change by link: how it works and how to build it into a script
The most flexible mode. Along with your credentials you receive a URL like https://api.provider/change?key=abc123. Calling that address from a browser, curl or a script switches the modem to a new IP from the carrier's pool. The response is usually JSON with the new address or a status.
How to build it into your workflow:
- Before logging into an account, call the link and wait for an “ok” response or the new IP in the response body.
- Wait 5–10 seconds: the modem is reconnecting to the network, and connections may drop in the first few seconds.
- Verify the new address with a request to api.ipify.org through the proxy and make sure it differs from the previous one.
- Do your work in the account. Do not call the link in the middle of a session.
- After logging out, make the next call and open the next profile.
Limitations worth knowing: most providers enforce a minimum interval between calls, usually 30–60 seconds, so the modem is not overloaded. The new IP is not guaranteed to be unique: the carrier assigns an address from its pool, and after a few changes you may get one you have seen before. For mobile networks this is normal: every address has thousands of subscribers behind it anyway.
Sticky sessions: when the IP needs to hold
A sticky session is a compromise between per-request rotation and a static address. The gateway pins one IP to your session for a set time, up to 30 minutes on ProxyFarm's residential proxies, and then changes it. Within that window all requests come from one address, and the site sees coherent user behaviour.
Technically the session is usually bound through a parameter in the username: user-session-abc123 or user-sid-12345. As long as the session string in the username stays the same, the IP stays the same. Change the string and you get a new address. This lets a single script hold dozens of parallel sessions with different IPs.
Where sticky sessions are needed:
- Cart and checkout on a marketplace: an IP change between adding an item and paying will reset the session or trigger a check.
- Authenticated scraping: the login and the pages that follow must come from one address.
- Verifying ads and multi-step funnels: ad click, landing page, form.
- Any scenario with cookies where the site ties the session to the IP.
Where rotation is needed and where it hurts
Rotation is not a universal upgrade. It solves one problem, the request limit per address, and creates another if the platform expects consistency from a user.
Rotation is needed for:
- Scraping catalogues, search results and product pages: thousands of requests an hour, and the site throttles by frequency per IP. Per-request rotation spreads the load. More on the proxies for scraping page.
- Monitoring competitors' prices and stock across dozens of regions.
- Checking Yandex and Google rankings from different cities.
- Multi-accounting: rotation between sessions so that each account gets its own address.
Rotation hurts:
- Inside an account session on a social network, on Avito (Russia's largest classifieds site) or in Telegram: a user does not change cities every five minutes. The platform will respond with a verification request or log you out.
- During payment and checkout: payment anti-fraud compares the IP at every step.
- In long uploads and downloads: an IP change will break the connection.
- When working with APIs where the token is bound to an address.
A practical rule: if the task is “many identical requests with no login”, use per-request rotation or a short timer. If the task is “working inside an account”, rotate only by link between sessions or use a sticky session.
How to choose rotating proxies for your task
Three ProxyFarm products support rotation, each with its own pool type and pricing model.
- Mobile proxies: from 490 ₽ a month for a shared channel, 2 500 ₽ for a dedicated device. Rotation by link and by timer, unlimited traffic, addresses from MTS, Beeline, MegaFon and Tele2. The choice for accounts.
- Rotating proxies on datacenter IPv4: from 1 490 ₽ a month, one port, a new IP on every request, no traffic limit. The choice for scraping and monitoring where the platform does not care about IP type.
- Residential proxies: from 290 ₽ per GB, per-request rotation or sticky sessions up to 30 minutes, 48 countries with city-level targeting. The choice for foreign platforms and geo tests.
Before committing to a month, test the mode on a short term: a mobile channel is free for an hour, the other types can be rented for 1 day. Within a day you will know whether the platform tolerates the chosen change frequency and whether sessions hold.
Related questions
What is proxy rotation in simple terms?
It is an automatic change of the IP address your traffic exits from, while your connection settings stay the same. You work with one host and port, and sites see different addresses: on a timer, on your command through a link, or on every new request.
How does the IP change by link work on mobile proxies?
You call the URL you were issued, and the modem in the farm reconnects to the carrier's network and gets a new address from its pool. It takes 3–10 seconds. An interval of 30–60 seconds between calls is usually required. The address is not guaranteed to be unique: the carrier may reissue an IP you have had before.
How does a sticky session differ from rotation by timer?
With a timer the IP changes for all connections at once on the provider's schedule. In a sticky session the address is pinned to a specific session that you define with a string in the username, and holds for up to 30 minutes; you can run many sessions with different IPs in parallel. Sticky is more convenient for scenarios with a cart or a login.
Do I need rotation for a single account?
No. A single account needs a permanent address: a dedicated IPv4 or a mobile channel without rotation inside the session. Rotation pays off when you have several accounts or when the task is bulk requests without logging in.