Getting frustrating at the 2002 and losing queue position

[ibiteyourankle]

The 2002 error is not due to the client's end FOR THE MOST PART. It's the overload of the server's "number crunching" capacity and connection priority.

Even if you have a super duper connection and not on wifi, you still might/will experience the problem because every connection has some sort of packet loss. Direct connect just has a lower amount. If the number of hops from you to the data center is high, you will most likely experience more 2002 disconnections. This is because every hop you do, you lose some packets and your client side needs to resend. So, math wise (below are arbitrary numbers):

• Let's say you have 10 hops from you to the server and you lose 1 packet for each hop. That's 10 re-request that needs to be done.

Now for those that have more than 50 hops....you can see what is going on. This is usually not a factor if things are running normally because the packets travel super fast (unless you have 200+ MS latency...then it's partly you), but, with how overloaded the servers are...it does become a big factor.

If you want to check how many hops you have, just do a tracert to the servers. Remember, each hop has a packet loss of some sort. Each packet loss needs a resend of the packet. Each send and send back (round trip) is dictated by your latency (i.e. ping in ms). If you put it all together:

• High packet loss due to a lot of client to server hops causes 2002

• High latency (that's why wifi is not a good idea because it adds more to the latency) causes 2002

• A lot of hops plus high latency...feels bad, man