Error [2002] the lobby server connection has encountered an error

[MewCat]

Dallas as well, can't connect.

I can also say the problem doesn't seem to be verizon (or their awful openwrt routers).

Here's the test:

1. Try to connect, examine connection, get the following:

Note: minimal packet loss, no issues save mysteriously can't get characters
2. This failed, let's try and log into a different DC, result is success, connecting to the server 199.91.189.74
3. Since this server is known to be good (disregarding any behind the scenes segmentation and access to server resources), let's add the following hostfile entry:

199.91.189.93 199.91.189.74

Note: this routes the first IP to the second
4. Attempt to log in to the original dc with the modification, result failure pointing at formerly succeeding IP


Conclusion:

Since we have an established connection transferring data in both cases with near identical throughput and one of them actually contacts the lobby server, we can make 3 assumptions:

1. That the TCP socket is created and that's it's exchanging data greater than a simple keepalive.
2. That the TCP connection is (or damn well better be) encrypted.
3. That VZ isn't dedicating resources to decrypting and analyzing the traffic of every call that goes through their routers.

Based on that reasoning, we can arrive at a reasonable conclusion:

There's either a downed server or a bad route (poisoned, lost, lb misonfigured etc) in the square DC in Montreal.

Edit: It is also possible that the information being streamed is causing redirection to an unavailable resource, or the resource is simply misconfigured and whichever service is powering this is throwing errors or returning invalid data. Once it hits the DC it's impossible to tell what precisely goes on without being inside of it, but we can in this case eliminate external factors.

More info:

Tracert ->
 12    52 ms     *       56 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] <- Level 3 router to montreal by way of dallas and chicago Dcs
 13    73 ms    73 ms    75 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] <- route to another host in same DC
 14    61 ms    58 ms    59 ms  192.34.76.10 <- internal entrypoint
 15    56 ms    56 ms    55 ms  199.91.189.242 <- internal redirect
 16    55 ms    56 ms    56 ms  199.91.189.93 <- final destination

 12    52 ms     *       56 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] <- Level 3 router to montreal by way of dallas and chicago Dcs
 13    73 ms    73 ms    75 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] <- route to another host in same DC
 14    61 ms    58 ms    59 ms  192.34.76.10 <- internal entrypoint
 15    56 ms    56 ms    55 ms  199.91.189.242 <- internal redirect
 16    55 ms    56 ms    56 ms  199.91.189.74 <- final destination