Rotating proxies
A connection that changes its outbound address automatically — every request, or on a timer you choose.
Pick this when
Each request stands alone.
- Accepted values
- -1 for every request, or 5, 10, 15, 20 or 60 minutes
- If you omit it
- The network applies its default of 15 minutes
- Anything else
- Rejected outright, never silently rounded to a nearby value
- Scope
- The connection, not the account — two jobs can rotate differently at once
How it works
Rotation is set when you build the connection, not on your account, so different jobs can rotate differently using the same credentials.
Per-request rotation gives each request a different address. It spreads traffic widely and is the right default for stateless collection.
Timed rotation holds an address for a fixed window — 5, 10, 15, 20 or 60 minutes — which keeps a short workflow coherent without pinning you to one IP for the whole job. Leave rotation out entirely and the network applies its own default of 15 minutes, which is rarely what you meant.
How it differs
Against its nearest neighbours, by name. If one of these describes your situation better, the row is a link.
Where it fits
Use it for
- Stateless collection where each request stands alone
- Spreading volume so no single address carries a disproportionate share
- Multi-step flows that must stay on one address briefly, using a timed window
Do not use it for
- Logged-in sessions that must persist longer than the rotation window — use a sticky session instead
- Flows where a mid-sequence IP change would invalidate a cart, token or checkout step
Rotate as fast as the workflow allows. The moment a target needs continuity across requests, a rotating connection starts breaking your session rather than protecting it.
A real connection
One credential pair covers everything. Type, country, rotation and session all travel inside the username, so you never provision a second proxy user to change one of them.
user-USERNAME-type-residential-country-es-rotation-10Accepted rotation values are -1 for per-request, 0 for sticky, and 5, 10, 15, 20 or 60 minutes. Anything else is rejected by the network rather than silently rounded.
Questions
- How fast should I rotate?
- As fast as the workflow tolerates. Per-request is right for independent page fetches. The moment a sequence of requests shares server-side state, rotation starts breaking it.
- Can different jobs rotate differently?
- Yes. Rotation is a property of the connection, not the account, so the same credentials can run per-request rotation for one job and a 60-minute window for another at the same time.
- Does rotating cost more than staying on one IP?
- No. Billing is by the byte, so rotation is free — the choice is purely technical.
- What happens at the end of a rotation window?
- The next request goes out from a different address. Anything the destination was holding against the previous address — a session, a cart, a token — will not follow it.
The same on every type
These four do not vary by proxy type, so they are worth stating once rather than six times. One balance covers all of it.
- Protocols
- HTTP, HTTPS and SOCKS5
- Targeting
- Country, then state or city; ASN by number
- Rotation
- Per request, sticky, or 5 / 10 / 15 / 20 / 60 minutes
- Rate
- $2/GB, sent plus received
Where this comes up
- Web scrapingMost scraping failures are not IP problems. Work out which one yours is before you change the IP class, because changing it is usually not the fix.
- Price monitoringA price is only meaningful alongside where it was observed. Get the location wrong and you are monitoring a number nobody is actually offered.
- Ad verificationAd servers make targeting decisions from the requesting IP. Verify from the wrong IP class and you measure a placement no real user ever saw.
- SERP and SEO monitoringThere is no single ranking for a keyword. There is a ranking in a place, and you have to look from that place to see it.
Where the address comes from
Pick exactly one.
- IP classResidential proxiesThe target rejects hosting ranges but does not need a carrier address.
- IP classDatacenter proxiesNothing is blocking you yet, or a predictable round trip matters more than provenance.
- IP classMobile proxiesResidential was rejected too, or the platform expects a carrier address.