IP rotation is the practice of sending outgoing requests through a pool of IP addresses and switching the source IP on a set rule: every request, every few minutes, per session, or when a block is detected. Spreading traffic this way keeps each IP's request volume lower, so per-IP rate limits and bans affect less of the job.

How aggressively to rotate is a tradeoff: rotating too frequently can break workflows that need a consistent session, like staying logged in, while rotating too rarely raises the odds any single IP gets flagged or banned before the job finishes.

Types of IP Rotation

  • Per request: every request gets a new IP. This suits independent page fetches.
  • Timed: the IP changes at a fixed interval, such as every few minutes.
  • Per session (sticky): one IP is held for a session and then replaced. This suits logins and carts.
  • On block: an IP is kept until it starts returning errors or rate-limit responses, then it is swapped from the pool.

Why Rotation Alone Isn't Enough

A new IP doesn't change everything else a site can see. Sites can link requests through a device fingerprint built from signals such as the User-Agent header, screen size, installed fonts, canvas rendering and TLS characteristics. A fingerprint can identify a client even when its IP is hidden or cookies are blocked. Keep headers, fingerprint and request timing consistent for each IP, and keep sessions intact where a site expects them to persist.