Why SNKRS Proxies are Essential for Copping Nike

July 29, 2019

Copping Nike on SNKRS can be tricky, especially when going after those hot drops that can be gone in a matter of seconds. To avoid getting blocked or blacklisted, you’ll need to use Nike SNKRS proxies.

Types of SNKRS Drops

If you’re looking to grab a pair of hot Nike sneakers, you’ll need to understand their drop system a bit more.

Nike SNKRS does three types of launches:

FLOW － the usual first come, first serve type of release. Mostly operates on general release shoes.

LEO － a queued drop that puts you in line and gives a result in 2-3 minutes.

DAN － used for the most exclusive launches. Unlike LEO, it puts your name in a draw, not a queue. The result comes back in 10-30 minutes.

To be honest, there is not much of a difference between LEO and DAN. Even though when copping a LEO release, you’re technically not in a queue as it’s not a first come, first serve basis. The queue is just as much of a lottery as a DAN release. However, you can increase your chances by using multiple accounts. We’re onto you, Nike.

To have the best chance at copping those sneakers, you need to get your hands on a sneaker bot, such as BnB or AIO .

Why do I Need Proxies to Cook on SNKRS?

Right off the bat, we’ll let you know that you won’t get anywhere without proxies. SNKR proxies makes it look like each request is coming from a different real-life person and it doesn’t flag Nike’s systems. If several requests come from the same IP address, Nike can either block you temporarily or blacklist your IP. To avoid this, we recommend creating multiple Nike accounts with different sneaker proxies attached to each one.

Residential proxies are perfect for LEO and DAN drops. They make it look like each hit is coming from a different location. If you want to run hundreds of Nike accounts, residential proxies are king as it’s the most efficient. These proxies come in GB packages so you can think about it as a mobile data plan. To put it into perspective, running 1000 Nike tasks on one release uses anywhere from 0.3 to 0.4 GB.

Check out our residential proxy plans here to make sure you’re ready to cook the next hot drop.