How IP Rotation Works at Hex Proxies

IP rotation is the process of changing the exit IP address used for proxy requests. The goal is to distribute requests across many IPs so that no single IP accumulates enough requests to trigger rate limits or blocks. Hex Proxies offers multiple rotation modes to match different use case requirements, and our rotation engine is built into the routing layer of our network architecture.

Rotation Modes Explained

Per-Request Rotation

In per-request mode, every HTTP request exits through a different IP address. This is the most aggressive rotation mode and provides the highest level of IP diversity. It is ideal for large-scale data collection where each request is independent and there is no need for IP consistency between requests.

Our per-request rotation draws from the full available pool for your selected region and proxy type. The selection algorithm avoids recently used IPs and prioritizes IPs with the highest reputation scores. Rotation happens at the routing layer and adds less than 10 milliseconds of overhead to request processing.

Timed Rotation

Timed rotation assigns you an IP for a configurable duration, typically between 1 and 30 minutes. All requests during that window exit through the same IP. When the timer expires, the system assigns a new IP from the pool automatically. This mode is useful for workflows that require multiple requests to the same target within a short window, such as navigating a multi-page website or completing a checkout flow.

Smart Rotation

Smart rotation is our most advanced mode. Instead of rotating on a fixed schedule, the system monitors target responses for early indicators of detection or rate limiting. These indicators include soft blocks (CAPTCHAs, cookie challenges), increased response latency, and changes in response content that suggest throttling. When the system detects these signals, it rotates the IP proactively before a hard block occurs.

Smart rotation requires our routing engine to inspect response headers and status codes in real time. This adds approximately 20 milliseconds of overhead but can dramatically improve success rates on targets with aggressive anti-bot systems.

Sticky Sessions

Sticky sessions are the opposite of rotation: the system maintains the same IP for as long as possible, up to the maximum session duration (typically 30 minutes, configurable up to 24 hours for ISP proxies). Sticky sessions are essential for use cases that require IP consistency, such as logging into accounts, maintaining shopping carts, or any workflow where a mid-session IP change would cause failure.

The Rotation Engine

Our rotation engine runs in the routing tier of our network. When a request arrives, the engine checks the session configuration to determine which rotation mode applies. For per-request mode, it selects the best available IP from the pool. For timed and sticky modes, it looks up the existing session binding and reuses the assigned IP if it is still healthy.

The engine maintains a real-time index of every IP in the pool with its current state: available, assigned, cooling down, or retired. This index is distributed across all routing nodes and updated within milliseconds when any IP changes state.

Rotation and IP Health

Rotation is tightly integrated with our IP health scoring system. When an IP is used for a request, its health score is updated based on the result. Successful requests improve the score; failures degrade it. IPs that fall below the health threshold are automatically removed from the rotation pool and placed in a cooldown period. This feedback loop ensures that the rotation engine always draws from the healthiest available IPs.

Configuring Rotation

Rotation mode is configured per-session through our gateway API. You can set rotation mode using URL parameters, request headers, or dashboard presets. Switching between rotation modes does not require reconnecting or re-authenticating. The configuration takes effect on the next request.

Best Practices

For maximum success rates, match your rotation mode to your use case. Use per-request rotation for independent data collection tasks. Use timed rotation for multi-page browsing sessions. Use smart rotation when targeting sites with known anti-bot protection. Use sticky sessions for account management and checkout flows. Avoid using sticky sessions for high-volume collection, as it concentrates traffic on a single IP and increases detection risk.