IP Rotation Best Practices for Mobile Proxies
How to choose the right rotation strategy for your use case — from per-request rotation for scraping to sticky sessions for account management.
What Is IP Rotation?
IP rotation means your traffic exits through different IP addresses over time. With a backconnect proxy, you connect to a single gateway address (host + port), and the proxy server routes each request through a different exit IP from its pool.
For mobile proxies specifically, rotation happens at the hardware level. Each proxy slot is a physical modem with a SIM card connected to a real cellular carrier. When the modem reconnects to the network, the carrier assigns a new IP from its CGNAT pool — the same mechanism that gives regular phone users new IPs.
How it works
Client → Gateway (fixed host:port) → Backconnect server selects exit modem → Modem connects to carrier → Carrier assigns IP from pool → Request reaches target with carrier IP.
Rotation Strategies
| Strategy | How It Works | Best For |
|---|---|---|
| Per-request | New IP for every HTTP request | Scraping, price monitoring, ad verification |
| Time-based | IP changes at fixed intervals (5/10/15/30/60 min) | Ad verification, general automation |
| Sticky session | Same IP maintained for a set duration | Social media, account operations, checkout flows |
Recommended Intervals by Use Case
| Use Case | Interval | Why |
|---|---|---|
| Web scraping | Per-request | Maximum anonymity. Each request appears from a different user. Prevents rate-limiting on target sites. |
| Social media management | 10-30 min sticky | Preserves session state. Platforms expect consistent IPs during a browsing session. |
| Account creation | Per-account sticky | One IP for the entire registration flow. Changing IP mid-signup triggers verification. |
| E-commerce / sneakers | 1-5 min sticky | Maintains session through product selection and checkout. Short enough to retry with a fresh IP on failure. |
| Ad verification | Per-request | See different geo-targeted ads by appearing as different users in different locations. |
How Our API Handles Rotation
You can trigger IP rotation programmatically via the API. Sending a request to:
This triggers a hardware-level modem reconnection. The physical modem disconnects from the carrier network and reconnects, receiving a new IP address from the carrier's CGNAT pool. This is the same process that happens when a real phone toggles airplane mode — the new IP is a genuine carrier IP with full trust.
The reconnection typically takes around 10 seconds. Your integration should wait for the API response before sending new requests through the slot.
HTTP/1.1 Keep-Alive and Rotation
An important detail: HTTP/1.1 connections default to Connection: keep-alive. This means multiple requests can reuse the same underlying TCP connection, and all requests on that connection will exit through the same IP.
For true per-request rotation
Close the TCP connection after each request (set Connection: close header) or create a new proxy connection for each request. Otherwise, HTTP keep-alive will reuse the same exit IP for all requests on the persistent connection.
Common Mistakes
- --Rotating too fast. Cellular carriers rate-limit network reconnections. Triggering rotation faster than every 30-60 seconds can result in the same IP being reassigned or temporary connection failures.
- --Not waiting for modem reconnect. After triggering a switch, the modem needs approximately 10 seconds to reconnect and receive a new IP. Sending requests before reconnection completes will fail or use the old IP.
- --Ignoring keep-alive. As noted above, HTTP/1.1 persistent connections reuse the same exit IP. Failing to close connections between requests defeats per-request rotation.
- --Using sequential IPs. If you rotate through the same small set of IPs in a predictable order, pattern detection can still identify your traffic. Use a pool of slots across different carriers to ensure diversity.
- --Over-rotating for session-based tasks. Social media platforms expect IP consistency within a session. Rotating mid-session triggers security checks. Match your rotation interval to the task duration.
Flexible Rotation, Real Carrier IPs
Per-request, time-based, or sticky sessions — configure rotation to match your exact use case. Every IP is a genuine carrier IP from our modem pool.