Sneaker proxies for queues, raffles and limited drops

Most drops are now raffles and queues, where a stable identity matters more than milliseconds. Static ISP IPs hold one address from queue to checkout for $2.00 per IP per month, with unlimited traffic.

Per ISP IP per month$2.00

Static, one customer per address, billed monthly.

Traffic on ISP and DC∞

Queue pages and monitors burn bandwidth; here it is not metered.

Port per ISP IP1 Gbps

Dedicated bandwidth per address.

Replacement window24 h

Swap an ISP IP once in its first day if it does not fit your target.

The 2026 reality

How drops work now

The first-come-first-served stampede is mostly gone. Nike moved SNKRS Pass to a draw with extra bot filtering in March 2022. Its own SNKRS pages now put bots at 10–50% of entries depending on the launch and say it stops up to 12 billion bot calls a month; in 2023 its SNKRS lead said nearly half the entries on hyped releases were bots.

Shopify Plus stores can switch on bot protection that puts a CAPTCHA checkpoint in front of checkout for events of up to 60 minutes and up to 500 products. Large retailers sit behind bot-management systems such as Akamai Bot Manager, which scores every request from 0 to 100 on fingerprint and behaviour, or Kasada, which uses changing proof-of-work challenges.

The consequence is simple. In raffles and queues the bottleneck is how many of your entries pass verification, not how fast they arrive. A proxy’s value is a stable, believable identity for the whole session; the IP gets you assessed, it does not get you approved.

The market has cooled too: the share of releases reselling above retail fell from 58% in 2020 to 47% in 2024, with typical margins of 10–25%. Hype has spread to trading cards and collectibles, and the same mechanics apply there.

Pick by release

Which proxy for which kind of release

Retailers change protection between releases, so treat this as a starting point and test before release day.

Release or site typeProxySessionLocation
Raffle entries (SNKRS-style draws)Residential or ISPOne account per IP, stickyThe account’s country
Queue-based sites (Foot Locker group and similar)ISPHold the IP 10–30 min through the queueThe store’s country
Shopify Plus stores with bot protectionISPSame IP from checkpoint to paymentThe store’s country
Smaller Shopify boutiquesISP or DatacenterOne IP per taskClose to the store
European retailersISP or ResidentialStickyThe store’s country, e.g. Germany for .de shops
Creating accountsMobileSticky, 30–60 minThe account’s country
Monitors and CAPTCHA harvestersDatacenterStaticAnywhere fast; never your checkout IPs

Reviewed October 2026. Retailer protections change without notice.

Our ISP network

What you get with our ISP proxies

An ISP proxy is a static IP registered to a consumer internet provider and hosted on a server. Retail anti-bot systems see a home-broadband network; your bot gets a server’s uptime and speed.

Every address is sold to one customer while you rent it, and carries unlimited traffic on a 1 Gbps port. Check the network behind each address yourself after purchase (the ASN should be a consumer ISP), and if one does not fit your target, replace it once within 24 hours.

Be sceptical of ping claims, ours included. Northern Virginia, home of AWS us-east-1, is the largest data-center market in the US, and many bot servers and ISP ranges sit there; whether that shortens the path to a given store depends on where the store is served from. For raffles and queues, latency barely matters; consistency does.

The rest of the toolkit

Other proxy types on release day

Budget

How many IPs your release calendar needs

Plan one ISP IP per checkout task and a few datacenter IPs for monitors. The same IP can serve the same task on different retailers, but never two tasks on one site.

Checkout tasks
tasks
Monitors and harvesters
IPs
ISP IPs25

$50.00 per month at $2.00 per IP

Datacenter IPs5

$6.00 per month at $1.20 per IP


Total per month$56.00

Unlimited traffic on both, billed monthly.

Get ISP proxies

Self-serve orders go up to 100 IPs per product. Larger blocks for a release calendar are arranged with sales.

Playbook

Release-day checklist

Trust, but verify

Is your proxy really ISP?

Not every “sneaker proxy” is what it claims. Castle, an anti-bot company, bought a plan sold as sneaker proxies and analysed 4,287 of its IPs: more than 99% sat in datacenter networks.

Check before you rely on an address. Look up its ASN: a consumer ISP such as Comcast, AT&T or Spectrum is what you paid for; a hosting company is not. It takes one request.

curl -x 198.51.100.24:8080 -U "user_7f2:PASS" https://ipinfo.io/json
# "org": "AS7922 Comcast Cable Communications, LLC"  -> consumer ISP
# "org": "AS24940 Hetzner Online GmbH"              -> hosting, not ISP
Billing

Why monthly, and no day passes

ISP and datacenter IPs are rented by the month, 1 to 100 IPs per order, with unlimited traffic and no volume discount. There are no day or week passes on purpose: an address keeps a clean history across releases only if one customer holds it for longer than a weekend.

Running a bigger calendar? Talk to sales about a custom block above 100 IPs, and plan residential gigabytes for raffle entries separately, since they never expire.

Store rules and the law

  • Purchase limits and the terms of the stores you buy from apply with or without a proxy.
  • Bot laws so far cover event tickets, not sneakers: the US BOTS Act, point 23a of EU Directive 2019/2161 and the UK’s 2018 secondary-ticketing rules. The Stopping Grinch Bots Act (S.3516), introduced in the US Senate on 17 December 2025, would extend similar rules to retail purchase limits; no further action has been recorded.
  • ChronoProxy does not support ticket bots or ticketing use cases.
Not legal advice. ChronoProxy is not affiliated with Nike, adidas, Shopify or any retailer.

Sneaker proxy questions

Proxies used by sneaker bots to give each checkout task its own IP address. Today they are mostly static ISP proxies, because queues and checkpoints reward an identity that stays the same for the whole session.

ISP for checkout tasks, residential or ISP for raffle entries, mobile for creating accounts and datacenter only for monitors and CAPTCHA harvesters.

One IP per task. Ten tasks on a release means ten ISP IPs; add a few datacenter IPs if you run monitors.

Yes, the same IP can run the same task on different retailers. Do not run two tasks on one site from one IP.

We do not publish a “works on” list, because retailers change protection between releases and no honest provider can guarantee results. Test on the sites you target and replace an address within 24 hours if needed.

Hold one IP through the whole queue or checkout, typically 10–30 minutes. ISP IPs are static, so that is automatic; residential sticky sessions last up to 60 minutes.

An IP in the store’s country. For US stores, East Coast addresses sit close to many hosting regions; for EU stores, use the store’s country, such as Germany for .de shops.

No. ISP and datacenter IPs carry unlimited traffic under a fair-use policy, which matters on queue pages that refresh constantly.

Consumer providers in each country. Look up each address’s ASN after purchase: it should belong to a consumer ISP, not a hosting company, and you can replace an address once within 24 hours.

Replace it within the first 24 hours of the rental. After that, the address is yours for the month; add a spare or two if a release matters.

No. ISP and datacenter IPs are rented monthly so that each address keeps a clean, single-customer history.

Bot laws in the US, EU and UK so far target event tickets, not retail goods, but store terms and purchase limits still apply, and a US bill to extend the rules to retail was introduced in December 2025. This is not legal advice.

No. Ticketing use cases are not supported on ChronoProxy.

Keep exploring

One static IP per task, unlimited traffic.