Proxy rotation

Also called: rotating proxy, sticky session.

A rotating endpoint hands you a different exit address on some schedule: every request, every few minutes, or whenever the provider's pool decides. A sticky session is the opposite arrangement — one address held for a stated period, sometimes hours — and a dedicated IP holds one indefinitely. Providers sell all three off the same pool, and which one you are on is usually a choice of hostname or port rather than a different product.

This is the single most expensive mistake in the category and the easiest to avoid, because the two jobs want opposite settings. Fetching public pages at volume wants rotation, so no one address carries the whole load. A signed-in account wants the opposite: a session whose address changes mid-scroll looks like a hijacked session, because that is exactly what a hijacked session looks like, and the platform's response is a verification cycle at best. Ask a vendor how long a sticky session actually holds before it rotates anyway. Argus assigns a proxy per profile and applies it at the network layer on every launch, so the address is part of the profile's identity rather than a global setting — the proxies page covers both cases.