Rotating datacenter proxies

Rotating datacenter proxies automatically assign a datacenter IP to each request or session. They combine fast connections, simple geo-targeting, and traffic-based pricing for public web data collection.

Use them when a task needs frequent IP changes without managing a static proxy list. They suit price monitoring, SEO research, market research, and other workflows where speed matters more than residential identity.

A rotating session changes the IP across requests, while a sticky session keeps the same IP when you need continuity. Choose how long you want to keep an IP based on the task you are running. You can also set a session lifetime when you need the IP to stay active for a defined period.

Endpoint format

Connect through the Geonode endpoint using this format:

hostname:port:username:password
Hostname: proxy.geonode.io
HTTP/HTTPS ports: 9000-9010
SOCKS5 ports: 11000-11010

Your username can include the selected location and session settings. The password comes from your Geonode dashboard.

Choosing a rotation interval

Use per-request rotation when requests are independent. Use a sticky session when several requests need continuity, such as pagination, a form, or a browsing flow.

Our sessions use a 10-minute lifetime by default. You can set a session duration from 3 minutes to 24 hours, depending on the task.

Rotating access is better when scale and automatic IP changes matter. Static access is better when a task must return through the same address.

Datacenter proxies generally offer higher speed and lower traffic costs. Residential proxies use IPs connected to real consumer networks, which makes them suitable for tasks that need residential routing.

Choose Subscription or Pay As You Go in the pricing table to see the available traffic allowances and rates. This product is billed by traffic in GB.

This product is billed per GB, so bandwidth is not unlimited. The phrase rotating proxies unlimited bandwidth refers to a different pricing model and should not be applied to this traffic-based product.

Flat plans vs per-GB

A flat plan usually charges for a fixed number of IPs and may include unlimited bandwidth. Rotating datacenter access instead charges for the traffic transferred through the proxy.

Choose per-GB billing when you want access to rotating IPs without purchasing each address separately. If you want to buy datacenter proxy access with fixed IPs, check whether a static or ISP-based plan better fits the task.

Why cheap rotating proxies still work for public data

Cheap rotating proxies can work well because datacenter servers provide fast and stable connections without using residential devices. The wholesale pricing model also lowers the cost as the selected traffic volume increases.

The lower price does not remove normal limits set by target websites. Use sensible request rates, retry logic, and concurrency settings when collecting public data.

Datacenter proxies are built for speed because their traffic runs through server infrastructure. Actual performance still depends on the target website, selected location, connection quality, number of threads, and request frequency.

The success rate can change between websites and workloads, so test the target before scaling. IP pool availability and geo-targeting options may also vary by location. We support country, state, and city targeting where matching addresses are available.

Replace USERNAME and PASSWORD with the credentials from your dashboard.

cURL

curl -x "http://USERNAME:PASSWORD@proxy.geonode.io:9000" \
  "https://example.com"

Python

import requests

proxy = "http://USERNAME:PASSWORD@proxy.geonode.io:9000"
proxies = {"http": proxy, "https": proxy}

response = requests.get("https://example.com", proxies=proxies)
print(response.text)

Node.js

const axios = require("axios");
const HttpsProxyAgent = require("https-proxy-agent");

const proxy = "http://USERNAME:PASSWORD@proxy.geonode.io:9000";
const agent = new HttpsProxyAgent.HttpsProxyAgent(proxy);

axios.get("https://example.com", { httpsAgent: agent })
  .then(response => console.log(response.data));

The same endpoint can be used through the API or added to tools that support authenticated HTTP or SOCKS5 proxies.