connection errors

[ShanksFCS]

I logged in first try this morning, no lag issues so far! Hopefully it's resolved now.

[DDRDiesel]

Came here to mention I also was able to log in on the first try. Hopefully more people see this and we get some more results. Pinging the DC IP address of 204.2.29.122 gets results right away, and tracert reaches the destination
------------
Tracert results:
Tracing route to 204.2.29.122 over a maximum of 30 hops

4 12 ms 5 ms 4 ms 65.19.100.4
5 3 ms 3 ms 6 ms 64.15.5.80
6 8 ms 3 ms 4 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
7 5 ms 4 ms 4 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
8 10 ms 19 ms 12 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 27 ms 24 ms 24 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 28 ms 26 ms 30 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 79 ms 72 ms 76 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 77 ms 77 ms 78 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 76 ms 79 ms 78 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 79 ms * 204.2.29.241
15 75 ms 77 ms 74 ms 204.2.29.122

Trace complete.
----------------------------------
The route looks to be changed from using the nodes owned by twelve99 to use nodes from Level3, another internet backbone provider.

Anyone not from the NY area that was having problems, please run a ping and tracert to the IP address 204.2.29.122 and let us know if you get the same results!

[Strider_xiii]

Same in with 0 issues right now