A post on r/proxies a couple of weeks ago asked for something a lot of bot runners want: "I run bots and am in need of private proxy pools that are not shared publicly. Am in need of both residential pools as well as virgin ISPs (subnet potentially)." Around the same time, someone on r/sneakerbots asked for the "cheapest mobile proxy provider that isn't burned", needing about 100 GB a month, and admitted the part most buyers skip: "haven't verified pool quality."
Private. Virgin. Unshared. Not burned. Real geo. Those words sit on almost every listing aimed at sneaker, card and ticket bots, and you cannot see behind them at checkout. You can check most of them afterwards. Do it before the drop. Below is what each label can honestly promise, and the commands that show what you were actually sold.
If you are still choosing between datacenter, ISP and residential in the first place, start with why proxy type matters more than anything on release day. This one assumes you have picked a type and now want to know whether the addresses are any good.
What "private", "dedicated" and "unshared" can actually promise
A private or dedicated proxy can promise that nobody else holds credentials for that address during your term, and nothing more. It says nothing about the neighbours.
The address is only one level a site scores. Anti-bot systems and fraud databases also look at the /24 (the block of 256 addresses your IP sits in) and at the network it is announced from. An IP that is yours alone can still sit next to 200 addresses that someone else ran through the same retailer last Saturday. The r/proxies poster knew this. Hence "(subnet potentially)". A private subnet and a private IP are two different products at two different prices. Ask any seller, us included, which one you are buying.
"Unshared" on a rotating residential plan is a softer word. A residential pool is a set of household connections that many customers exit through, so the honest meaning is narrower: the pool is not on public free lists, or it is sold to fewer people. There is no test you can run from outside that proves how many other customers share it.
How to check who else sits on your subnet and network
The quickest subnet check is to count how many of your addresses share a /24, then look up which network announces them.
Run this on a list in ip:port:user:pass format:
cut -d: -f1 proxies.txt | cut -d. -f1-3 | sort | uniq -c | sort -rn
If 25 addresses come back as 25 lines, you got spread. If they come back as one line with 25 in front, every task you run lives in the same block, and one bad week on that block hits all of them together. Neither is automatically wrong. You just want to know which one you have before the drop.
Then look up the network.
whois -h whois.cymru.com " -v 203.0.113.45"
That returns the AS number, the announced prefix, the country on record and the AS name. An ISP proxy should show a consumer ISP's name there. A hosting company or a cloud means datacenter, whatever the listing said. The r/aws thread from someone building a scalper bot on Lambda ("I don't want to get my personnal IP getting banned") is the extreme case. AWS publishes its whole address list as ip-ranges.json. Any site can block it with one rule.
What "virgin" and "not burned" can and cannot promise
Nobody can promise that a retailer has never seen an address. Retailers do not publish their block lists, and an IP has a history from before any proxy seller touched it.
What "virgin" can mean in practice is that the seller has not sold the address as a proxy before. What "not burned" can mean is that it passed some check at some point. Both are claims about the past, and the only question that matters is how the address does on your target this week. You can get close to an answer three ways.
First, the blocklists. Spamhaus can be queried over DNS by reversing the IP:
dig +short 45.113.0.203.zen.spamhaus.org
Empty is good. A 127.0.0.2 to 127.0.0.9 answer is a real listing (spam source, compromised host). A 127.0.0.10 or 127.0.0.11 answer is the policy list for end-user ranges, which is normal for a residential or ISP address and not a burn. One catch: queries sent through big public resolvers get an error code (127.255.255.254) instead of an answer, so run it from a machine with its own resolver or use the web lookup.
Second, the fraud scores. Our free IP fraud score checker and IP lookup show the connection type, the ASN and whether the address reads as proxy or hosting. Treat them as opinions from a database. Different checkers often disagree about the same IP, and none of them is the retailer.
Third, the one that counts: load the real target through the address on a quiet day. A challenge page or a block on a Tuesday afternoon, with no drop running, means the address or its block is already known there. Do it the day before, not ten minutes before.
How to catch a fake-geo IP before drop day
You catch fake geo by measuring round-trip time, because physics does not read geolocation databases. Light in fibre covers roughly 100 km of distance per millisecond of round trip, and real routes are longer than straight lines.
A thread on r/selfhosted describes the problem exactly: the target was hosted "in the Oregon/Washington region", the team ran 30 static ISP addresses, and "most providers we've tested are slow, likely due to fake geo IPs or overloaded/resold infrastructure." A geolocation database only records what the network registered. An address can be registered as US and physically answer from Frankfurt.
Rent a small server in the region that matters and time the TCP handshake to the proxy port. Many proxies ignore ping, but the proxy port has to accept a connection:
for i in 1 2 3 4 5; do curl -s -o /dev/null -w '%{time_connect}\n' http://203.0.113.45:8080; done
Take the lowest. Frankfurt to the US East Coast is over 6,000 km, so a real round trip cannot come in much under 60 ms. If a "US" address answers in 3 ms from your Frankfurt box, it is in Frankfurt. Then trace the path with mtr -rwc 10 -T -P 8080 203.0.113.45 and read the router names near the end. They often carry airport or city codes like fra, lhr, ord or sea.
One honest caveat. "US" is a big country. An address in Virginia is real US geo and still sits about 3,700 km from Oregon, which puts a floor of close to 40 ms on the round trip that no tuning removes. Our own ISP proxies are sold by country, with no city choice, so for a West Coast target you would measure exactly as above before committing.
The r/webscraping slot-booking post makes the same point. Slots "open at exactly 12:00 PM" and "run out in seconds." Distance is part of that race.
Captcha proxies and checkout proxies are two different purchases
A captcha proxy holds one Gmail's harvester session steady for weeks, while a checkout proxy carries one task through one release, so they get judged on different things.
A 2022 r/sneakerbots thread shows the confusion well: "none of my gmails passed splash ... I've been farming the past month with unknown captcha proxies and they were all apparently 0.9 and all that crap but it still gave me issues during drop. So I'm wondering if it's my gmails or maybe even the captcha proxies." A reCAPTCHA score is handed to the whole browser session making the request, and a logged-in Gmail is part of that session. A seller's "0.9" describes their browser and their account on their test. It does not describe your Gmail on drop morning.
Harvesters need few addresses, held long, one account each, in the account's country. Checkout needs one address per task in the release country, spread out. Don't flip that.
Mobile per GB or ISP per IP when the budget is tight
Per-GB mobile makes sense when the bot moves little data, and per-IP ISP makes sense when it loads full pages all day, because the ISP bill does not change with traffic.
The r/sneakerbots buyer did the maths out loud: "refusing to pay $6-8/GB from mainstream providers, that's $600+ before the rest of the stack." That number depends on how much data one task really uses. Measure it. Put one task on its own sub-user (both our residential and mobile plans have them), run a test session, read the usage and multiply. Request-based and full-browser bots differ a lot.
Mobile carrier addresses sit behind shared carrier gateways, so you are sharing them with strangers by design. "Not burned" for mobile means the carrier range is not flagged on your target, and you test that the same way, by loading the target through it. Static ISP addresses on our side have no data limit, so a block of them costs the same whether the bot loads ten pages or ten thousand.
A 2022 UK poster had "total budget 1k which is for sneakers, bot, proxy and server." Proxies are a slice of that. Ten tested addresses beat a big list nobody checked.
What BirdProxies sells against these labels
We sell addresses, and we can tell you exactly what comes with them. Every ISP address is dedicated to one customer at a time. The smallest order is 10 addresses for 30 days.
The ISP buy page has a site reachability tester: paste the retailer's URL and see, per location, whether the site answers before you pay. For Pokemon Center there is a separate clean pool in the US, Germany, the UK and France, where each subnet is checked against pokemoncenter.com before it is sold. If clean stock runs out, the order waits. It is never filled with unchecked addresses. If a block goes stale later, the IP Refresh Pass swaps all the addresses on a plan for fresh ones, once per billing period.
What we do not promise: that a site keeps working, or that no retailer has ever seen an address. No proxy beats a queue. None fixes a slow bot. The sneaker bot proxy page has the setup side.
A checklist to run the day before a drop
- Count /24s on your list and note how concentrated it is.
- Look up the ASN for a sample. Hosting or cloud names mean datacenter.
- Check a sample against Spamhaus and a fraud score tool.
- Time the TCP handshake from a server in the target region.
- Load the real target through each address once.
- Match proxy country to account, billing and shipping country.
Anything that fails steps 2, 4 or 5 is worth raising with the seller before the drop, not after.
FAQ
What does virgin ISP proxy mean?
It usually means the seller has not sold that address as a proxy before. It cannot mean no site has ever seen it, because the address had a history before any seller touched it. Test it against your actual target to know where it stands.
How do I check if a proxy is burned?
Load the target site through it at a quiet time, with no drop running. A challenge or block page then is the answer. Spamhaus lookups and fraud score checkers help as a first pass, but only the target's reaction tells you whether it is burned there.
Is a private proxy the same as a private subnet?
No. A private proxy means nobody else has credentials for that one address during your term. A private subnet means the whole block of 256 addresses is yours, which is rarer and priced differently. Ask the seller which one the listing means.
How can I tell if a proxy has fake geolocation?
Time the TCP connection to the proxy from a server in the claimed region and from one far away. A round trip much faster than the distance allows means the address is not where the database says. A traceroute with city codes in the router names confirms it.
Are captcha proxies different from checkout proxies?
Yes. Captcha proxies hold one harvester account steady for weeks in the account's country. Checkout proxies carry one task each in the release country. A low captcha score can come from the Gmail or the browser just as much as the address.
Is mobile or ISP cheaper for sneaker bots?
It depends on how much data one task uses. Mobile is billed per GB, so measure one task's usage on a test run first. Static ISP is billed per address per month, so the heavier the bot's traffic, the more a flat per-address price works in your favour.
Can I use AWS or Lambda IPs for a bot?
You can, but AWS publishes its whole address list, so any retailer can block those ranges with one rule. Expect trouble on protected retail sites, however clean a single address looks.
