ISP proxies are usually bought per IP, every month, which makes them unforgiving of a bad purchase. Buy the wrong locations, the wrong number of IPs or addresses that are not really residential, and you pay for that mistake every billing cycle until you notice.
Most of those mistakes are avoidable with a little preparation before you buy and a few checks during the first days. This guide covers what to decide first, what to verify, and the pricing traps to watch for. We sell ISP proxies ourselves, so we will say where our own product fits, but every check below applies to any provider.
First, make sure ISP proxies are what you need
ISP proxies give you a stable address on a residential internet provider, in a location you choose, for weeks or months. That is the right tool for a narrow set of jobs:
- Staying logged into accounts you manage, day after day.
- Sessions that last hours rather than minutes.
- Checking how a site looks from a specific city and provider.
For collecting many pages across many sites, a rotating residential pool is usually cheaper and more effective, and for some targets you need no proxy at all. Our comparison of ISP and residential proxies covers the split, and when you don’t need a residential proxy covers the case where neither is necessary.
Decide three things before you shop
1. How many IPs. Count identities, not requests. If each account, store or worker should look like its own household, you need one IP per identity. Buying “a few extra” is how small plans become large invoices; add IPs when you add accounts.
2. Which locations, and how precise. Write down where each identity should appear to be. Some jobs need only a country. Account work usually needs the city the account normally logs in from. Ad and localisation checks may need a specific internet provider (ASN) in that city. A provider that only sells by country is the wrong one if you need city and ISP.
3. How long. If the job lasts a week, a monthly per-IP plan may cost more than it saves. If it runs indefinitely, stability and support matter more than the entry price.
What to check during a trial or refund window
Claims on a pricing page are easy to make. These checks take an hour and tell you what you actually bought.
Is it really residential? An “ISP proxy” should exit from a consumer internet provider, not a hosting company. Look up each exit IP’s network: a data-centre owner in the results means you are paying residential prices for server addresses.
Is it where you were promised? Check the country and city of each exit against what you ordered.
How spread out are the addresses? If most of your IPs sit in the same small block of addresses, they look related to any site that checks, and one block decision can hit them all.
The script below automates those three checks for a batch of trial proxies using ip-info.com, our free IP geolocation API, which reports the network and whether it is residential or hosting:
from collections import Counter
import requests
def inspect(proxy_url, get=requests.get):
"""Where does this proxy really exit, and on what kind of network?"""
info = get("http://ip-info.com/json", proxies={"http": proxy_url, "https": proxy_url}, timeout=20).json()
return {k: info.get(k) for k in ("ip", "city", "country", "asn", "as_name", "user_type", "connection_type")}
def audit(proxies, expected_country, get=requests.get):
"""Check a batch of trial proxies before you commit to a provider."""
exits = [inspect(p, get) for p in proxies]
subnets = Counter(".".join(e["ip"].split(".")[:3]) for e in exits)
return {
"proxies": len(exits),
"not_residential": [e["ip"] for e in exits if e["user_type"] != "residential"],
"wrong_country": [e["ip"] for e in exits if e["country"] != expected_country],
"distinct_asns": len({e["asn"] for e in exits}),
"largest_subnet_share": round(max(subnets.values()) / len(exits), 2),
}Run on three proxies, two residential and one that turned out to be a data-centre address in the wrong country (an illustrative example), it reports:
from verify_isp import audit
trial = [
"http://USER1:PASS@isp.example.com:443",
"http://USER2:PASS@isp.example.com:443",
"http://USER3:PASS@isp.example.com:443",
]
print(audit(trial, expected_country="US")){'proxies': 3, 'not_residential': ['198.51.100.5'], 'wrong_country': ['198.51.100.5'], 'distinct_asns': 2, 'largest_subnet_share': 0.67}Does it hold up over a few days? Run your real workload at its real pace through a handful of IPs. Watch for connection errors, slow responses and sites challenging the logins. One afternoon of testing hides problems that show up on day three.
Can you get help? Ask support a specific technical question during the trial. How fast and how well they answer is a preview of the next outage.
Pricing traps
| Trap | What it looks like | What to ask |
|---|---|---|
| Bandwidth caps on “unlimited” plans | Per-IP pricing plus a traffic allowance in the small print | Is bandwidth metered at all on this plan? |
| Location surcharges | The advertised price applies only to a few countries | What does each of my locations cost? |
| Minimum terms | A low monthly price that requires a long commitment | Can I cancel or downsize monthly? |
| Replacement limits | A cap on how often you can swap a bad IP | How do I replace an IP that stops working? |
| Paying for idle IPs | IPs bought for accounts that never launched | Can I add IPs later instead of buying ahead? |
Also ask how addresses behave over time. Some providers promise an address that never changes; others, including us, keep the city and provider fixed while the address behind them can refresh occasionally, the way a home connection does. Neither is wrong, but your setup should match what you buy. Our guide to ISP proxy setup for long sessions and persistent logins shows how to build for it.
Questions about sourcing
ISP and residential addresses come from somewhere, and how a provider obtains them affects both reliability and your own risk. Ask where the addresses come from, whether the network owners or users have agreed to the arrangement, and what the provider does about abuse. Our explainer on how providers ethically source residential IPs lists the questions worth asking and the answers to expect.
Where Shifter fits
For reference, this is how our own ISP proxies answer the questions above:
- Sold per IP, with unlimited bandwidth.
- You choose the city and ISP (ASN) for every IP, across 120 countries.
- Plans start at 4 IPs and go up to 200, so you can buy close to the number of identities you need.
- HTTP(S) and SOCKS5 on one host and port.
- A 3-day money-back guarantee on your first purchase, which is the window for the checks in this guide.
Current prices are on the ISP proxy pricing page.
FAQ
How many ISP proxies do I need?
One per identity that should look like a separate household: one per account, store or long-running worker. Buy for the identities you have now and add more as you grow.
How can I tell whether ISP proxies are really residential?
Look up the network behind each exit IP. A genuine ISP proxy exits from a consumer internet provider; a hosting or data-centre network means it is not residential, whatever the product is called.
Are ISP proxies worth it for web scraping?
For long sessions, logins and location-specific checks, yes. For collecting many pages across many sites, rotating residential proxies are usually more cost-effective.
What should I test before committing to a provider?
Whether each exit is residential, whether it is in the location you ordered, how spread out the addresses are, how it performs under your real workload for a few days, and how well support answers a technical question.
The bottom line
Decide how many identities you need, where each should be and for how long before you look at prices. Use the trial or refund window to check that every IP is residential, in the right place and not clustered, and run your real workload for a few days. Read the pricing for bandwidth caps, surcharges and minimum terms. An hour of checks at the start costs far less than a year of paying for the wrong IPs.