Rotating Proxy

A rotating proxy is a proxy endpoint that gives you a different exit IP from a shared pool, either on every request or every few minutes. You connect to one address that never changes; the provider quietly swaps the IP behind it.

The value is arithmetic. A site that blocks any visitor making 100 requests an hour will certainly block one address making 10,000. Spread those same 10,000 requests across 5,000 IPs and each one looks like a person who dropped by twice.

How the gateway works

You are not handed a list of IPs to cycle through yourself. The provider gives you a single backconnect gateway — something like gate.provider.com:7000 — and rotates the exit address behind it. Your scraper's configuration never changes; what the target site sees changes constantly.

That design is why rotation is easy to adopt. One host, one port, one set of credentials, and the entire pool is available. It also means the provider is responsible for retiring dead and burned addresses, which is the tedious half of running your own list.

Per request, or per session

Two modes cover nearly every job:

• Rotate on every request — a new IP for each call. Correct for stateless crawling: product pages, search results, listings, anything where no request depends on the one before it.
• Sticky sessions — one IP pinned to you for a fixed window, typically 1 to 30 minutes, usually requested by adding a session ID to your proxy username. Required for anything with state: logging in, filling a basket, paginating through a filtered result set.

Choosing wrongly here is the most common rotation mistake. A checkout that begins in Texas and finishes in Poland fails not because the IPs were poor quality but because the journey was impossible.

Rotation is a property of the endpoint, not the pool

"Rotating" describes how addresses are assigned; it says nothing about where they come from. Any pool can rotate, and the pool is what determines trust, speed, and price.

• Rotating residential — real home ISP addresses, the highest trust and the usual choice for protected targets. Slower and billed by bandwidth.
• Rotating datacenter — fast and cheap, often sold with unlimited traffic, but easy for anti-bot systems to identify by ASN.
• Rotating ISP — datacenter speed with residential registration, rotated across a smaller pool.
• Rotating mobile (4G/5G) — carrier addresses shared by thousands of real handsets through CGNAT, the hardest to block and the most expensive.

What rotation does not fix

A new IP resets one signal. It does not reset the rest of your identity, and modern bot detection weighs several at once.

• Cookies and local storage carry across a rotation unless you clear them, re-identifying you instantly.
• Browser fingerprint and TLS fingerprint stay identical whichever IP you exit from.
• Behaviour — 60 requests a minute in perfect rhythm reads as automation from any address. Rotation should be paired with throttling, not used as a substitute for it.

Rotating an IP while keeping one fingerprint and one cookie jar is actively worse than not rotating, because a single visitor appearing from hundreds of countries is a pattern no real user produces.

What it costs

Rotating residential and mobile pools are billed by gigabyte, so the size of the pages you fetch drives the bill more than the number of requests. Blocking images, fonts, and third-party scripts in your scraper is the single largest saving available. Datacenter pools are usually billed per port or per thread with generous or unlimited traffic, which is why they remain the default for high-volume crawling of soft targets.

Free rotating endpoints exist, and they are shared with everyone else using them — expect addresses already blocked by the sites you care about. Most reputable providers offer a small paid trial instead, which is the honest way to test whether a pool works against your specific targets.