How to Use Residential Proxies With Nike SNKRS: Complete 2026 Setup Guide

Nike SNKRS is the strictest sneaker platform on the internet. It runs Cloudflare Bot Management on top of Nike's own Kount integration. Getting a residential proxy setup that consistently gets through the queue takes more than "buy some proxies and paste them into your bot." Here's the actual setup.

What you need

• A bot with SNKRS support: NSB, Wrath, Balko, Prism, MEK, Cybersole, Dashe, or Cyber.
• Nike accounts warmed for at least 7 days (14+ ideal). Freshly-created accounts get soft-banned on drop day.
• Residential proxies with sticky session support. Not rotating. More on that below.
• A jig (public Nike bug that increases cop rate — check bot Discord for current)

Step 1: Pick the right country pool

Match the proxy country to the account's shipping address. Nike geo-checks the IP against the account's registered region — a US account making requests from Germany triggers instant fraud review.

• US accounts → US residential IPs
• EU accounts → same country as billing address (DE account → DE IPs)
• UK accounts → UK IPs (not "EU pool")
• JP accounts → JP IPs

SMT lets you geo-target down to country level. On the generate page, pick "Premium Residential" as your network type, then select your country.

Step 2: Sticky sessions, always

SNKRS runs a session-affinity check. If your first request lands on IP A and your second request 3 seconds later lands on IP B, you get a 403 back within the checkout flow. Rotating proxies (a fresh IP per request) will get you banned faster than any datacenter proxy could.

Use sticky sessions of 10–30 minutes. That's long enough to finish a full task chain (home → PDP → ATC → checkout → payment auth) without your IP flipping mid-flow, but short enough to release the IP once you're done.

In SMT proxy string format:

premium-residential.smtproxies.com:10000:USERNAME-country-us-session-YOURSESSION-lifetime-30:PASSWORD

lifetime-30 = 30 minute sticky. session-YOURSESSION = your task-unique session ID (any string).

Step 3: Warm the IP before drop

Don't have your first request on drop day be an ATC. Warm the IP for 30–60 seconds first:

1. Load the Nike homepage
2. Wait 15–30 seconds
3. Load a random category page (Air Force 1s, Dunks)
4. Wait another 10–20 seconds
5. Load the PDP for the drop product
6. Now ATC

Most modern SNKRS bots have a "warm-up" or "prewarm" toggle. Turn it on. If your bot doesn't, run a lightweight browser instance through the same proxy 60 seconds before task start.

Step 4: One task per IP, one IP per account

Do not share a proxy IP across accounts. Nike correlates checkout attempts by IP + account combinations, and 3 different Nike accounts checking out from the same residential IP within a 60-second window will get all 3 accounts flagged.

Task pool math:

• 20 tasks = 20 unique sticky sessions
• Each session should target the same country as its account's shipping address
• Use unique session strings per task (bot handles this automatically if configured)

Step 5: Estimate bandwidth

SNKRS drops are short — usually 10–20 minutes of active checkout traffic. For a typical 20-task run:

• Warm-up + monitor: 100 MB total (20 tasks × 5 MB warming)
• Checkout attempts: 40 MB total (20 × 2 MB per checkout chain)
• Queue holding (if FCFS): up to 500 MB if the queue is 30+ minutes

Budget 500 MB – 1 GB per drop for 20 tasks. Bigger runs scale linearly.

Common mistakes

• Using rotating instead of sticky. Instant ban. See step 2.
• Country mismatch. US account + EU IP = fraud review. See step 1.
• Fresh accounts. Nike heuristic: account age < 7 days + drop-day activity = 90% ban rate.
• Sharing IPs across accounts. Ban all connected accounts. See step 4.
• Same TLS fingerprint as datacenter attempts. If you were running the same bot on DC proxies last week and got Nike'd, your TLS is flagged. Use a different bot or wait 2 weeks.

Bot-specific config notes

NSB: Import proxies as proxy_list.txt with sticky format. Set task count = number of accounts.

Wrath: Proxy group with sticky enabled, one proxy per task strand.

Prism: Native support for lifetime parameter — just include it in the proxy string.

Cyber: Older UI, use "residential" mode and set session ID manually per task.

What if it still doesn't work?

Three usual suspects, in order:

1. Accounts too fresh — warm 2+ weeks minimum
2. Jig is stale — check bot Discord for current jig
3. Card is flagged — use a card that hasn't been used on Nike in the last 30 days

None of those are proxy problems. If you're getting past checkout but consistently getting cancels, the issue is upstream.

Get started

SMT residential proxies are $$8.50/GB with premium residential country targeting. Try 2 GB for $2 if you want to test on one drop before committing to a bigger buy.