Concrete proof finally provided that the 2002 error has NOTHING is server side issue

[Catwho]

Sometimes it's not your equipment nor the data center equipment, but the nodes connecting you in between.

For those who aren't PC savvy, here is how you can see the router your computer is using:

Go to the website ARR Server Status: https://arrstatus.com/

Click on your data center. At the bottom of the list of servers is an IP address for the lobby server. The current ping time from their website to the lobby of Primal, my DC, is 155 ms, which is..... not great. There's a traffic jam on the internet between this website and the lobby server.

Take that IP address, and on Windows, open up a command prompt. Click on Start and type in the letters CMD to open it up.

In the command prompt, type in tracert "server IP address" (without the quotes) and let 'er rip.

This is what mine just spit out:

Tracing route to 204.2.229.10 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     8 ms     7 ms     7 ms  096-034-004-140.biz.spectrum.com [96.34.4.140]
  4    10 ms    10 ms    10 ms  096-034-072-047.biz.spectrum.com [96.34.72.47]
  5    16 ms    15 ms    15 ms  bbr02atlnga-bue-3.atln.ga.charter.com [96.34.2.72]
  6    14 ms    12 ms    11 ms  bbr02atlnga-tge-0-2-0-0.atln.ga.charter.com [96.34.3.111]
  7    10 ms    12 ms    10 ms  atl-b24-link.ip.twelve99.net [62.115.179.146]
  8    12 ms    11 ms    13 ms  ae-2.r04.atlnga05.us.bb.gin.ntt.net [129.250.9.21]
  9    12 ms    10 ms    11 ms  ae-14.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.202]
 10    30 ms    32 ms    30 ms  ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
 11    75 ms    72 ms    71 ms  ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12    69 ms     *       70 ms  ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
 13    76 ms    78 ms    75 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 14    79 ms    75 ms    76 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
 15    74 ms     *        *     204.2.229.230
 16    73 ms    74 ms    75 ms  204.2.229.10

Trace complete.

As you can see, there's two spots between me and the lobby server that have dropped packets. One is just outside the data center, which I imagine is slammed with traffic - and granted, trace route packet pings are lowest priority and many nodes will just reject them, but the node "snjsca04" also dropped a packet and it's not anywhere near the data center yet. (San Jose, I think? Sacramento nodes are cool.)

From what we understand, all it takes is one of those heartbeat communications from the local client to the data center lobby failing too many times to generate 2002. That's a lot of potential points of failure.