What is a rotating proxy and how does it work?

A rotating proxy automatically assigns a different exit IP to each request or on a set schedule, so the target site sees traffic from many addresses instead of one. Nodetonet rotates through a pool of real 4G/5G mobile-carrier IPs from your paired Android devices, with health-aware selection on every connection.

What is the difference between rotating and sticky proxies?

A rotating proxy gives a new exit IP over time for maximum identity spread. A sticky proxy pins one IP to a session for a set time-to-live, keeping multi-step flows (login, checkout) on the same address. Nodetonet does both from a single proxy: add a -session-XXXX suffix to your username for sticky, omit it for rotating.

Can I trigger IP rotation from code or automatically on a block?

Yes. The on-demand rotation mode lets you trigger a new IP via the REST API, a public reset link, or the panel — so your scraper can call the reset endpoint the moment it detects a block. Timed mode handles automatic rotation without any external trigger.

What happens if a device in my pool goes offline mid-job?

Health-aware selection automatically skips offline or saturated devices, and automatic failover moves active traffic to a healthy device in the pool — with no manual action required. The failed device is re-added to rotation once it comes back online.

Can I target a specific country, city, or mobile carrier with a rotating proxy?

Yes. Nodetonet lets you append country, city, or carrier modifiers directly to the proxy username (e.g. -country-tr or a specific carrier name) without changing the endpoint. The pool selection then filters to only devices matching that criteria. See the geo-targeting feature page for the full syntax.

How do per-client controls work on a shared rotating proxy?

Each proxy client gets its own username/password, bandwidth quota, thread limit, expiry date, and IP/domain restrictions — all enforced at the edge without a panel round-trip. This makes it safe to share or resell a rotating pool: one customer cannot exceed their quota or reach resources outside their domain allowlist.

Do rotating proxies support HTTP and SOCKS5?

Yes. Nodetonet serves rotating proxies over both HTTP/HTTPS and SOCKS5 from the same device pool. Use HTTP for browsers and most scrapers, SOCKS5 for raw TCP traffic or non-web applications. Both support username/password authentication.

What is the cost model for Nodetonet rotating proxies?

Nodetonet uses prepaid credit with no monthly subscription. You pay only when traffic flows — an idle proxy costs nothing. There is no per-GB surcharge on top of device cost, and you own the devices, so the long-run cost per gigabyte is far lower than renting a residential pool billed per GB.

Rotating proxies — automatic IP rotation with sticky-session control

A rotating proxy gives you a different exit IP over time instead of one fixed address — so a target site sees many distinct visitors rather than a single client hammering from one IP. Nodetonet rotates through a pool of real 4G/5G mobile-carrier IPs sourced from your paired Android devices, giving you full, granular control over when and how the rotation happens — with the ability to snap into a sticky session at any moment.

TL;DR: pair Android phones once, configure a token group, choose a rotation mode, and your rotating mobile proxy pool is live — no subscription, billed on prepaid credit only when traffic flows.

Why rotation matters for modern scraping

Anti-bot systems track request frequency, timing, and behavioural patterns per IP. Once an address exceeds a threshold — too many requests too fast, or the same fingerprint appearing in unrelated sessions — it gets flagged or blocked. Rotating proxies break that pattern: each request (or burst of requests) appears to come from a fresh address, dramatically reducing the chance any single IP accumulates enough signal to trigger a block.

Residential IPs help, but mobile proxies are an order of magnitude harder to block. Carrier-grade NAT (CGNAT) places thousands of real paying subscribers behind the same public IP at any given moment. Banning that IP means banning thousands of innocent customers — so anti-bot vendors actively avoid it. When you rotate through a mobile pool, every exit address carries that built-in trust.

Three rotation modes

Nodetonet gives you three distinct modes so you can match rotation behaviour to your exact workflow:

Per request — every new connection picks a fresh device and IP from the pool. Maximum spread and diversity. Ideal for broad crawls, ad verification sweeps, and SERP monitoring where each page fetch should look independent.
Timed — hold one IP for a configurable interval (e.g. 30 s, 2 min, 10 min), then rotate. Good balance of stability and freshness: the current IP builds a tiny browsing history before switching, which looks natural to session-tracking targets.
On demand — the pool stays on one IP until you explicitly trigger a rotation: via the panel, a public reset link, or the REST API. Suits scrapers that rotate only after a block signal, or tools that need deterministic timing.

Sticky sessions when you need one IP to hold

Pure rotation is great for stateless requests but it breaks multi-step flows — logging in, adding to cart, confirming an order — that expect a consistent IP throughout. Nodetonet solves this without a separate proxy: append a -session-XXXX suffix to your proxy username and the platform pins that session to one device for a configurable TTL. When the TTL expires the slot releases back to the pool.

This means you can rotate by default and go sticky only for the steps that need it, all on the same endpoint. No endpoint switching, no extra credentials. Read sticky sessions explained for a full walkthrough, or when to use rotating mobile proxies to decide which mode fits your use case.

Smart pool management

A pool is only as good as the logic that selects the next device. Nodetonet runs health-aware selection on every single connection:

Token groups bundle many Android phones into one logical pool behind a single endpoint. Add or remove phones without touching your tool configuration. Learn more at token groups: creating pools.
Least-connections selection routes each new request to the device with the fewest active tunnels, avoiding hot spots and spreading load evenly across the fleet.
Health-aware skipping automatically excludes devices that are offline, failing health checks, or saturated — so a dead phone in your fleet never causes a request to hang.
Automatic failover moves traffic off a device that drops mid-job to a healthy one, with no manual intervention. See automatic failover for mobile proxies for detail.
Unique-IP mode avoids handing out the same IP twice in a row when maximum identity diversity matters — useful for account-creation and multi-seat workflows.
Round-robin distributes requests evenly by index when you want predictable ordering rather than load-weighted selection. See round-robin device selection.

Geo and carrier targeting

A rotating IP is not just "somewhere mobile" — it carries a real country, city, and carrier. Because Nodetonet devices are real phones on real SIMs, you can target any combination of those attributes with username modifiers, without changing the proxy endpoint. Target a Turkcell, Vodafone, or Türk Telekom exit, or pin to Istanbul, on a rotating pool just as easily as on a single device. Full syntax is documented in geo-targeting.

HTTP and SOCKS5 — your choice

The same rotating pool is accessible over both HTTP/HTTPS and SOCKS5. Use HTTP for browsers, scrapers, and tools that handle CONNECT tunnelling natively. Use SOCKS5 for raw TCP or UDP traffic — game clients, custom tooling, or anything outside the web stack. Both modes support per-client username/password auth. Unsure which to pick? Read HTTP vs SOCKS5.

Rotating vs other proxy types — comparison

Here is how rotating mobile proxies on Nodetonet sit relative to other common approaches:

Approach	IP quality	Rotation control	Sticky sessions	Cost model	Best for
Nodetonet rotating mobile	Real 4G/5G CGNAT IPs	Per-request / timed / on-demand	Yes — `-session-XXXX` suffix	Prepaid credit, no subscription	Scraping, ad verification, multi-account
Rented residential rotating	Home ISP IPs, shared pool	Per-request (provider-controlled)	Provider-dependent	Per GB ($8–15)	Broad geo coverage
Datacenter rotating	Cloud/server IPs	Per-request	Rare	Per IP / month	Unprotected targets
Static single IP	Any type	None	Always (single address)	Per IP / month	Logins needing one fixed identity

For a detailed head-to-head against specific commercial providers, see Nodetonet vs Bright Data, vs Smartproxy, vs Oxylabs, and vs IPRoyal.

Per-customer access controls

Rotating proxies can be resold or shared safely. Every proxy client (a customer or sub-user) gets independent controls enforced at the edge:

Dedicated username and password — clients never share credentials.
Bandwidth quota with a configurable limit and hard-stop at the cap. See quota limits per client.
Thread limit — cap concurrent tunnels per client to prevent one customer from saturating the pool. See thread limits per client.
Expiry date — a client automatically stops working after a set date. See time-limited proxy clients.
IP and domain allow/deny lists — restrict which source IPs may connect, or which destination domains the client can reach. See IP allow/deny lists.

All of these are managed from the panel and enforced at the edge with no per-request panel round-trip. If you are building a reseller or white-label operation, see the reseller feature for the full picture.

Upstream forwarding

Need to chain out through an external residential or datacenter provider? Nodetonet's upstream forwarding lets you point a rotating proxy at an external backconnect endpoint. This is useful when you need geographic reach that your own device fleet does not yet cover. See upstream residential forwarding and upstream username modifiers for setup.

Monitoring and bulk operations

When you manage a large rotating pool, visibility and batch control matter. The Nodetonet panel surfaces per-pool live throughput, active-connection counts, and per-device health badges. Need to rotate the IP across fifty devices at once or restart a fleet segment? Bulk operations covers the panel UI and REST API for doing exactly that at scale.

Get started in minutes

Install the Android agent app on one or more phones and pair each to your panel via token. See your first token and Android pairing if this is your first device.
Group the devices into a token group in the panel — this is your rotating pool.
Create a rotating proxy bound to that token group, choose a rotation mode (per-request / timed / on-demand) and set an optional sticky TTL.
Point your tool at the proxy endpoint with your credentials. Add -session-XXXX to the username only for the requests that must stay on one IP.
Add per-client credentials if you are sharing the pool with customers.

Ready to start? Create a free account, or read the end-to-end walkthrough in setup a rotating mobile proxy from scratch. Questions? Reach us at support@nodetonet.com or on Discord.