All IPv4 proxy plans in one place
IPv4 only. Four products with different economics: datacenter, ISP, rotating, and personal. Below is not just prices, but an explanation of what you're paying for in each plan and which scenario it pays off in.
Infrastructure in numbers
All four plans run on ProxyElite's own hardware in a Tier-III datacenter. No reselling of third-party pools — IP addresses, servers, and channels belong to us since 2012.
Datacenter IPv4 proxies: from $0.065/IP
Datacenter proxies are static IPv4 addresses from datacenters. Their strength is not in "provider reputation", but in price per unit and channel speed. If the task is mass-scale and doesn't require anti-fraud trust — this is the basic choice.
ISP IPv4 proxies: from $0.175/IP
ISP proxies are more expensive than datacenter, and this is not a marketing markup. The IP is registered with an internet provider (Comcast, BT, Deutsche Telekom), so to sites it looks like a home connection. You pay for anti-fraud systems not seeing the difference between you and a regular user.
Rotating IPv4 proxies: from $25/1M requests
There is no rental of specific addresses here. You get access to a pool of 100,000+ IPv4s and pay for actual requests. For heavy parsing with a large number of requests, this is cheaper than maintaining hundreds of static IPs that idle between tasks.
Personal IPv4 proxies: from $3.68/IP
A personal proxy costs more per unit than a datacenter one, but the address is assigned only to you. This is not about scale, but about privacy: when proximity to other people's actions on the same IP creates a risk for an account or session.
Comparison of all IPv4 proxy plans
Quick table: which plan for which task. Detailed comparison across 14 parameters — on the home page.
| Parameter | Datacenter | Rotating | Personal | ISP |
|---|---|---|---|---|
| IP type (by whois) | Datacenter | Datacenter (pool) | Datacenter | Real ISP |
| Session stability | Fixed IP | Rotation / sticky | Fixed IP | Fixed IP |
| IP exclusivity | Pool | Shared pool | Only you | Pool |
| Fits anti-fraud sites | No | No | Depends | Yes |
| Price from | $0.065/IP | $25/1M req | $3.68/IP | $0.175/IP |
| Best use case | Parsing, SEO, DevOps | Mass parsing without accounts | Private accounts, banking | Arbitrage, multi-accounting |
| Action | Datacenter | Rotating | Personal | ISP proxies |
Tasks by proxy type
Each plan is designed for a specific scenario. Below are typical ProxyElite client tasks and the suitable plan.
Parsing and SEO (datacenter)
Mass data collection from loyal sites, SERP monitoring. Unlimited traffic and low price per IP — from $0.065.
Mass parsing without accounts (rotating)
New IP on each request from a 100,000+ pool. Pay per request — from $25/1M. Removes frequency-based blocks.
Personal accounts (personal)
IP in single hands for social networks, banking, API with whitelist. Address reputation is only yours. From $3.68/IP.
Arbitrage and multi-accounting (ISP)
Static IP with provider ASN for Facebook, Google, marketplaces. Anti-fraud sees a "home" user. From $0.175/IP.
DevOps and load testing (datacenter)
Distributed testing (k6, Locust, JMeter) from different IPs. Uplink up to 1 Gbps, unlimited traffic.
Geo-targeted ad testing (ISP)
Check creatives with an IP from the desired region. An ISP address with Comcast or BT ASN will show the ad as a real user.
Automation in ZennoPoster (personal)
Dedicated IP for templates and bots. Address reputation depends only on your actions — without surprises from shared pools.
Crypto exchange monitoring (datacenter)
Low latency, unlimited traffic, API key binding. For arbitrage bots on Python/Node.js.
How all proxy plans work
Technical mechanics without simplifications. Clear what exactly happens between your client and the target site — general logic for all four plans.
Connecting to the proxy
Your client (browser, Python script, ZennoPoster) sends a request to the IP:port or gateway:port address. Connection via HTTP, HTTPS, or SOCKS5.
Authentication — by login/password and/or by IP from the whitelist. Can be combined for server and mobile clients.
Traffic routing
The proxy receives the request, replaces the source address with its IPv4, and sends the request to the target site. The X-Forwarded-For header is not passed — Elite anonymity level.
DNS resolution on the proxy side (important for SOCKS5 and geo-tests — the target site sees the provider's DNS, not your local one).
Response and session
The site responds to the proxy, the proxy forwards the response to you. For static plans (datacenter, personal, ISP), the IP doesn't change — the session is stable, cookies are preserved.
For rotating proxies, the IP changes on each request or by timer (sticky 5/10/30 minutes) — configured in the client area.
Verification via whois
The address type is verified via whois: the orgname or netname field. For datacenter — hosting, for ISP — real provider (Comcast, BT).
ASN — autonomous system — is also visible in whois. This affects the trust of anti-fraud systems: ISP passes where datacenter is blocked.
Workflow: from purchase to usage
Four steps, each takes less than a minute. No "pending moderation" requests — IP delivery is automatic for all plans.
Choosing a plan in the calculator
Choose the type (datacenter/ISP/rotating/personal), country, IP count or request count, rental term (1/3/6/12 months). See the final price with discount.
Instant list delivery
After payment, the system automatically allocates IPs and generates the list. Available in txt, csv, json formats — without waiting and manual checks.
Configuring authentication
In the control panel, you enable the whitelist (5 IPs free) or use login/password. Dual authentication is supported for security.
Export and IP replacement
Export the list in the desired format. If an IP is banned on a site — request a replacement via ticket, free during the rental period.
Connect in 5 minutes
Ready code examples for the most common scenarios. Connection data (IP:port@login:password) is taken from the client area.
# Check IP via ProxyElite HTTP proxy
curl -x "http://USER:PASS@PROXY_IP:PORT" \
-L "https://api.ipify.org?format=json"
# Login/password can be passed as a separate flag
curl --proxy "http://PROXY_IP:PORT" \
--proxy-user "USER:PASS" \
"https://httpbin.org/ip"# SOCKS5 with DNS resolution on the proxy side (socks5h)
curl -x "socks5h://USER:PASS@PROXY_IP:PORT" \
-L "https://api.ipify.org?format=json"
# SOCKS5 without local resolution — socks5
curl --socks5 "PROXY_IP:PORT" \
--proxy-user "USER:PASS" \
"https://httpbin.org/ip"import requests
proxies = {
"http": "http://USER:PASS@PROXY_IP:PORT",
"https": "http://USER:PASS@PROXY_IP:PORT",
# for SOCKS5 you need pip install requests[socks]
"socks5": "socks5h://USER:PASS@PROXY_IP:PORT",
}
r = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=10)
print(r.json()) # {'ip': 'PROXY_IP'}import { request, ProxyAgent } from 'undici';
const agent = new ProxyAgent('http://USER:PASS@PROXY_IP: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":"PROXY_IP"}
}<?php
$ch = curl_init('https://api.ipify.org?format=json');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_PROXY, 'PROXY_IP:PORT');
curl_setopt($ch, CURLOPT_PROXYUSERPWD, 'USER:PASS');
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
// For SOCKS5 uncomment:
// curl_setopt($ch, CURLOPT_PROXYTYPE, CURLPROXY_SOCKS5);
$response = curl_exec($ch);
echo $response; // {"ip":"PROXY_IP"}
curl_close($ch);IP:port@login:password or IP:port for whitelist authentication.
Works with your software
All IPv4 proxy plans are compatible with any tool that supports HTTP/HTTPS/SOCKS5. The most popular ones are listed — 500+ solutions work in total.
IP:Port
192.0.2.1:8080
IP:Port:Login:Password
192.0.2.1:8080:user:pass
Format builder
any template via separators
Proxy infrastructure for business
A separate block of conditions for B2B clients: agencies, arbitrage teams, datacenters, and SaaS services. We cover legal and financial matters.
Contract and documents
We sign an official contract. We provide invoices, acts of performed work, and closing documents for accounting.
Flexible payment terms
Deferred payment for regular clients. Cashless settlement, invoice payment, cryptocurrencies (BTC, ETH, USDT), and bank cards.
Dedicated manager
Personal account manager with direct contact in Telegram/Slack. Solves issues of subnet allocation, IP replacement, and API integration.
Corporate orders from $1,000
Individual prices for orders from 5,000 IPs. Dedicated /24 subnets, custom geo, 99.9% SLA with downtime compensation.
How to read IPv4 proxy prices: the economics of each plan
The four products differ not just in the price tag. Behind each price is its own cost model. Below is a breakdown without generalities: what exactly you're paying for and when the overpayment is justified.
Datacenter IPv4: minimum price per unit, but without "home" reputation
A datacenter proxy is renting an IP in a datacenter. The provider doesn't pay for "provider address reputation", so the price per IP is the lowest in the lineup (from $0.065). You get a static address, unlimited traffic, and a channel up to 1 Gbps. There's one limitation: for anti-fraud systems, such an IP is a clear sign of a datacenter (ASN Hetzner, OVH). Where a site checks the "home" nature of the connection (banks, some social networks, payment services), a datacenter proxy may not pass. But for parsing catalogs, SEO monitoring, and mass requests where speed and price per IP matter, not the illusion of a home user, this is the optimal choice.
ISP proxies: you pay for not being distinguished from a subscriber
An ISP proxy uses an IPv4 officially registered with an internet provider (Comcast, BT, Deutsche Telekom). To the external site, this is not an "IP from a datacenter", but a regular connection. This is why the ISP plan is more expensive than datacenter (from $0.175): the price includes not speed or traffic volume, but the trust of anti-fraud systems. If the task is a long authorized session, an ad account, or an account where address history matters, an ISP proxy pays off by not losing access. For mass parsing where the site doesn't care where the request came from, overpaying for ISP usually doesn't make sense.
Rotating IPv4: price per request instead of price per idle
With rotating proxies, you don't rent an IP. You buy access to a pool and pay for actual requests (from $25 per 1M). If you run heavy parsing on static IPs, some addresses will idle between tasks, and you'll pay for that. The rotating model shifts payment to the actual load: more requests — more cost, but no fixed rent "just in case". For peak tasks, this is economically more profitable; for a uniform small load, it may turn out more expensive than static. Before buying, open the "Network" tab in the browser, refresh the target page, and look at the actual number of requests — this gives an accurate cost estimate.
Personal IPv4: a surcharge for the absence of neighbors
A personal proxy is an IP that no one uses but you (from $3.68 per IP). In datacenter and ISP packages, the address may be shared among several clients (although with load balancing), while in a personal one — it's only yours. The surcharge here is not for speed or traffic, but for eliminating other people's behavior on the same IP. This is justified when the account or session is sensitive to address reputation (banking, messengers, API with whitelist), and doesn't make sense for mass tasks where the IP is a consumable. A simple rule: if the IP is part of the account reputation, take personal. If the IP is a consumable, take package datacenter.
Where to actually save on IPv4 proxies
Three levers that work. First — volume: in datacenter, ISP, and personal plans, the price per IP drops as the package grows. Second — term: paying for 3, 6, or 12 months gives a discount of up to 20%, and this is fixed savings without quality loss. Third — rejecting an unnecessary type: if the task doesn't require rotation, rotating proxies are almost always more expensive than static in terms of predictable load. And vice versa: for peak parsing, don't buy hundreds of static IPs that will idle. For orders of 5,000+ IPs, individual bulk conditions apply — a manager will calculate the exact price.
Brief logic for choosing a plan
Datacenter — when price per IP and speed matter, and address reputation is not critical. ISP — when the site checks the "home" nature of the IP and the session should live long. Rotating — when the load is peak and you don't want to pay for idling static addresses. Personal — when you need an IP without neighbors and are willing to pay for it. All four plans at ProxyElite work on IPv4, with unlimited traffic (except rotating — pay per request) and a refund within 24 hours.
Prohibited to use proxies for
List of tasks proxies cannot be used for. This is related to the upstream providers' policy and the service rules. Violation is a reason for refund refusal.
The full list of restrictions is in the service rules. If violated, proxies are blocked without refund.
Frequently asked questions about IPv4 proxy plans
How plans differ in price, how requests are counted, and when the overpayment is justified.
A datacenter IP belongs to a datacenter (ASN Hetzner, OVH), so it costs less — from $0.065 per IP. An ISP address is registered with an internet provider (Comcast, BT, Deutsche Telekom) and looks like a home connection to sites. The price difference is the cost of anti-fraud system trust, not speed or traffic. If a site checks the "home" nature of the IP, the ISP overpayment pays off with the absence of blocks.
Because you don't rent specific addresses. You get access to a pool of 100,000+ IPv4s and pay for actual requests (from $25 per 1M requests). This more accurately reflects the load: when parsing, you don't pay for IPs that idle between tasks. Before buying, open the "Network" tab in the browser and look at the actual number of requests on the target page — this gives an accurate cost estimate.
When IP reputation is critical. A personal address (from $3.68 per IP) is not shared with other clients, so other people's actions don't affect your session. For mass tasks where the IP is a consumable, the personal overpayment is usually not needed. A simple rule: if the IP is part of the account reputation (banking, messengers, API with whitelist), take personal. If the IP is a consumable for parsing, take package datacenter.
Yes. Term discounts: 3 months — −10%, 6 months — −15%, 12 months — −20% on all plans. For orders of 5,000+ IPs, individual bulk conditions apply for datacenter, personal, and ISP proxies. A manager will calculate the exact price for your volume and term. For B2B clients, deferred payment and a dedicated manager are available.
Yes, within 24 hours of purchase, provided the usage limits are not exceeded. For a refund, contact support via ticket with the order number. This reduces the risk of error when choosing between datacenter, rotating, personal, and ISP proxies: you can verify on a real scenario that the plan works with your target site as expected.
Most target sites — marketplaces, social networks, ad accounts, anti-fraud systems — either don't support IPv6, or keep IPv6 addresses in separate pools with reduced trust. Old parsing software (BAS, ZennoPoster, some Python libraries) also works poorly with IPv6. ProxyElite keeps the entire plan lineup on IPv4 only, to guarantee compatibility with any target resource without additional diagnostics.
Automatically, immediately after payment — for all plans. The IP list is available in the client area in txt, csv, and json formats. If access hasn't arrived within 10 minutes — contact support via ticket. No "pending moderation" requests — IP delivery is automatic.
Not sure which IPv4 proxy plan is right for you?
Go back to the calculators above or contact support — we'll help match the task and proxy type without overpaying for unnecessary features. Delivery right after payment, refund within 24 hours.
24-hour refund guarantee · 24/7 support · Delivery after payment