Sneaker Proxies: The Complete Guide to Proxies for Sneaker Bots

What are sneaker proxies?

Sneaker proxies are proxies used with sneaker bots to enter raffles, join queues and check out limited releases on retail websites. A sneaker bot can fill in forms and submit checkouts in milliseconds, but retailers limit how many requests and purchases a single IP address can make. Proxies give each bot task its own IP address, so the retailer sees many separate shoppers instead of one machine.

There's nothing technically special about a "sneaker proxy". It's a regular residential, ISP or datacenter proxy, chosen and configured for the specific demands of sneaker releases: speed, clean IPs that haven't been banned on the sites you're running, and the right location. Providers that sell "sneaker proxies" usually package these up with subnets that have been tested on footsites, Shopify and Nike.

This guide covers everything from choosing the type to setting them up. For our view on providers specifically, see best proxies for sneaker bots and sneaker proxy providers compared.

Why you can't cop at scale without proxies

Retailers fight bots in layers:

• Per-IP rate limits. Too many requests from one IP and you're throttled or blocked.
• Order limits. Most releases are limited to one pair per customer, and IP is one of the signals used to link orders.
• Bot protection. Services such as Akamai, Datadome, PerimeterX (now HUMAN), Cloudflare and Kasada score every visitor. Datacenter IPs start with a worse score.
• Queue systems. Some sites put shoppers in a virtual waiting room, and each IP or session holds one position.

Running ten tasks from your home IP will get you banned or, at best, give you one entry. Running ten tasks on ten clean proxies gives you ten chances.

How sneaker releases work, and what proxies do in each

Before choosing proxies, it helps to understand the release formats you'll face, because each one stresses proxies differently.

First come, first served (FCFS)

Stock goes live at a set time and the fastest checkouts win. This is a pure speed race. What matters:

• Low latency from your bot to the proxy and from the proxy to the retailer.
• Stable connections that don't drop mid-checkout.
• IPs the site hasn't banned.

ISP proxies dominate FCFS releases because they combine speed with residential-looking IPs. See ISP proxies for sneakers.

Queues and waiting rooms

Many large retailers put shoppers in a virtual queue when a release opens. Each session holds a place, and the site decides who gets through. What matters:

• Many distinct, clean identities, because each one is a separate place in line.
• Session stability, because losing the session usually means losing your place.
• Reasonable request rates, because queue systems watch for repeated polling.

Sticky residential sessions or ISP proxies both work, depending on the site. Speed matters less than staying in the queue cleanly.

Online raffles and draws

Entries open for a period, then winners are chosen. Retailers check for duplicate entries using accounts, addresses, payment details, devices and IPs. What matters:

• A unique IP per entry, ideally from the right country or region.
• Lightweight usage, since entries are small forms.

Rotating residential proxies are the natural fit, and per-GB billing makes them cheap for this. See residential proxies for sneakers.

App-exclusive and account-based releases

Releases through a brand's app (SNKRS-style draws, for example) depend heavily on account history and device signals. Proxies matter, but account age, purchase history and device consistency matter more. Residential or mobile IPs that stay consistent per account are the safest. See Nike SNKRS proxies.

In-store raffles with online entry

Some boutiques run raffles online for in-store pickup. Entries must usually match a local address and sometimes local IPs. City-targeted residential proxies help, but winners must collect in person, so this is about legitimate local entries, not volume.

Shopify drops

Thousands of independent stores run on Shopify, and many sneaker boutiques use it. Protection varies widely from store to store: some use basic checks, others add bot protection apps or checkpoints. Datacenter proxies work on some, ISP on most. See Shopify sneaker proxies.

How a sneaker bot uses proxies

Understanding the moving parts inside a bot makes proxy decisions much easier. Most bots share the same building blocks.

Tasks

A task is one attempt to buy one item from one site with one profile. Each task usually gets its own proxy. When you hear "one proxy per task", this is what it means.

Profiles

A profile holds shipping, billing and contact details. Retailers link orders by profile details, so proxies can't make one profile look like ten people. Plan tasks around the profiles you have.

Proxy groups

Bots organise proxies into groups, such as "ISP US East", "Residential raffle UK" or "Monitor DC". You assign groups to tasks by site and role. Good grouping lets you swap a failing group in seconds on release day.

Monitors

A monitor watches product pages or APIs for restocks and releases and triggers tasks when stock appears. Monitors make lots of requests, so they need their own cheap proxies, separate from checkout proxies. See sneaker monitor proxies.

Delays and retries

Bots wait between requests (the "monitor delay" and "retry delay"). Short delays react faster but hit rate limits sooner. Your proxy count and delays should be planned together: more proxies allow shorter delays per proxy without tripping limits.

Captcha handling

Many sites present CAPTCHAs to suspicious traffic. Bots handle them with harvesters (browser windows where you or a solver complete challenges in advance) or with solving services. Proxies affect how often CAPTCHAs appear: cleaner, higher-trust IPs see fewer.

Sessions and cookies

During a checkout, the site sets cookies that tie the session together. Switching IPs mid-session usually breaks it or flags it. That's why checkout proxies need to hold the same IP for the whole flow, which static ISP proxies do naturally and sticky residential sessions do for their set duration.

ISP proxies for sneakers, in depth

Because ISP proxies are the default checkout proxy for most cooks, it's worth understanding what separates a good batch from a bad one.

Subnets and ASNs

ISP proxies come in blocks of IPs from specific internet providers. Retailers and bot protection services ban at the IP level, the subnet level and sometimes the ASN level. A batch spread across several subnets and providers survives a ban much better than a batch from a single range. When buying, ask which ISPs and how many subnets the batch spans.

"Tested on" claims

Sneaker proxy sellers often advertise which sites their batches work on. These claims can be useful but go stale quickly, since a site can ban a subnet days after a seller tests it. Treat them as a starting point and run your own test the night before a release.

Region matching

Match the proxy region to the site and to your server. A US retailer's servers or CDN edges will respond faster to proxies on the same coast as your bot server. A UK site expects UK traffic. A mismatch costs milliseconds at best and gets you blocked at worst.

Daily, weekly and monthly packages

Daily ISP packages exist because many cooks only need IPs for specific releases. They cost more per day but far less per release than a month. Monthly packages make sense if you run releases every week or use ISP proxies for account work in between. See cheap sneaker proxies.

Shared or dedicated

Shared ISP proxies are cheaper, but other cooks using the same IPs on the same release will compete with you and may get them banned. For hyped releases, dedicated IPs are worth it.

Bandwidth

ISP proxies usually include unmetered or generous bandwidth, which matters because bots poll a lot during a release. That's one reason ISP proxies beat per-GB residential for checkout traffic.

Residential proxies for sneakers, in depth

Residential proxies earn their place in a sneaker setup for raffles, account work and the toughest sites.

Rotating vs sticky for sneakers

• Rotating (new IP per request) is perfect for submitting raffle entries, where each entry is a single request or a short form.
• Sticky (same IP for minutes to hours) is needed for anything with a session: logging in, account creation, carts and checkouts. Choose a session length that comfortably covers the whole flow. Some providers offer sticky sessions of up to 24 hours, which covers even long queue waits.

Doing the per-GB math for raffles

Raffle entries are light. A simple entry might transfer tens of kilobytes; one that loads a full page in a browser might use a few megabytes.

The difference is huge. If your raffle tool supports request-based entries, residential bandwidth goes a very long way. If it uses a full browser, block images and media where the tool allows.

Region targeting

Many raffles only accept entries from certain countries, and some check that the IP matches the shipping country. Residential proxies with country, state or city targeting let you match each entry to its profile. See geo-targeted proxies.

Speed expectations

Residential proxies are slower than ISP proxies because traffic passes through real home connections. That's fine for raffles and account work, and a disadvantage in FCFS races. Use the right type for the right job rather than trying to make one type do everything.

ISP vs residential vs datacenter for sneakers

ISP proxies: the default sneaker proxy

For most sneaker cooks today, ISP proxies are the default. They combine residential-looking IP registration with datacenter speed and a static IP that doesn't drop mid-checkout. They're often sold by the day or week around big releases, which keeps costs down. The downside is that a subnet that gets flagged on a site can burn the whole batch.

Residential proxies: for raffles and the toughest sites

Residential proxies for sneakers are best for raffle entries, account creation and sites with the most aggressive bot protection. Because you pay per GB, they're cost-effective for lightweight raffle entries and expensive for heavy, browser-based checkout flows. Their weakness is speed: a home connection on the other side of the country adds latency.

Datacenter proxies: cheap but limited

Datacenter proxies for sneakers still have a role. They're good for monitors and for some smaller Shopify stores that don't use strong protection. But on major footsites and Nike, datacenter IPs are generally blocked or heavily penalised.

Which proxies for which sites

Retailers change their protection all the time, so what works for one season might not for the next. Sneaker communities and your bot's own guides are the best source for the current meta.

How many sneaker proxies do you need?

The traditional rule of thumb is one proxy per task, and often one to two tasks per proxy on lenient sites. If you run 50 tasks on a footsite, plan for roughly 25 to 50 ISP proxies. For raffles you'll generally want a unique IP per entry, which is exactly what rotating residential gives you.

More proxies isn't always better. Running hundreds of tasks on a site that only lets each account buy one pair, with a handful of accounts, just burns proxies. Our detailed guide how many proxies for a sneaker bot gives per-site ratios.

Speed: why milliseconds matter

On hyped releases, stock can sell out in seconds. Two things matter:

1. Latency from your bot to the proxy. Run your bot on a server close to the proxy's location. See sneaker bot server location.
2. Latency from the proxy to the retailer. A proxy located near the retailer's servers or CDN edge responds faster.

Measure speed with your bot's built-in proxy tester, but don't treat a low ping as a guarantee. A fast proxy that's banned on the site is still useless. See sneaker proxy speed.

Setting up sneaker proxies

Most providers deliver proxies as a list in this format:

ip:port:username:password

Paste them into your bot's proxy group, test them, and assign the group to your tasks. Residential providers usually give you a single gateway hostname with country and session parameters in the username, which you can expand into a list. Our sneaker proxy setup guide walks through it step by step, including IP whitelisting and testing.

Bot protection on sneaker sites, and what proxies can and can't do

Every major sneaker retailer uses some form of bot protection. Knowing how it works keeps your expectations realistic and points you to the right fix when things fail.

How bot protection scores you

Services such as Akamai Bot Manager, DataDome, HUMAN (formerly PerimeterX), Cloudflare and Kasada all work in broadly similar ways. They combine many signals into a score for each visitor:

• IP signals: whether the IP belongs to a hosting provider, a home ISP or a mobile carrier, its history of abuse, and how many requests it's making.
• Client signals: the TLS and HTTP/2 fingerprint of your bot, headers and their order, and whether they match a real browser.
• Browser signals: JavaScript challenges that inspect the browser environment for automation and inconsistencies.
• Behaviour signals: timing, navigation and interaction patterns.
• Account and order signals: linked profiles, payment details and addresses.

What proxies fix

• IP type. Residential and ISP IPs start with better scores than datacenter IPs on most protected sites.
• Per-IP limits. Spreading tasks across many IPs keeps each one under rate limits.
• Region checks. Region-matched IPs avoid geography-based blocks.

What proxies don't fix

• Client fingerprints. If your bot's TLS fingerprint or headers look automated, a premium IP won't save it. That's the bot developer's job, which is why bot choice matters as much as proxy choice.
• JavaScript challenges. These are solved by the bot's browser or solving modules, not the proxy.
• Behaviour. Hammering a site with short delays looks automated from any IP.
• Order linking. Shared addresses, cards and accounts link orders regardless of IPs.

Practical takeaways

1. When a site suddenly blocks everything, check your bot's announcements before blaming proxies. Protection updates often require bot updates.
2. When some proxies work and others don't on the same site, it's a proxy (subnet) problem.
3. When proxies pass tests but checkouts fail later in the flow, look at fingerprints, sessions and profiles.

See browser fingerprinting and proxies and CAPTCHAs and proxies.

How bans spread across sneaker proxies

Understanding ban scope helps you buy and use proxies more defensively.

• Single IP bans happen when one address misbehaves: too many requests, failed challenges, or abuse flags. Swap the IP.
• Subnet bans happen when a site sees bad behaviour across a range, often because many cooks used the same seller's IPs on the same release. Swap to a different subnet, not just a different IP.
• ASN-level penalties can hit IPs from an entire provider network that a site associates with bots. Switch to IPs from a different ISP.
• Account bans follow the account regardless of IP. New proxies won't help.
• Device and fingerprint bans follow your bot or browser profile.

Defensive habits: buy across subnets and ISPs, keep task counts per IP modest, avoid sellers who oversell the same ranges to everyone, and log results by subnet so you can see patterns. IP reputation is shared and it remembers, so the IP reputation and proxies guide is worth a read.

A first release, start to finish

If you've never run a bot before, here's how a sensible first release looks. It assumes a modest, low-risk setup on a Shopify boutique release.

A week before

You pick one release on a Shopify store known to be bot-friendly enough for beginners, read your bot's guide for Shopify, and set up two profiles with your own real details. You decide on ten tasks: five per profile.

Four days before

You rent a small server in the region nearest the store's main market for two days around the release, and buy ten ISP proxies for two days in the same region. You also buy a small residential balance for the store's raffle, which a friend recommended.

Two days before

You install the bot on the server, import the ISP proxies into a group called "Shopify ISP", and import a residential list (generated in your provider's dashboard with a different session ID per line) into "Raffle Resi". You enter the raffle with each profile, one residential IP per entry.

The night before

You run one proxy test against the store. Nine pass; one shows a block, so you request a replacement. You set up a monitor on a separate cheap datacenter proxy.

Release morning

Thirty minutes before the drop, you test once more. You start the tasks at the time the bot's guide recommends. The monitor detects the product; tasks add to cart and begin checkout. Three tasks hit CAPTCHAs; your harvester handles them.

After

One task checks out. You log the result: store, proxy type, seller, subnet, success. You let the dailies expire and shut down the server. Total spend is modest, and you now have a log entry and a working setup to build on.

The point isn't the outcome of one release. It's that you learned the whole process at low cost, with a clean setup you can scale. See best proxies for sneaker bots for what to buy as you grow.

Sneaker proxy pricing models compared

The right mix changes with your release calendar. Non-expiring residential traffic, such as Geonode's, is especially useful for cooks because raffle activity comes in waves rather than at a steady monthly rate.

Why sneaker proxies get banned

• The subnet is burned. Someone else already abused that IP range on the same site.
• Too many tasks per proxy. You hit a rate limit.
• Wrong region. A UK footsite won't like US IPs.
• Fingerprint mismatch. The browser or bot profile doesn't match the IP's location.
• Account linking. Multiple accounts using the same card, address or device fingerprint get linked no matter how good your proxies are.

Our troubleshooting guide covers fixes: why sneaker proxies get banned (and how to fix it).

Using Geonode for sneaker proxies

We're a Geonode affiliate, so here's a straightforward look at how its products map onto a sneaker setup, and where you might combine it with specialist sellers.

Raffles and account work: Geonode residential

Geonode's residential proxies are billed per GB, and purchased bandwidth doesn't expire. For cooks, that's the key feature: raffle seasons are uneven, and traffic that disappears at the end of a month is wasted money. Residential traffic can rotate per request for raffle entries or hold sticky sessions (Geonode lists up to 24 hours) for account logins and long queues, and it can be targeted by country, state, city or ASN to match each profile.

Checkout: Geonode ISP proxies

Geonode sells static ISP proxies, shared or dedicated, with unmetered bandwidth. These suit checkout tasks and account management where you want one fast, stable IP. As with any ISP seller, ask about subnets and test on your target sites before a big release.

Monitors: datacenter traffic

Geonode's rotating datacenter proxies are a cheap way to spread monitor requests across many IPs on sites that don't block datacenter traffic.

Where to combine with specialists

Sneaker-specific sellers often run batches tested on particular footsites for particular releases, with release-day support in Discord. Many cooks use a general provider like Geonode for raffles, accounts and monitors, and add specialist ISP batches for the biggest FCFS releases. That mix gives you flexible, non-expiring residential traffic plus the latest "tested on" checkout IPs.

A simple Geonode-based setup

1. Buy a residential balance sized to your raffle entries and account logins for the season.
2. Buy a handful of ISP proxies for account maintenance and smaller drops.
3. Use rotating datacenter traffic for monitors where sites allow it.
4. Add specialist daily ISP batches for hyped FCFS releases if your results justify it.

See Geonode for sneaker bots for a step-by-step guide, and compare options in sneaker proxy providers compared.

Pairing servers and proxies

Your bot server and your proxies form one network path, and the slowest link sets your speed.

Where to put the server

Run your bot on a server in the same region as your checkout proxies, and ideally near the retailer's infrastructure. Common choices:

Many large retailers serve traffic through CDNs with edges in many cities, so "near the retailer" often means near the major internet hubs of that region. See sneaker bot server location.

Measuring the path

Measure three things: server to proxy latency, proxy to retailer latency (your bot's proxy tester usually measures this), and total checkout time in test runs. If server to proxy latency is high, move the server or choose proxies closer to it.

Residential proxies and servers

Residential exits are scattered across a region, so latency varies. If you use residential for checkout on a site that requires it, target the state or city closest to your server where the provider allows it.

Home vs server

Running a bot from home works, but your home connection becomes part of the path, and your home IP can leak if a proxy fails and the bot falls back to a direct connection. Servers avoid both problems. If you do run from home, check that your bot is set to fail rather than connect directly when proxies fail.

CAPTCHAs, harvesters and proxies

CAPTCHAs are a tax on suspicious traffic. Proxies don't solve CAPTCHAs, but they strongly influence how many you see.

• Higher-trust IPs see fewer challenges. ISP and residential proxies usually trigger fewer CAPTCHAs than datacenter proxies on protected sites.
• Harvesters need good proxies too. If you pre-solve CAPTCHAs in harvester windows, those windows often need to use the same proxy as the task, or at least a proxy from the same region, for the solved token to be accepted. Check your bot's documentation.
• Burned IPs see endless challenges. If one proxy keeps getting CAPTCHAs while others don't, retire it.
• Too many requests per IP increase challenges. Lower task counts per proxy or lengthen delays.
• Solving services cost money per CAPTCHA, so better proxies can pay for themselves in fewer solves.

See CAPTCHAs and proxies.

Accounts and proxies

Many releases require accounts, and accounts carry history. Proxies play a supporting role in keeping them healthy.

Creating accounts

Account creation is one of the most scrutinised actions on retail sites. Use residential or mobile IPs, one per account, from the region the account will shop in. Create accounts gradually rather than in bursts, and give them time and normal activity before relying on them.

Maintaining accounts

Log in to each account from a consistent location. If an account always logs in from the same ISP proxy or the same residential region, it builds a stable history. Jumping between countries and ISPs triggers security checks.

One account, one identity

Keep each account's IP, browser profile, address and payment method consistent and separate from other accounts. Proxies are only one part of the identity; the others matter at least as much.

A word on rules

Most retailers' terms limit accounts per person and purchases per customer, and they cancel orders and close accounts they link together. Proxies don't change the terms you agreed to. Know the risks before you build an account-heavy setup. See are proxies legal?.

Sneaker monitors in depth

Monitors are often treated as an afterthought, but a slow or blocked monitor means your tasks start late.

• Separate pools. Never share monitor proxies with checkout proxies. Monitors make far more requests and are more likely to get IPs flagged.
• Cheap IPs. Datacenter proxies or rotating datacenter traffic are usually enough for monitors on sites that allow them. Use residential only for sites that block datacenter traffic, and keep the monitor's requests lightweight.
• Delays. Set monitor delays based on how many proxies you have. With more proxies, each one can wait longer between requests while the monitor as a whole still checks frequently.
• Endpoints. Many monitors watch lightweight product endpoints rather than full pages, which keeps bandwidth low.
• Redundancy. Run two monitors on different proxy pools for important releases.

See sneaker monitor proxies.

Testing sneaker proxies the right way

Most bots include a proxy tester. Used well, it saves releases. Used badly, it burns IPs.

1. Test against the actual site, not against a generic speed test or a search engine. A proxy can be fast and banned at the same time.
2. Test once the night before and once 30 to 60 minutes before a release. Repeated testing can flag IPs.
3. Read the result, not just the speed. A "403" or "banned" result means the IP is unusable on that site, however fast it is.
4. Group results by subnet. If one subnet shows bans, assume the rest of it is at risk.
5. Keep a log of which proxies and subnets worked on which sites. Over a season, this log becomes your best buying guide.
6. Ask for replacements quickly. Many sellers replace IPs that are banned on arrival, but only within a short window.

What do sneaker proxies cost?

ISP proxies are commonly sold in daily, weekly and monthly packages. Daily packages around a single release can be a few dollars per proxy, while monthly ISP proxies often fall in the low single-digit dollars per IP. Residential sneaker plans are usually sold per GB. If you're on a budget, read cheap sneaker proxies and our broader guide to cheap proxies.

Buying checklist for sneaker proxies

• Does the provider say which sites their subnets are tested on?
• Can you choose the region (US East, US West, UK, EU)?
• Are the IPs dedicated to you, or shared with other cooks?
• Is there a daily or weekly package for single releases?
• What's the replacement policy if a subnet is banned on arrival?
• Is support active on release days, usually through Discord?
• Do they publish a test proxy or trial?

A complete release-day timeline

Knowing what to do and when makes more difference than any single proxy purchase. Here's a typical timeline for a hyped release, assuming you run a bot on a server.

One week before

• Confirm the release details: sites, regions, release method (FCFS, queue, raffle or draw).
• Plan task counts against the profiles and accounts you actually have. Proxies without matching profiles are wasted money. See how many proxies for a sneaker bot.
• Order raffle traffic (rotating residential) and start entering raffles as they open.
• Check your server provider has capacity in the region you need. See sneaker bot server location.

Two to three days before

• Order checkout proxies (usually daily or weekly ISP proxies) for the release window. Ask the seller which sites the batch is performing on.
• Spin up your server and install or update your bot.
• Set up proxy groups by site and role: checkout, raffle, monitor. See sneaker proxy setup guide.

The night before

• Run one proxy test against the target site. Remove anything that fails or shows bans; request replacements from the seller.
• Spread tasks across subnets so a single subnet ban doesn't wipe out your run.
• Check monitors are running on separate proxies. See sneaker monitor proxies.

Release morning

• Retest once, 30 to 60 minutes before the drop. Don't test repeatedly; constant tests can flag IPs.
• Start tasks at the time your bot's guides recommend for that site.
• Watch for errors and switch to your backup proxy group if a subnet starts failing.

After the release

• Note which proxies and subnets performed, per site. This log is gold for future releases.
• Rest or release proxies you no longer need. Daily packages simply expire.
• Check orders for cancellations, which usually point to profile linking rather than proxy problems. See why sneaker proxies get banned.

How sneaker proxies evolved

The history explains why today's advice looks the way it does.

The datacenter era

In the early days of sneaker bots, retailers mostly limited requests per IP, and cheap datacenter proxies were enough. Cooks bought large lists of datacenter IPs and ran hundreds of tasks. As retailers adopted commercial bot protection, datacenter ranges became easy to identify and block on the major sites.

The residential shift

Residential proxies, which route traffic through real home connections, offered much higher trust. They became the standard for the strictest sites and for raffles. But their speed and per-GB pricing made them awkward for FCFS checkouts, where bots poll heavily and every millisecond counts.

The rise of ISP proxies

ISP proxies combined the best of both: IPs registered to consumer ISPs, hosted on fast datacenter infrastructure, static for as long as you rent them. They quickly became the default checkout proxy. The trade-off is limited supply: a few providers and subnets serve a large share of the market, so bans spread quickly when ranges are overused.

Today

Modern setups mix types by role: ISP for checkout, rotating residential for raffles and accounts, datacenter for monitors, and occasionally mobile for the hardest account work. At the same time, bot protection increasingly weighs fingerprints, behaviour and order linking, so proxies are one part of a bigger picture rather than the whole answer.

A well-run intermediate setup, end to end

Here's what a solid setup looks like for a cook who runs several releases a month and wants consistent results without overspending.

• Servers: one monthly server in US East, plus a London server rented by the day for EU releases.
• Checkout proxies: 30 monthly ISP proxies across three subnets from two different sources for regular drops, plus daily batches from a specialist seller for hyped FCFS releases.
• Raffle and account proxies: a non-expiring residential balance with country and state targeting, sized to a season of entries. A provider such as Geonode fits here, because unused traffic carries into the next season.
• Monitor proxies: a small datacenter pool or rotating datacenter traffic, separate from everything else.
• Groups: per site and role, with reserves set aside.
• Process: one test the night before and one shortly before each release, results logged after every release, and a monthly review of cost per checkout by site.
• Security: sub-users per bot instance, credentials stored outside chat, passwords rotated after sharing screens.

This setup isn't the cheapest possible, and it isn't the most expensive. It's built to be resilient: no single seller, subnet or server can take down a whole release, and the results log steadily improves buying decisions.

Sneaker proxies compared with other proxy uses

If you also use proxies for other work, or you're coming to sneakers from scraping or social media, the differences are worth knowing.

Skills transfer well between them: measuring success rates, logging results and matching proxy type to the job are the same everywhere. See the best proxies guide for the bigger picture.

Before your first sneaker proxy purchase

Run through these questions:

1. Which release, which site, which region, which release method?
2. How many profiles do you have, and therefore how many tasks make sense?
3. Does your bot support the site, and what proxy type does its guide recommend?
4. Have you rented a server in the right region, or will you run from home?
5. Do you need checkout proxies, raffle traffic, monitor proxies, or all three?
6. Does the seller offer replacements, and how long is the window?
7. Do you have a plan to log results?

If you can answer all seven, you're ready to buy. If not, the answers will save you more money than any discount code.

Quick answers to common cook questions

Should my proxies match my shipping address?

For raffles and region-locked releases, matching the proxy's country (and sometimes state or city) to the profile's address is sensible, because retailers can compare them. For FCFS checkouts, region matching matters more for speed than for address checks.

Can I reuse raffle proxies for the next raffle?

With rotating residential proxies, every entry gets a fresh IP from the pool anyway, so there's nothing to reuse. With static proxies, avoid entering the same raffle twice from one IP.

Do I need IPv6 proxies for sneakers?

Generally no. Most sneaker setups use IPv4. Some sites support IPv6, but support and treatment vary, and bot guides rarely recommend it.

Why do my proxies pass the bot's test but fail during the release?

Release traffic is different from a test: more requests, queue systems, CAPTCHAs and protection that tightens under load. Proxies that pass a quiet test can still be rate-limited or challenged during a busy drop. Spread tasks across more subnets and keep task counts per proxy low.

Should I buy proxies from the same company that sells my bot?

Some bot developers partner with proxy sellers. That can be convenient, and the proxies may be tested with the bot, but compare prices and results like any other seller.

Can a VPN replace sneaker proxies?

No. A VPN gives you one shared IP that many other people also use, often from a known VPN range that retailers block. It can't give each task its own IP. See proxy vs VPN.

Is it safe to share proxies with friends?

Only through sub-users with separate credentials and limits. Sharing one set of credentials means one person's mistake affects everyone, and you can't see who used what.

What should I do with leftover residential traffic?

If it doesn't expire, keep it for the next season of raffles or for account maintenance. If it expires, plan smaller purchases next time.

How do I know if a proxy seller is reselling someone else's network?

You often can't know for certain, but there are clues: identical gateway hostnames or username syntax to a known provider, identical subnets reported by other cooks, or a seller who can't answer basic questions about where IPs come from. Reselling isn't bad in itself, but it matters if you're trying to spread risk across sources. Two sellers on the same upstream network are effectively one source.

What's a reasonable success rate for sneaker proxies?

There isn't a universal number, because success depends on the site, the release, your bot and your profiles as much as on proxies. A more useful measure is your proxy test pass rate on the target site (ideally well above 90% for a fresh batch) and your cost per checkout over a season.

Do I need a separate proxy for my harvester?

Often yes. Many bots work best when CAPTCHA tokens are solved from the same IP, or at least the same region, as the task that uses them. Check your bot's documentation, because the recommended setup differs between bots and sites.

When should I upgrade from dailies to monthly ISP proxies?

When you run releases often enough that the monthly price is lower than the total you'd spend on dailies, or when you need ISP proxies between releases for account work. Your results log and release calendar will tell you which month that happens.

Is it worth running releases in other countries?

Only if you have profiles, addresses and payment methods that genuinely fit those markets, and the release ships there. Region-locked releases check much more than IP. When you do run international releases, buy proxies and servers in that region, and expect different site mixes and proxy prices from the US.

What's the single biggest improvement most cooks can make?

Keeping a results log. It costs nothing, and after a dozen releases it tells you which sellers, subnets, proxy types and regions actually work for your bot on your sites. Every other decision in this guide gets easier once you have that data, from which seller to use next month to whether a hyped release is worth running at all. Start the log with your very next release, even if it's a small one, and review it every month.

Sneaker proxy setups by budget

Whatever the budget, the principle is the same: spend the most on checkout proxies for the sites that matter, keep monitors cheap and separate, and buy raffle traffic by the gigabyte. For more on keeping costs down, read cheap sneaker proxies and our pillar guide to cheap proxies.

Sneaker proxies outside the US

The same principles apply in the UK, EU and Asia-Pacific, with a few differences:

• Smaller ISP pools. UK and EU ISP proxies are less plentiful and can cost more than US ones. See UK proxies.
• Region-locked releases. Many European and Asian releases only ship within the region, so proxies and profiles must match.
• Different site mixes. Independent boutiques and regional raffles play a bigger role in some markets, which favours residential proxies.
• Server locations. London, Frankfurt and Amsterdam are common hubs for EU releases.

Evaluating a sneaker proxy seller

The sneaker proxy market has dozens of sellers, from large providers to one-person resellers. A few questions separate the good ones from the rest.

Where do the IPs come from?

A seller who resells another network adds a layer between you and the source. That isn't necessarily bad, but you should know. Ask which ISPs the ISP proxies come from and whether residential traffic is their own network or a reseller arrangement.

How fresh are the subnets?

Ask when the current batch's subnets were introduced and which sites they've been tested on recently. Good sellers rotate in fresh ranges and say so.

What's the replacement policy?

The best sellers replace IPs that are banned on arrival or fail tests within a set window. Get the details before you buy.

What does release-day support look like?

Most sneaker sellers support customers through Discord. Check how active the support channels are around releases, and whether staff answer technical questions or just post promotions.

Are there reviews from real results?

Look for results posts in cook groups that mention the seller, the site and the outcome. Be wary of review sites and influencers who don't disclose their commissions.

How do they handle payments and refunds?

Official website checkout with clear terms is better than direct messages and payment links. Never pay a "support" account that contacts you first.

Do they explain their limits?

Sellers who explain that no proxy works everywhere and tell you which sites their batches struggle on are usually more trustworthy than those who promise guaranteed success.

See sneaker proxy providers compared and proxy provider red flags.

Sneaker proxies by setup type

Desktop bots on a server

The classic setup. The bot runs on a server near the retailer, with proxies in the same region. Everything in this guide applies directly.

Desktop bots at home

Workable for small setups, but latency includes your home connection, and a proxy failure could expose your home IP if the bot falls back to direct connections. Make sure fallback is disabled.

Cloud-hosted bots

Some bots run in the developer's cloud and let you add your own proxies or include proxies in the subscription. Follow the bot's guidance on proxy types and regions; the bot's servers determine one end of the network path.

Browser-based tools and extensions

Autofill extensions and browser-based tools run in your normal browser. They use your system or browser proxy settings. For a single extra identity, a residential proxy with a browser extension is the simplest setup. See browser proxy settings.

Mobile apps

For app-based releases, the phone's connection matters. Some people use mobile proxies or a proxy configured in the phone's Wi-Fi settings, but app releases rely heavily on account and device history, so proxies play a smaller role. See proxy setup on iPhone and Android.

What milliseconds actually buy you

Speed is the most marketed sneaker proxy feature, and also the most misunderstood.

• On FCFS releases, every step of checkout involves a request through the proxy. If each round trip is 50 ms faster and checkout takes ten requests, you save half a second. On a release that sells out in seconds, that can matter.
• But speed only counts if the request succeeds. A proxy that's 20 ms faster and gets challenged twice as often is slower in practice.
• The bot's own speed matters more for many steps: how fast it parses responses and submits the next request.
• Queue releases reward stability over speed. Your position depends on when you joined and how the site's queue works, not on the last few milliseconds.
• Raffles don't reward speed at all.

So measure speed, but rank proxies on success first. A sensible test ranks proxies by "passes the site test" and then by latency among those that pass. See sneaker proxy speed.

The data worth logging for every release

A results log turns guesswork into a strategy. For every release, record:

After ten or twenty releases, patterns appear: which sellers work on which sites, which regions matter, which proxy types are worth their price. That's the knowledge experienced cooks rely on, and you can build it yourself.

Why residential and ISP proxies work together

New cooks often ask which single proxy type they should buy. The honest answer is that most successful setups combine them, because each solves a different problem.

• ISP proxies win speed races and keep checkout sessions stable.
• Rotating residential proxies give every raffle entry and new account its own trusted IP.
• Datacenter proxies keep monitors cheap.

A provider that offers more than one type under one account makes this simpler to run. Geonode, for example, offers residential traffic that doesn't expire, static ISP proxies with unmetered bandwidth, and rotating datacenter traffic. Whether you use one provider or several, think in roles (checkout, raffle, account, monitor) and buy the cheapest proxy that does each role well.

Mistakes new cooks make

1. Buying a month of proxies for one release instead of a daily package.
2. Running every task through one subnet.
3. Using monitor proxies for checkout.
4. Testing proxies against Google rather than the actual retailer.
5. Assuming residential is always better. For checkout races, ISP proxies usually win on speed.
6. Ignoring profiles. Duplicate cards and addresses get orders cancelled no matter how good the proxies are.
7. Buying from the cheapest seller with no replacement policy.

Sneaker proxy myths

"Faster proxies always cook more"

Speed only counts if requests succeed. Clean IPs that pass the site's checks matter first; speed is a tiebreaker among proxies that work.

"Residential is always safer than ISP"

Residential IPs are more diverse, but on FCFS releases their speed and occasional instability cost checkouts. ISP proxies are usually the better checkout tool; residential shines for raffles and accounts.

"More proxies means more pairs"

Only if you have the profiles, accounts and payment methods to match. Proxies without matching profiles are money spent on nothing. Retailers link orders by much more than IP.

"Expensive proxies come with guaranteed success"

No seller controls a retailer's bot protection. Premium sellers can offer fresher subnets and better support, but nobody can guarantee a checkout.

"Once a proxy works on a site, it always will"

Sites update protection and ban ranges continually. Re-test before every release.

"Testing proxies a lot keeps them healthy"

The opposite. Repeated testing against a site creates traffic that can flag IPs. Test once the night before and once shortly before the release.

"Mobile proxies are the ultimate sneaker proxy"

They're the most trusted IPs, but slow and expensive for checkout. They're a specialist tool for account work on the strictest platforms.

"Proxies make bots undetectable"

Proxies handle one layer of detection: the IP. Fingerprints, behaviour and order linking are separate layers your bot and your profiles must handle.

Proxy assignment strategies inside your bot

How you assign proxies to tasks affects both success and ban risk.

One-to-one

Each task gets its own proxy for the whole release. Simple, predictable, and the safest default on strict sites.

Rotating within a group

Tasks pull the next proxy from a group when they retry or restart. Useful when some proxies fail mid-release, but make sure a task keeps its proxy for the duration of a checkout session.

Spread across subnets

When assigning a group to tasks, interleave subnets so neighbouring tasks use different ranges. If one subnet gets banned, you lose a fraction of tasks, not a block of them.

Reserve proxies

Keep 10 to 20% of proxies out of the initial assignment as reserves. When a proxy fails during the release, swap in a reserve rather than reusing an active proxy and doubling its load.

Separate restock proxies

If you run tasks for restocks after the main release, consider fresh proxies. The ones used during the release may be rate-limited or flagged.

Restocks and late releases

Restocks happen after the main release, often unannounced. They reward monitors and patience.

• Keep monitors running on cheap, separate proxies after the release window.
• Use fresh checkout proxies if possible, since release-day proxies may have been flagged.
• Watch request rates. Long-running monitors with short delays are a common reason for bans. Lengthen delays and add proxies rather than polling faster.
• Expect smaller quantities. Restocks are often small, so don't buy a large new batch of dailies on a hunch.

When to give up on a site

Sometimes a site's protection gets ahead of your setup. Signs it's time to step back:

• Every proxy type, from several sellers, fails tests on the site.
• Your bot developer has announced the site is unsupported or under maintenance.
• Cook group results for the site have dried up.
• Your cost per checkout on the site is higher than the profit (or the value to you) of a pair.

Stepping back saves money. Sites often become workable again after bots update, and your results log will tell you when to return.

Watching your proxies during a release

On release day, you need to know quickly when proxies fail.

• Watch the bot's task log for patterns: many tasks failing at the same step usually means a site-side change; tasks failing on specific proxies usually means banned IPs.
• Keep your provider dashboard open to see usage and any service notices.
• Have backup groups ready so you can switch a failing group without re-importing.
• Don't panic-buy mid-release. New proxies bought in the middle of a drop rarely arrive, import and test in time. Plan reserves in advance instead.

Regional considerations within the US

The US is large enough that region choice matters even within the country.

• US East (Virginia, New York, New Jersey) hosts a lot of retail infrastructure and many cooks' servers. It's the default for most US releases.
• US West (California, Oregon) can be faster for retailers with West Coast infrastructure.
• Central US sometimes offers a compromise for sites whose infrastructure is spread across the country.

Test both coasts for the sites you run most, record the results, and stick with what your data shows. When using residential proxies for US raffles, state targeting can help match entries to profile addresses where the raffle checks location.

Staying safe in the sneaker proxy scene

The sneaker world moves fast and runs on Discord, which makes it a favourite hunting ground for scammers. Protect your money and your proxies:

• Never paste proxy lists in public channels. Anyone who copies them can burn your IPs or your bandwidth. Share setups as screenshots with credentials blurred, or not at all.
• Use sub-users where your provider offers them. Give each teammate or server its own credentials, so one leak doesn't expose everything.
• Be wary of "free proxy" and "free bot" giveaways. Cracked bots and unofficial tools are a classic way to spread malware that steals account logins, payment details and proxy credentials.
• Verify sellers before paying. Check that a support account in a Discord server really belongs to the seller, and buy through the official website rather than direct messages. Impersonation is common.
• Change proxy passwords after sharing a screen, swapping servers or removing someone from your group.
• Keep payments traceable. Pay through methods with buyer protection where you can, and keep receipts.

If something feels off, it usually is. A legitimate seller will happily answer questions on the official support channel and won't pressure you into a rushed payment before a drop.

For vetting sellers properly, see sneaker proxy providers compared and proxy provider red flags. For saving money safely, see cheap sneaker proxies.

Site-by-site notes

Retailers change their defences constantly, so treat these notes as patterns rather than guarantees. The best current information always comes from your bot's documentation and active cook groups.

Nike and SNKRS

Nike's releases lean heavily on account history, device signals and draw mechanics. Proxies matter for keeping each account's location consistent and for avoiding linked activity, but a clean IP won't rescue an account with no history or a shared payment method. Residential IPs that stay consistent per account, used gently, are the common approach. See Nike SNKRS proxies.

Foot Locker, Champs and the footsite family

These sites share platforms and protection, and they've historically been sensitive to IP reputation and region. ISP proxies in the right region are the default, spread across subnets so a single ban doesn't take out the whole batch. Queue behaviour means session stability matters. See footsites proxies.

adidas and CONFIRMED

adidas releases often combine app-based draws (CONFIRMED) with web releases. Account health and device consistency matter for the app; web releases may favour residential or ISP IPs depending on the protection in use at the time. See adidas CONFIRMED proxies.

Shopify boutiques

Hundreds of sneaker and streetwear boutiques run on Shopify, and protection ranges from almost none to strong bot protection apps and checkpoints. Some stores work with datacenter proxies; most of the popular ones need ISP. Because Shopify checkouts share a common structure, a well-configured bot can run many stores, but each store's protection is its own. See Shopify sneaker proxies.

European retailers and raffles

Many European releases run through raffles at boutiques and larger chains. Raffle entries usually need IPs from the right country and profiles with matching addresses. Rotating residential with country targeting is the standard choice. For FCFS releases at European chains, London, Frankfurt and Amsterdam ISP proxies paired with nearby servers are common. See UK proxies.

Streetwear brand drops

Weekly streetwear drops are short, intense FCFS races with heavy traffic. Speed and clean ISP IPs matter most, along with strong monitoring. Many of these drops are also popular targets for bot protection, so expect the meta to change often.

Mobile proxies for sneakers

Mobile proxies come up often in sneaker circles, usually for account work.

• Where they help: account creation and logins on the strictest sites and apps, where carrier IPs carry the most trust because many real users share them.
• Where they don't: FCFS checkouts, where mobile connections are slower and less predictable than ISP proxies.
• Cost: high, whether per GB or per port. Use them for the small number of actions that need them, not for bulk traffic.
• Rotation: good mobile products let you change IP on demand. For account work, keep the IP stable during a session and rotate between accounts.

For most cooks, residential proxies cover account work well enough, and mobile is a specialist tool for the hardest cases. See mobile proxies and best mobile proxies.

Troubleshooting sneaker proxies: a quick matrix

For a deeper walkthrough, see why sneaker proxies get banned.

Keeping up with the sneaker proxy meta

The "meta" is the community's current understanding of what works on each site. It shifts with every protection update. Ways to stay current:

• Your bot's own channels. Bot developers publish site-specific guidance, recommended proxy types and settings.
• Cook groups. Paid communities share release information, success reports and proxy recommendations. Results posts show which proxies worked on which sites.
• Your own log. Record, for every release, which proxy types, sellers and subnets you used per site, your success rate and any errors. Your own data beats anyone's opinion for your setup.
• Seller updates. Good proxy sellers post which sites their batches are performing on and when they've refreshed subnets.

Be sceptical of any claim that a single proxy product works everywhere. The sites that matter most change most often.

Collectors, resellers and the ethics question

People use sneaker proxies for different reasons. Some are collectors trying to get one pair of a shoe they love in a market where bots buy most of the stock. Others run reselling businesses. Either way:

• Bots and multiple entries usually break retailers' terms. Orders can be cancelled and accounts closed. Using proxies is legal in most places, but terms of service still apply.
• Consumer protection and anti-bot laws vary by country and product category. Some jurisdictions restrict bots for specific goods such as event tickets. Sneakers are not usually covered, but check your local rules.
• Proxy networks should be legitimate. Using residential IPs from networks built on infected devices harms real people. Choose providers that explain their sourcing. See ethically sourced proxies.
• Scams target the scene. Fake sellers, cracked bots and phishing are common. See the safety section above.

We explain how sneaker proxies work because people ask and because the technology is the same as in many other industries. What you do with it is your responsibility.

Sneaker proxy glossary

Planning a sneaker proxy budget for a whole season

Most cooks overspend because they buy proxies release by release, in a rush, at whatever price is available. Planning a season smooths that out.

Step 1: Map the calendar

List the releases you realistically intend to run over the next three months, with site, region and release method. Mark which ones are hyped (worth premium checkout proxies) and which are routine.

Step 2: Estimate checkout proxy days

For each release, estimate the number of ISP proxies you'll use and for how many days. A hyped FCFS release might need 25 to 50 proxies for one or two days; a routine Shopify drop might need ten. Add them up: this is your checkout proxy-days for the season.

Step 3: Compare daily vs monthly

If your proxy-days for a region exceed roughly the number of days that makes a monthly package cheaper, buy monthly for that region. Otherwise buy dailies per release. Many cooks end up with a small monthly ISP base for regular use plus dailies for the big releases.

Step 4: Estimate raffle traffic

Count expected raffle entries for the season and multiply by data per entry using the table in the residential section. Add 30% for retries and account logins. Buy that much residential traffic, preferably non-expiring so unused traffic carries into next season.

Step 5: Budget monitors and servers

Monitors: a small datacenter pool or a little rotating datacenter traffic. Servers: by the day for big releases, or monthly if you run every week.

Step 6: Track cost per pair

After each release, record what you spent on proxies and servers and how many pairs you checked out. Cost per successful checkout is the sneaker equivalent of cost per successful request. It tells you which sites and which proxy types are worth it.

A table like this quickly shows where your money works hardest. For many cooks, raffles turn out to be the cheapest wins per dollar, and some FCFS releases cost far more than the profit on a pair.

Setting up sneaker proxies in your bot: a closer look

The setup section above covers the basics. Here are the details that trip people up.

Formats

Most bots expect ip:port:user:pass, one per line. Some accept user:pass@ip:port. Residential providers often give you a single gateway with targeting and session parameters in the username. To use them in a bot, generate a list where each line has a different session ID, so each task gets its own IP:

gateway.example.com:9000:customer-USER-country-us-session-a1b2c3:PASS
gateway.example.com:9000:customer-USER-country-us-session-d4e5f6:PASS
gateway.example.com:9000:customer-USER-country-us-session-g7h8i9:PASS

Every provider's syntax is different. Most dashboards include a generator that produces these lists for you, with your chosen country, session type and session length. Geonode's dashboard, for example, generates endpoints in host:port:username:password format. See sneaker proxy setup guide.

Whitelisting

If your provider supports IP whitelisting, you can add your server's IP and drop the username and password. Remember to update the whitelist whenever you change servers, or every proxy will fail with authentication errors.

Grouping

Create separate groups per site and role: "FL ISP East", "Shopify ISP", "Raffle Resi UK", "Monitor DC". Never mix monitor and checkout proxies in one group.

Testing after import

Run the bot's proxy test against the target site once after importing. Remove failures and request replacements.

Fallback behaviour

Check what your bot does when a proxy fails. The safe setting is to retry with another proxy or stop, never to fall back to a direct connection from your server or home IP.

Sneaker proxy setups for groups and teams

When several people run bots together, coordination becomes a proxy question.

• Avoid overlap. Two teammates running tasks on the same subnet for the same release compete with each other and double the chance of a subnet ban. Assign subnets per person.
• Use sub-users. If your provider supports sub-users, give each member their own credentials and traffic limits. One leak or one runaway task doesn't affect everyone.
• Pool purchasing power. Groups can buy larger packages at better prices and split them.
• Share results, not credentials. Share which proxies and settings worked; never paste proxy lists in shared channels.
• Spread sources. Buy checkout batches from more than one seller, so one burned upstream doesn't sink the whole team.

More sneaker proxy questions, answered

How many tasks per proxy is safe?

On strict sites, one task per proxy. On lenient sites, two to three can work. Start conservative and increase only if your logs show no rate limiting or bans.

Do I need different proxies for every site?

Not necessarily different proxies, but you should test each batch on each site. An ISP batch can be clean on one footsite and banned on another. Grouping proxies by site lets you track this.

Should I use residential or ISP proxies for queues?

Either can work. ISP proxies give speed and stability; sticky residential sessions give more IP diversity. If the site is strict about IP reputation and your ISP batch is flagged, residential may get further. Test both on smaller releases.

Can I use the same proxies for raffles and checkouts?

You can, but it's better not to. Raffle traffic suits rotating residential (unique IP per entry), while checkouts suit static ISP. Mixing them wastes money on one side and performance on the other.

How long do ISP proxies last before they're banned?

There's no fixed answer. A clean subnet can work for months on one site and be banned on another within days. That's why sellers sell daily and weekly packages and why tracking results per subnet matters.

Is it worth paying for "premium" sneaker proxies?

Sometimes. Premium usually means fresher subnets, more providers, tested batches and better support. For hyped FCFS releases with real profit potential, it can be worth it. For routine drops and raffles, standard ISP and residential proxies are usually enough.

Can I run sneaker bots without any proxies?

For a single task on a single site, maybe. Beyond that, your home or server IP will hit rate limits and get blocked quickly, and you'll only ever get one entry.

Do proxies help with app-only releases?

Less than with web releases. App draws weigh account history and device signals heavily. Consistent residential or mobile IPs per account help keep accounts healthy, but they won't win draws on their own.

What's the best provider for sneaker proxies?

The one whose IPs work on the sites you run, in the regions you need, at a cost per checkout that makes sense. For flexible residential and ISP proxies under one account, Geonode is a solid option; for the latest tested footsite batches, specialist sellers are worth comparing. See best proxies for sneaker bots.

Your sneaker proxy checklist

Before the season

• Calendar of releases with site, region and method
• Budget for checkout proxy-days, raffle traffic, monitors and servers
• Providers chosen for residential, ISP and monitor traffic
• A results log ready to fill in

Before each release

• Proxies grouped by site and role
• One test against the real site the night before
• Tasks spread across subnets
• Monitors on separate proxies
• Server in the right region
• Fallback set to "fail", not "direct"

After each release

• Results logged by proxy, subnet and site
• Replacements requested for banned IPs
• Unused dailies allowed to expire
• Cost per checkout calculated

Follow this checklist, keep your log, and your proxy spend will steadily move towards the sites and proxy types that actually work for you.

FAQ

What are the best proxies for sneaker bots?

For most sites in 2026, ISP proxies are the best general-purpose sneaker proxies, with rotating residential proxies used for raffles and the hardest sites. See best proxies for sneaker bots.

Can I use free proxies for sneakers?

No. Free proxies are slow, unreliable and almost certainly banned on every major sneaker site already.

Do I need a server for my sneaker bot?

Not always, but running your bot on a server near your proxies' location reduces latency and keeps your home connection out of the picture. See sneaker bot server location.

Are sneaker proxies the same as residential proxies?

Sometimes. "Sneaker proxies" is a marketing label for proxies chosen for sneaker sites. They may be residential, ISP or datacenter. See residential proxies.

Can one proxy be used for multiple tasks?

Yes, on lenient sites, but you increase the chance of hitting rate limits and having orders linked. One proxy per task is the safe default.