Buy rotating IPv4 proxies with automatic IP rotation

Datacenter IPv4 proxies from a pool of over 100,000 addresses. You connect to a single entry point, and our load balancer substitutes a free IP under each request — no device binding, no traffic limit, with payment only for the number of requests. Suitable for marketplace parsing, price monitoring, SERP SEO analysis, and automation where you can't expose the same address.

from $25/1M requests 100,000+ IPs in the pool New IP per request Unlimited traffic Sticky sessions

Infrastructure in numbers

Rotating proxies run on our own hardware in a Tier-III data center. All 100,000+ IPs in the pool have been owned by ProxyElite since 2012 — we don't resell third-party subnets and don't use residential addresses.

10 Gbit/s
Uplink per node
No shaping or FUP
99.8%
Network uptime
24/7 monitoring
100,000+
IPv4 in the rotation pool
Datacenter only, no residential
since 2012
Own data center
N+1 redundancy

What you get when you buy rotating proxies

Technical facts without marketing. Every benefit is a specific parameter that affects the outcome of parsing or automation.

New IP on every request

The load balancer substitutes a free IPv4 from the pool of 100,000+ under each request. Anti-fraud can't build a profile in time — while one address is being checked, the next request is already leaving from another.

Sticky sessions 5/10/30 min

For multi-step tasks (authorization, cart, forms) you can hold a single IP for a set period. Switching between rotation and sticky is done via connection parameters, with no tickets required.

Elite anonymity

Rotating proxies do not forward the HTTP_X_FORWARDED_FOR header and do not expose your real IP. The level is Elite, not Anonymous.

Unlimited traffic

You pay only for the number of requests, not for gigabytes. You can route as much data through the proxy as the task requires — without fear of hitting a traffic limit.

HTTP/HTTPS/SOCKS5

Rotating proxies support HTTP, HTTPS, SOCKS4, and SOCKS5. For parsing, SOCKS5 is more common — it doesn't send extra headers and works with remote DNS.

No IP binding

No whitelist is needed and your external IP doesn't matter. Rotating proxies work from any device — server, mobile, Docker container — via login and password authentication.

Tasks solved by rotating proxies

Rotating IPv4 wins where address binding isn't what matters — protection against frequency-based blocking is. Below are typical ProxyElite client scenarios.

Marketplace parsing

Collecting prices, stock, and product cards. Changing the IP on every request removes frequency limits — the parser doesn't hit 429 and CAPTCHAs after a few minutes of work.

SEO monitoring and SERP

Collecting positions in search results across dozens of regions. IP rotation prevents personalization of results and CAPTCHAs — the data comes out "clean".

Competitor price monitoring

Regular price collection from different platforms. Rotating proxies distribute requests so the target site doesn't associate the requests with a single client.

News and content scraping

Scraping news sites, blogs, forums. A pool of 100,000+ IPs guarantees that a single address won't be used twice within a short period of time.

Ad testing by geo

Testing creatives and ad campaigns from different IPs. Rotation lets you quickly check how a user from the target region will see the ad.

Automation without accounts

Bulk collection of open data without authorization. The ideal scenario for rotating proxies — no session binding, only request frequency matters.

ML data collection

Preparing datasets for machine learning: collecting images, texts, metadata from different sources. IP rotation lifts frequency limits.

Website availability checks

Uptime monitoring and regional availability checks. Rotating IPs let you test a site from different addresses without being blocked for "monitoring".

How a rotating proxy works

The technical mechanics without simplifications. Understand exactly what happens between your client and the target site when working through a rotating IPv4 proxy.

1

Connecting to the gateway

Your client (Python script, Scrapy, ZennoPoster) sends a request to a single entry point — the gateway:port address with login and password authentication.

IP binding (whitelist) is not required — rotating proxies work from any device via login/password.

2

Load balancer picks an IP

The ProxyElite load balancer accepts the request and picks a free IPv4 from the pool of 100,000+ addresses. The selection algorithm is round-robin with load awareness, so a single address is never used twice in a row.

In sticky session mode, the balancer remembers the chosen IP for 5/10/30 minutes — all requests within the session leave from a single address.

3

Routing and response

The proxy replaces the source address with the chosen IPv4 and sends the request to the target site. The X-Forwarded-For header is not forwarded — anonymity level is Elite.

The site responds to the proxy, and the proxy forwards the response to you. One plan credit is debited upon receiving the response (including 4xx/5xx).

4

Rotation on the next request

The next request gets a new IP from the pool. From the target site's perspective, it looks as if different users are reaching it — anti-fraud can't build a profile in time.

If a sticky session is enabled, the IP is kept until it expires, after which rotation resumes. Switching modes is done via connection parameters.

Rotating vs other proxy types

A quick table: when rotating IPv4 is the best choice, and when you should consider Datacenter, personal, or ISP. For a detailed comparison, see the home page.

Parameter Datacenter Rotating Personal ISP
IP type (by whois) Data center Data center (pool) Data center Real ISP
Session stability Fixed IP Rotation / sticky Fixed IP Fixed IP
IP exclusivity Pool Shared pool Only you Pool
Suitable for anti-fraud platforms No No Depends Yes
Price from $0.065/IP $25/1M req $3.68/IP $0.175/IP
Best task Parsing, SEO, DevOps Mass parsing without accounts Personal accounts Arbitrage, multi-accounting
Action Datacenter Choose rotating Personal ISP proxies

Rotating IPv4 proxy calculator

Build a package for your task: number of requests and rental period. Discounts for 3, 6, and 12-month payments. Delivery right after payment.

Rotating proxies
Automatic IP rotation
IP typeDynamic IPv4
ProtocolsHTTP/S, SOCKS4/5
Speed100 Mbit/s – 1 Gbit/s
TrafficPer request
IP bindingNone
AnonymityElite (no headers)
Refund24 hours
Discounts for payment
3 months
-10%
6 months
-15%
12 months
-20%
Pay per request
The plan is counted in requests, not traffic. One request = one credit. Unlimited traffic — you pay only for the number of requests.
Sticky sessions
Support for holding an IP for 5, 10, or 30 minutes for multi-step tasks: authorization, cart, forms. Switch via connection parameters.
Plan validity period
30 days. Unused credits expire at the end of the period. The package can be increased mid-period.
Build a proxy package
Delivery right after payment · 24-hour refund

Pool workflow: from purchase to use

Four steps, each taking less than a minute. No "pending moderation" requests — access to the rotation pool is delivered automatically.

1

Choose a request package

In your personal account calculator, choose the number of requests (from 1M) and the rental period (1/3/6/12 months). You see the total price with discount.

2

Instant access delivery

After payment, the system automatically issues the login, password, and gateway address. You can connect immediately — no waiting, no manual checks.

3

Configure rotation mode

By default — IP rotation on every request. Via connection parameters, you can enable a sticky session for 5/10/30 minutes for multi-step tasks.

4

Monitor credit usage

Your personal account shows the remaining requests in real time. If needed, the package can be increased mid-period, without waiting for renewal.

Connect in 5 minutes

Ready-to-use code examples for the most common scenarios with rotating proxies. Connection details (gateway:port@login:password) are available in your personal account.

bash · HTTP/HTTPS rotating proxy
# Check IP via ProxyElite rotating HTTP proxy
# Every request gets a new IP from the pool of 100,000+
curl -x "http://USER:PASS@GATEWAY:PORT" \
     -L "https://api.ipify.org?format=json"

# Sticky session for 10 minutes (parameter session-10m)
curl -x "http://USER-session-10m:PASS@GATEWAY:PORT" \
     -L "https://api.ipify.org?format=json"
bash · SOCKS5 rotating proxy
# SOCKS5 with DNS resolution on the proxy side (socks5h)
curl -x "socks5h://USER:PASS@GATEWAY:PORT" \
     -L "https://api.ipify.org?format=json"

# SOCKS5 with a 30-minute sticky session
curl -x "socks5h://USER-session-30m:PASS@GATEWAY:PORT" \
     -L "https://httpbin.org/ip"
python · requests + IP rotation
import requests

# Basic rotation: a new IP on every request
proxies = {
    "http":  "http://USER:PASS@GATEWAY:PORT",
    "https": "http://USER:PASS@GATEWAY:PORT",
}

# Sticky session for 10 minutes (for multi-step tasks)
proxies_sticky = {
    "http":  "http://USER-session-10m:PASS@GATEWAY:PORT",
    "https": "http://USER-session-10m:PASS@GATEWAY:PORT",
}

r = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=10)
print(r.json())  # {'ip': '...'} — a new IP every time
node.js · undici (ProxyAgent)
import { request, ProxyAgent } from 'undici';

const agent = new ProxyAgent('http://USER:PASS@GATEWAY:PORT');

const { statusCode, body } = await request('https://api.ipify.org?format=json', {
  dispatcher: agent,
  headersTimeout: 10_000,
});

for await (const chunk of body) {
  console.log(chunk.toString());  // {"ip":"..."} — IP changes on every request
}
php · cURL extension
<?php
$ch = curl_init('https://api.ipify.org?format=json');

curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_PROXY,            'GATEWAY:PORT');
curl_setopt($ch, CURLOPT_PROXYUSERPWD,     'USER:PASS');
curl_setopt($ch, CURLOPT_TIMEOUT,          10);

# Sticky session: use 'USER-session-10m:PASS' instead of 'USER:PASS'
# curl_setopt($ch, CURLOPT_PROXYUSERPWD, 'USER-session-10m:PASS');

$response = curl_exec($ch);
echo $response;  // {"ip":"..."} — a new IP every time
curl_close($ch);
Where to get the details: login, password, and the rotating proxy gateway address — in your ProxyElite personal account → "My proxies" section. For a sticky session, append -session-5m, -session-10m, or -session-30m to the login.

Works with your software

ProxyElite rotating IPv4 proxies are compatible with any tool that supports HTTP/HTTPS/SOCKS5. Listed are the most popular ones — 500+ solutions work in total.

Playwright Scrapy Selenium Puppeteer ZennoPoster BAS Dolphin Anty AdsPower Multilogin Python requests Node.js undici PHP cURL cURL / Wget A-Parser Key Collector Serpstat and 500+ more tools

IP:Port

gateway.proxyelite.biz:8080

Login:Password

user:pass (or user-session-10m:pass)

Format builder

any template with separators

Proxy infrastructure for business

A separate block of conditions for B2B clients: agencies, arbitrage teams, data centers, and SaaS services. We handle legal and financial matters.

Contract and documents

We sign an official contract. We provide invoices, certificates of completion, and closing documents for accounting.

Flexible payment terms

Deferred payment for regular clients. Bank transfer, payment by invoice, cryptocurrencies (BTC, ETH, USDT), and bank cards.

Dedicated manager

Personal account manager with direct contact via Telegram/Slack. Handles subnet allocation, IP replacement, and API integration.

Corporate orders from $1000

Custom pricing on orders from 10M requests. Dedicated IP pools, custom rotation parameters, 99.9% SLA with downtime compensation.

Rotating IPv4 proxies: how they work, tasks, and load estimation

A practical breakdown without generalities: how per-request rotation differs from a static IP, why we don't sell IPv6, and how not to get the package size wrong.

Rotating proxy vs a regular Datacenter proxy: what's the difference

A regular Datacenter proxy is pinned to you for the whole term: one IP, one geolocation, a predictable binding. A rotating proxy works differently — instead of a single address, you get access to the entire pool of Datacenter IPv4, and the system itself decides which address to give for a specific request. Formally, this is the same Datacenter proxy: the same data centers, the same Elite anonymity level without exposing headers. The only difference is the delivery model: a static IP is needed where binding matters (account, session, whitelist), while rotation is needed where you shouldn't expose a single address at high request frequency. Understanding this distinction is the key to choosing the right tool.

Automatic IP rotation on every request and sticky sessions

By default, every new request leaves from a new IP. This is the optimal mode for parsing and any high-frequency data collection: anti-fraud can't build a profile in time, because the profile is new every time. But sometimes you need the opposite mode — to hold a single address for a few minutes. For example, when authorizing on a site, placing an order, or completing a multi-step form, where changing the IP inside one logical session looks suspicious. We support both scenarios: rotation per request and a sticky session with a timer (5/10/30 minutes). You switch between them via connection parameters (the -session-10m suffix in the login), not through support tickets. This is critical for scenarios where changing the IP too often looks more suspicious than one stable address for a few minutes.

A pool of 100,000+ IPv4 addresses: why a margin matters

The pool size directly affects how long you can work without bans. If the pool has 1,000 addresses and you make 500,000 requests a day, each IP is used hundreds of times — anti-fraud will sooner or later link these requests and block the subnet. A pool of 100,000+ addresses distributes the load so that the chance of a single IP being reused in a short period stays low. This is critical for marketplaces and search engines that aggressively limit the request rate from a single address. All addresses in the pool are legitimate Datacenter IPv4 of Elite level. These are not residential IPs from someone else's home networks and not devices from botnets: the target site doesn't receive headers exposing your real IP or the very fact that a proxy is in use.

Parsing marketplaces and price monitoring

Large platforms set strict limits on the number of requests from a single IP per minute. Without rotation, a parser hits 429 Too Many Requests or a CAPTCHA within minutes. With rotating proxies, the limit is effectively lifted: every request comes from a new address, and the system can't apply the restriction in time. The same logic works in SEO monitoring: to check a site's positions across dozens of regions and queries, you need to query the search engine from different IPs, otherwise the results will be skewed by personalization or a CAPTCHA. Rotating IPv4 closes both tasks with one tool. For parsing, SOCKS5 is often chosen — it doesn't send extra HTTP headers and works with remote DNS, which is important for geo tests.

How rotating differs from personal and ISP

We have four types of IPv4 proxies, each with its own niche. Personal — a single static IP for you alone, for an account that can't be exposed from someone else's address. ISP — also a static IP, but under a provider's name, so it looks like home access; good for long sessions and multi-accounting. Static Datacenter — the workhorse for tasks with stable binding. Rotating is the only one where the IP isn't pinned at all: it's built for high-frequency requests where changing the address matters more than binding. The choice depends on the task, not on which type is "better". If you need binding, take a static one; if you need anonymity at mass data collection — take a rotating one.

Why we deliberately don't sell IPv6

IPv6 addresses are cheaper and there are formally more of them, but in practice they cause problems. Some sites and anti-fraud systems still don't support IPv6 correctly, and some block such connections by default, considering them less trusted. As a result, you pay for a proxy that simply doesn't work on half of the target resources. We keep the entire lineup on IPv4 to guarantee compatibility with any site, service, or API without extra diagnostics. This is a deliberate limitation, not a shortcoming. If your task is a predictable result in any software (from ZennoPoster and BAS to Python scripts and anti-detect browsers), rotating IPv4 is the working choice in 2026.

How to calculate the request limit and not get it wrong

The plan is counted in requests, not traffic, and it's easy to get this wrong here. A single online store page is 10–40 requests: images, scripts, styles, counters. A search results page under active scraping can pull up to 100 requests per URL. Before taking the minimum package, open the "Network" tab in your browser, refresh the target page, and look at the actual number of requests. Multiply by the planned number of pages per day — you'll get an estimate close to reality. If the load grows, the package can be increased mid-period, without waiting for renewal. It's important to understand: 4xx and 5xx errors also consume credits — payment is for the fact of the request, not for the success of the response. So control errors on your software's side.

It is forbidden to use rotating proxies for

A list of tasks for which rotating proxies cannot be issued. This is due to the policy of upstream providers and the terms of service. A violation is a reason to refuse a refund.

Malware and viruses
Brute force and password guessing
Carding and fraud
DDoS attacks

The full list of restrictions is in the terms of service. On violation, rotating proxies are blocked without refund.

Questions and answers about rotating IPv4 proxies

How requests are counted, what's in the pool, and how per-request rotation differs from a sticky session.

A rotating proxy is a Datacenter IPv4 proxy that is not tied to a single address. You connect to a single entry point, and the ProxyElite load balancer picks a free address from the pool of 100,000+ IPv4 for each request. From the target site's perspective, it looks as if different users from different IPs are reaching it, not a single client from one address. That's why anti-fraud systems can't block you as a whole: while they check one address, the next request is already leaving from another.

Yes, this is called a sticky session. By default, we rotate the IP on every request, but if you need to pass authorization, add an item to the cart, or run a chain of actions without changing the address — the session can be pinned for 5, 10, or 30 minutes. Requests within the session leave from a single IP, and after it expires the next request again gets a new address. This is convenient for scenarios where changing the IP too often looks more suspicious than one stable address for a few minutes.

One API request or one concurrent connection consumes one plan credit. It's important to understand: when working with regular websites, one "thread" in your software is not a single connection. A browser or parser sends dozens of requests at once: loading an online store page can include 10–40 requests, and a search results page up to 100. So before choosing a package, open the "Network" tab in your browser's developer tools, refresh the target page, and look at the actual number of requests.

The pool contains only legitimate Datacenter IPv4 addresses — over 100,000 addresses. We do not use residential (home) IPs, mobile proxies, or botnet addresses. Traffic is not limited: you pay only for the number of requests, not for gigabytes. This is what sets rotating proxies apart from traffic-based plans and lets you route as much data through the connection as the task requires.

Yes. If a request was sent and the server returned a response — even with an error code — the credit is consumed. This is standard practice for rotating proxies: payment is for the fact of the request, not for the success of the response. To avoid burning the limit in vain, control errors on your software's side: if the parser consistently gets 403 or 429, the problem is more often in headers or behavior, not in the proxy, and changing the plan is pointless.

A plan is valid for 30 days. The limit can be spent in a day or stretched over a month; unused credits expire at the end of the period and are not carried over on renewal. A refund is possible within the first 24 hours after purchase: unused credits are converted into personal account balance and withdrawn via the ticket system.

Because IPv6 is still not supported everywhere. A significant portion of websites, anti-fraud systems, and ad platforms either do not accept IPv6 connections or flag such addresses as less trusted and block them by default. We keep the entire lineup — Datacenter, rotating, personal, and ISP proxies — on IPv4 only, so you don't waste time diagnosing "why doesn't the site see my address". IPv4 works with any target resource without surprises.

Ready to buy rotating IPv4 proxies?

Choose a request package in the calculator — the price is calculated immediately. Delivery after payment, unlimited traffic, refund within 24 hours. Access to a pool of 100,000+ IPv4 with automatic IP rotation on every request.

Go to the calculator

24-hour money-back guarantee  ·  24/7 support  ·  Delivery after payment