Rotating Datacenter Proxies, Priced per GB or Unmetered

# The gateway picks an exit for each connection (each curl call opens one)
for i in 1 2 3; do
  curl -s -x http://USER:PASS@gw-rotating_datacenter.node4.io:8083 https://api.ipify.org
  echo
done

# Hold one exit IP for a multi-step flow
curl -x http://USER-session-482913:PASS@gw-rotating_datacenter.node4.io:8083 \
  https://api.ipify.org

# Same product over SOCKS5 - same credential, different port
curl --socks5-hostname USER:PASS@gw-rotating_datacenter.node4.io:1083 https://api.ipify.org

import requests

HOST = "gw-rotating_datacenter.node4.io"
USER, PASS = "user-42-abc123", "your-password"

# Rotation per connection: each requests.get() opens a new one
rotating = {"https": f"http://{USER}:{PASS}@{HOST}:8083"}
for _ in range(5):
    print(requests.get("https://api.ipify.org", proxies=rotating).text)

# Sticky: same exit for a login or cart flow
sticky = {"https": f"http://{USER}-session-482913:{PASS}@{HOST}:8083"}
with requests.Session() as s:
    s.get("https://example.com/login", proxies=sticky)
    s.get("https://example.com/account", proxies=sticky)

// `dispatcher`, not `agent`. With { agent } fetch routes nothing and all
// five of these requests leave from the same address: your own.
import { fetch, ProxyAgent } from "undici";

const base = "gw-rotating_datacenter.node4.io:8083";
const dispatcher = new ProxyAgent(`http://USER:PASS@${base}`);

for (let i = 0; i < 5; i++) {
  const res = await fetch("https://api.ipify.org", { dispatcher });
  console.log(await res.text()); // an exit picked per connection; a kept-alive tunnel reuses its exit
}

How often does the IP change?

The gateway picks an exit when an HTTPS tunnel or SOCKS5 connection opens, and for each plain-HTTP request. An HTTPS client that keeps its CONNECT tunnel alive reuses the same exit until it closes the connection. Each pick is drawn from the pool, so it can repeat an address you had earlier. Add a session identifier to hold one exit deliberately, for up to 30 minutes measured from when the pin is first assigned.

What is the difference between rotating and residential?

Rotating proxies rotate through datacenter IPs that Node4 owns: fast, cheap per gigabyte, and fine wherever datacenter ranges are accepted. Residential rotates through real consumer connections, which is what you need when datacenter ranges are blocked.

Do I need to manage an IP list?

No. You connect to one gateway hostname and port; selection happens behind it.

Is bandwidth shared between the rotating plans?

No. Each plan has its own allowance and its own endpoint. Rotating Unmetered has no bandwidth allowance at all; what it caps is concurrent connections.

Do you offer rotating proxies with unlimited bandwidth?

Yes. Rotating Unmetered is a rotating datacenter product with unlimited bandwidth, priced by the number of connections you hold open at once instead of by the gigabyte. We can charge for concurrency instead of bytes because these exits are datacenter addresses on blocks we own, so the bytes are not bought from a supplier by the gigabyte. What you give up is a ceiling on simultaneous connections, so a bursty workload is sized by its burst rather than its average. If your volume is modest and your concurrency is low, the per-GB plans are cheaper and remain on sale.

How many concurrent connections can I run?

On Rotating Datacenter, the per-GB plan, there is no plan-level cap on concurrent connections; a per-source-IP safety limit still applies across the platform. On Rotating Unmetered, concurrency is what you buy: the size you pick is a ceiling the gateway enforces rather than a threshold that bills extra, and with no per-GB charge there is no overage. Size it by the burst rather than the average, since a job that opens many connections briefly needs a larger plan than its mean would suggest.

Does rotating help if the site already blocks datacenter IPs?

No. Rotation changes which address you arrive from, not what kind of address it is; a target that classifies hosting ranges will classify every exit in this pool the same way. That workload belongs on residential, which rotates through consumer connections on the same one-endpoint design. Rotating datacenter is for targets that accept hosting traffic but enforce per-IP limits on it.

Can I use IP whitelist authentication on the gateway?

Yes. On the rotating gateways, register your address and connect with no credentials for an untargeted exit, or send the username with an empty password to keep country targeting and session pinning, which are declared in the username on every connection. IP whitelisting is available on every product; on the residential gateway there is no empty-password option, so a whitelisted residential connection gets an untargeted exit and you use credentials whenever you need targeting.

Which countries can I rotate through?

The United States, Italy and Spain, where our owned blocks sit; a country segment constrains exits to any of those markets. If your workload needs other geographies, that is residential territory (170+ countries with state and city targeting).

Does rotation work for logged-in or multi-step flows?

Yes, with a session. Pin a session id and one exit is held for up to 30 minutes, which covers most flows; a longer one should mint a fresh session id and carry on. The usual pattern is rotation for discovery and a session per login, checkout or paginated read, all through the same endpoint and credential, chosen per connection by the username.

What does a burned exit cost me here?

A retry. In rotation, a target blocking one address affects only the connections that land on it. In a session, retire the session id and the next pick comes from the pool again. The exception is a target that refuses hosting ranges as a class; rotation within a datacenter pool does not recover from that.

Is there anything to install or configure?

No software, no IP lists, no rotation timers. Anything that speaks to an HTTP or SOCKS5 proxy (cURL, a scraping framework, a headless browser, an HTTP library) points at the gateway hostname and port with your credential. The code samples below are complete working configurations.