# Rotating ISP Proxies: How Rotation Really Works and What a 1,000-IP Pool Costs

Published 2026-11-13 · By Team CleanProxies · [Read on the web](https://www.cleanproxies.com/blogs/rotating-isp-proxies)

> Rotating ISP proxies explained: rotate a pool of dedicated static ISP IPs (as low as $0.75/IP, unlimited bandwidth) in your own code, or pay per GB. Sizing formula, cost table and Python code.

Rotating ISP proxies are ISP IPs that change between requests, and you get them one of two ways: you buy a pool of static ISP IPs and rotate through it in your own code, or you use a provider's rotating gateway billed per GB. CleanProxies sells the first: a pool of dedicated static [ISP proxies](https://www.cleanproxies.com/products/isp-proxies) **as low as $0.75/IP** a month with unlimited bandwidth, which you rotate per request, per session or per account (1,000 IPs cost $990 a month). We do not sell a rotating ISP gateway; if you want a gateway that changes the IP for you, our separate rotating residential pool costs $0.99/GB at 100 GB and goes **as low as $0.63/GB**. This guide shows how to rotate an ISP pool, how many IPs you need, what that costs, and when per-GB rotation is the better buy.

**[Buy an ISP proxy pool](https://www.cleanproxies.com/products/isp-proxies)** · [See all prices](https://www.cleanproxies.com/pricing) · Need 100+ IPs or a whole /24? See [bulk pricing](https://www.cleanproxies.com/bulk-proxies).

*Updated 13 November 2026. Prices come from our public product and pricing pages that day. The cost table below comes from a small model we ran on the same date; its formula and assumptions are printed under the table. The rotation code was checked the same day against three local test proxies (one returning 429), not against a live site.*

![CleanProxies ISP proxy configurator with 1,000 IPs selected at $0.99 per IP for $990, unlimited bandwidth and 100Gbps](https://www.cleanproxies.com/media/blog/-P5Gq60aUN0D2Nm9Ldme.webp "The ISP configurator: 1,000 dedicated IPs cost $0.99 each ($990 a month), and 10,000 IPs $0.75 each. Screenshot: cleanproxies.com/products/isp-proxies, 31 October 2026; prices unchanged on 13 November.")

## TL;DR

- **An ISP IP is static by design.** It holds the same address for as long as it is on your plan. "Rotating ISP" means rotating across many static ISP IPs, either in your own code or behind someone's gateway.
- **Rotate your own pool** when you need predictable cost and unlimited bandwidth: 100 IPs = $149/mo, 1,000 IPs = $990/mo, 10,000 IPs = $0.75/IP (standard carrier ladder). Every IP is dedicated to you, never shared.
- **Use a per-GB rotating gateway** when you need IPs in many countries, states or cities, or a fresh IP on almost every request: rotating residential at $0.99/GB at 100 GB, down to $0.63/GB at 10,000 GB; data never expires.
- **Rule of thumb:** at 1,000 IPs one static IP costs the same as about 1.2 GB of residential data at the 1,000 GB rate ($0.84/GB). If each IP in your pool would carry clearly more than that per month, the pool is usually the cheaper buy.
- **Sizing rule:** IPs needed = peak requests per hour ÷ requests you allow per IP per hour, plus 15% headroom.

## Do rotating ISP proxies exist?

Yes, but the name covers two different products, and it pays to know which one you are looking at.

**1. A static ISP pool you rotate yourself.** You buy a list of dedicated ISP IPs (each one is an address announced by a consumer or business internet provider, hosted in a data center). Each IP keeps its address all month. Your scraper, bot framework or browser profile manager picks a different IP from the list for each request, each session or each account. This is what we sell: static residential ISP IPs on Tier-1 carrier ASNs, unlimited bandwidth and threads, 100Gbps network ports, delivered in seconds.

**2. A rotating gateway on ISP ranges.** Some providers put a pool of ISP IPs behind one hostname, bill per GB or per port, and change the exit IP for you on each request or on a sticky timer. You usually do not choose which IPs are in the pool, and in most such products other customers send traffic through the same addresses.

A third thing is often sold under the same name: **rotating residential** proxies, where the exits are real home connections (peer devices) rather than ISP ranges hosted in a data center. That is what our [rotating residential proxies](https://www.cleanproxies.com/products/rotating-residential-proxies) are: 50M+ IPs in 190+ countries, rotating per request or sticky for 5, 10, 15, 30 or 60 minutes or 24 hours.

## Static ISP pool vs rotating gateway vs rotating residential

|  | Static ISP pool (you rotate) | Rotating ISP gateway | Rotating residential (gateway) |
| --- | --- | --- | --- |
| Who changes the IP | Your code | Provider | Provider |
| IPs dedicated to you | Yes, 100% dedicated | Usually a shared pool (check the provider) | Shared pool |
| Billing | Per IP per month | Per GB or per port | Per GB |
| Bandwidth | Unlimited (CleanProxies) | Metered or capped | Metered |
| Same IP tomorrow | Yes, all month | Only if its sticky sessions last that long | Only inside a sticky session (up to 24 h) |
| Geo choice | Carrier and country (US, Canada, UK, France) | Varies | Country, state, city or network |
| Auth (CleanProxies) | user:pass, IP whitelist (1-20 IPv4) or SOCKS5 | n/a | user:pass, HTTP(S) |
| CleanProxies price | As low as $0.75/IP | Not sold | As low as $0.63/GB |
| Best for | High request volume to a few sites, account work, allowlists | Mid volume when you do not want to manage IPs | Wide geo coverage, a new IP on nearly every request |

If you were searching for **static** ISP IPs and landed here, see our [static residential proxies](https://www.cleanproxies.com/static-residential-proxies) page: that is the same product sold per IP, and it is the base for everything in the next section.

## How rotation over static ISP IPs works

You get a list of proxy lines from your dashboard, one per IP, in `host:port:user:pass` form (or IP-whitelisted, or SOCKS5). Rotation is then a choice you make in code. Four patterns cover most jobs:

1. **Round-robin per request.** Request 1 uses IP 1, request 2 uses IP 2, and so on. It spreads load evenly and is the simplest way to stay under a site's per-IP rate limit.
2. **Random per request.** Same idea, less predictable order. Useful when a target looks for regular patterns.
3. **Sticky per account or per session.** Each account, cart or browser profile is pinned to one IP and keeps it. This is what logins and ad accounts need: an account that jumps to a new IP on every click looks unusual. A static ISP IP gives you that stability for a whole month.
4. **Cool-down on errors.** When an IP gets a 429 or 403, take it out of the rotation for a while (and honour any `Retry-After` header) instead of retrying it right away.

Here is a short Python example of patterns 1, 3 and 4 with the `requests` library. Put your proxy lines in a file called `proxies.txt`, one `host:port:user:pass` per line (`USERNAME`, `PASSWORD`, `PROXY_HOST`, `PROXY_PORT` from your dashboard). It handles passwords that contain `:` or `@`, and `Retry-After` given in seconds or as a date. It is an example to adapt, not a benchmark.

```python
import email.utils
import itertools
import time
import zlib
from urllib.parse import quote

import requests

with open("proxies.txt") as f:
    lines = [l.strip() for l in f if l.strip()]

def to_url(line):
    host, port, user, pwd = line.split(":", 3)  # the password may contain ":"
    return f"http://{quote(user, safe='')}:{quote(pwd, safe='')}@{host}:{port}"

pool = [to_url(l) for l in lines]
round_robin = itertools.cycle(pool)
cooling = {}  # proxy url -> time it can be used again

def retry_after_seconds(value, default=300):
    if value.isdigit():
        return int(value)
    try:  # Retry-After can also be an HTTP date
        return max(0, email.utils.parsedate_to_datetime(value).timestamp() - time.time())
    except (TypeError, ValueError):
        return default

def next_proxy():
    for _ in range(len(pool)):
        p = next(round_robin)
        if cooling.get(p, 0) <= time.time():
            return p
    raise RuntimeError("every proxy is cooling down; slow down")

def sticky_proxy(account_id):
    # the same account always gets the same IP; if it is cooling down, wait for it
    p = pool[zlib.crc32(account_id.encode()) % len(pool)]
    time.sleep(max(0, cooling.get(p, 0) - time.time()))
    return p

def fetch(url, proxy):
    r = requests.get(url, proxies={"http": proxy, "https": proxy}, timeout=20)
    if r.status_code in (403, 429):
        cooling[proxy] = time.time() + retry_after_seconds(r.headers.get("Retry-After", ""))
    return r

if __name__ == "__main__":
    for i in range(3):  # round-robin: a different pool IP per request
        r = fetch("https://api.ipify.org?format=json", next_proxy())
        print("rotating", i, r.status_code, r.text)
    for i in range(2):  # sticky: account-42 keeps the same IP
        r = fetch("https://api.ipify.org?format=json", sticky_proxy("account-42"))
        print("account-42", i, r.status_code, r.text)
```

More patterns (sessions, retries, async) are in our guide on [how to rotate proxies in Python](https://www.cleanproxies.com/blogs/how-to-rotate-proxies-in-python), and [rotating vs sticky sessions](https://www.cleanproxies.com/blogs/rotating-vs-sticky-sessions) explains when to pin an IP. Before you put a pool into production, run a few lines through the [proxy checker](https://www.cleanproxies.com/tools/proxy-checker).

### Check your exits and fix the common errors

- **Exit IP and network:** print the IP each line exits from (the example above calls an IP echo service) and look it up in our [IP lookup](https://www.cleanproxies.com/tools/ip-lookup) tool. The network (ASN) shown should be the carrier you ordered, not a hosting company.
- **Expect repeats:** in a pool of N IPs, round-robin reuses each IP every N requests. That is normal; what matters is the rate per IP, which the sizing formula below controls.
- **407 Proxy Authentication Required:** wrong username or password, or an IP-whitelisted line used from an address that is not on your whitelist.
- **Timeouts or connection refused:** check host and port, and that you use the HTTP or SOCKS5 line type you chose in the dashboard.
- **403 or 429 from the site:** your per-IP rate is too high for that site. Let the IP cool down and lower the rate, or add IPs.

## How many ISP IPs do you need to rotate?

The number of IPs depends on your peak request rate and how many requests per hour you let each IP carry. Sites do not publish their limits, so start with a conservative per-IP rate, watch your 429s, and adjust.

**IPs needed = peak requests per hour ÷ requests per IP per hour × 1.15 (headroom for IPs that are cooling down)**

We ran this formula (script `rotisp.py`, 13 November 2026) for three job sizes, spread evenly over 24 hours, at 60 and 20 requests per IP per hour. Checkout prices any amount at the rate of the highest tier it reaches (799 IPs are billed at the 500-IP rate of $1.15), so the costs below are for the exact number of IPs. We compared each job with sending the same requests through rotating residential data at an assumed 150 KB per page.

| Requests/day | Requests per IP per hour | IPs to buy (+15%) | ISP pool cost/mo | Residential GB/mo (150 KB pages) | Residential cost/mo |
| --- | --- | --- | --- | --- | --- |
| 100,000 | 60 | 80 | **$143.20** | 450 GB | $423 |
| 100,000 | 20 | 240 | **$357.60** | 450 GB | $423 |
| 1,000,000 | 60 | 799 | **$918.85** | 4,500 GB | $3,600 |
| 1,000,000 | 20 | 2,396 | **$2,252.24** | 4,500 GB | $3,600 |
| 5,000,000 | 60 | 3,994 | **$3,554.66** | 22,500 GB | $14,175 |
| 5,000,000 | 20 | 11,980 (two orders: 10,000 + 1,980) | **$9,460.20** | 22,500 GB | $14,175 |

*Assumptions: 30-day month; traffic spread evenly over 24 hours (if your job runs 8 hours a day, the peak rate and the IP count triple); every request succeeds the first time (add your retry rate); 150 KB per page is an assumed HTML-only average, and pages loaded in a headless browser with images and scripts can weigh 1-3 MB, which multiplies the residential column but not the ISP column. ISP rates used: 50+ $1.79, 250+ $1.29, 500+ $1.15, 2,000+ $0.94, 3,000+ $0.89, 10,000 $0.75 per IP (standard carrier ladder; AT&T has its own, higher ladder). One ISP order holds up to 10,000 IPs. Residential rates used: 250+ GB $0.94, 2,500+ GB $0.80, 10,000+ GB $0.63 per GB. Large orders depend on carrier stock at the time you order.*

What the numbers mean:

- **At steady, high volume a static pool wins on price,** because ISP bandwidth is unlimited and the cost does not grow with page weight. At 1 million requests a day the pool costs $919-$2,252 a month against $3,600 for the same traffic on per-GB data.
- **Check the next tier up.** 799 IPs cost $918.85; 1,000 IPs cost $990. For $71 more you get 201 more IPs and a lower rate per IP.
- **Per-GB rotation wins when the job is small, bursty or spread across many locations.** A 20 GB job does not justify 100 IPs, residential data never expires, and no static pool gives you about 3,800 US cities.
- **Rule of thumb per IP:** one static IP costs the same as about 1.8 GB of residential data at 100 IPs ($1.49/IP vs the 1,000 GB rate of $0.84/GB), 1.2 GB at 1,000 IPs, and 0.9 GB at 10,000 IPs. At the 10,000 GB rate ($0.63/GB) those figures are 2.4, 1.6 and 1.2 GB. If each IP in your pool would carry clearly more traffic than that in a month, the pool is usually cheaper; if you would buy a smaller data pack, compare at that pack's rate.

## Pools of 255+ IPs: subnets and bulk orders

For big pools you can buy whole /24 blocks instead of single IPs. Our [ISP subnet proxies](https://www.cleanproxies.com/products/isp-subnet-proxies) come in 255, 510 or 1,020 IPs:

| Subnet order | Price per IP | Monthly cost |
| --- | --- | --- |
| 255 IPs (one /24) | $1.49 | $379.95 |
| 510 IPs (two /24s) | $1.35 | $688.50 |
| 1,020 IPs (four /24s) | $1.19 | $1,213.80 |

A subnet gives you a contiguous block on one carrier, which is handy for allowlists and for jobs where you manage the range yourself. For rotation across many sites, remember that a site that blocks a whole /24 blocks every IP in it, so for maximum spread buy single ISP IPs across several carriers (Frontier, AT&T, Comcast, Cox and RCN in the US; AT&T has its own, higher price ladder) rather than one block. A 1,000-IP order of single ISP IPs costs $990 a month; a 1,020-IP subnet order costs $1,213.80.

**Buying 100+ IPs or reselling?** Volume pricing goes down to $0.75/IP at 10,000 IPs; see [bulk proxies](https://www.cleanproxies.com/bulk-proxies). If you sell proxies to your own customers, our [proxy reseller](https://www.cleanproxies.com/reseller-api) API lets you create and manage sub-users with tier pricing (it needs $500 in deposits or approval).

## When to choose which

- **Account work, logins, ad accounts, allowlisted APIs:** a static ISP pool with one IP pinned per account. Rotation per request is the wrong tool here.
- **Price monitoring, SERP tracking or catalog scraping on a few large US sites at high volume:** a static ISP pool with round-robin and cool-downs. Unlimited bandwidth keeps the cost flat as page weight grows. See [proxies for web scraping](https://www.cleanproxies.com/use-cases/web-scraping).
- **Many countries, states or cities, or targets that need a new IP almost every request:** rotating residential, per GB, data never expires.
- **Mobile-only targets or app testing on carrier networks:** our [mobile proxies](https://www.cleanproxies.com/products/mobile-proxies), real 4G/5G IPs in 190+ countries from $0.79/GB.

## How to test before you buy a pool

1. Write down your target sites, requests per day and the per-IP rate you plan to use.
2. Take the [$4.99 trial](https://www.cleanproxies.com/create-account?next=/dashboard/buy-proxies/trial) (5 ISP IPs for 1 hour, or 100 MB of data) and run a slice of your real job through it with the rotation code above.
3. Count status codes per IP: 200s, 403s and 429s. If 429s climb, lower the per-IP rate and size the pool again with the formula.
4. Buy the pool size the formula gives you (it already includes 15% headroom), and check whether the next tier up costs little more.

![CleanProxies pricing page: ISP proxies as low as $0.75/IP, residential as low as $0.63/GB and mobile as low as $0.79/GB](https://www.cleanproxies.com/media/blog/-P5n_XUkK2vxjfUYVevV.webp "Our pricing page: ISP as low as $0.75/IP, residential as low as $0.63/GB, mobile as low as $0.79/GB. Screenshot: cleanproxies.com/pricing, 7 November 2026; prices unchanged on 13 November.")

Every ISP IP is dedicated to you and never shared, delivered instantly, with 99.9% uptime, under 20 ms latency and 24/7 support. ISP proxies start **as low as $0.75/IP** with unlimited bandwidth; rotating residential **as low as $0.63/GB**; mobile **as low as $0.79/GB**.

**[Build your ISP pool now](https://www.cleanproxies.com/products/isp-proxies)** · [Compare every plan on the pricing page](https://www.cleanproxies.com/pricing)

## FAQs

### Do ISP proxies rotate?

Not on their own. An ISP proxy is a static IP that keeps the same address for as long as it is on your plan. CleanProxies sells static ISP pools that you rotate in your own code (per request, per session or per account); if you want a gateway that changes the IP for you, use our separate per-GB rotating residential proxies.

### How much does a rotating ISP proxy pool cost?

At CleanProxies, 100 ISP IPs cost $149 a month, 1,000 IPs $990 a month and 10,000 IPs $0.75 per IP, all with unlimited bandwidth. Any amount is billed at the rate of the highest tier it reaches; AT&T IPs have their own, higher price ladder. Whole /24 subnets cost $379.95 for 255 IPs, down to $1.19 per IP at 1,020 IPs.

### How many ISP IPs do I need to rotate?

Divide your peak requests per hour by the requests you allow each IP per hour, then add about 15% for IPs that are cooling down after a 429. At 1 million requests a day spread over 24 hours and 60 requests per IP per hour, that is about 799 IPs.

### Is a static ISP pool or rotating residential cheaper?

It depends on traffic per IP. At 1,000 IPs one static IP costs the same as about 1.2 GB of residential data at the 1,000 GB rate ($0.84/GB). If each IP in your pool would carry clearly more than that per month, the static pool is usually cheaper; for small, bursty or many-location jobs, per-GB rotating residential is usually cheaper.

### Can I use SOCKS5 with a rotating ISP pool?

Yes. Our ISP and ISP subnet IPs support user:pass HTTP(S), IP whitelisting for 1-20 IPv4 addresses, and SOCKS5. Rotating residential and mobile proxies use user:pass over HTTP(S).

### Can I buy a large pool or resell it?

Yes. One ISP order holds up to 10,000 IPs, prices drop to $0.75 per IP at 10,000 IPs, and resellers can create and manage sub-users through our reseller API (it needs $500 in deposits or approval).
