connection errors

[Hav3nsblade]

Giving an update early in the morning. Don't know if this is due to near non-existent traffic at this time of day but I managed to get in first try with no hitches at this very moment.

Now you can bet your asses and half a t**** I won't be logging out for the rest of the day

[Ostheim89]

My trace results are actually reaching the destination IP this morning, so I'm tentatively going to assume the problem got fixed, wherever it was.

[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

[Rolanberryy]

Same here I'm able to log in no problem. My connection route is also going through Level3 now.

[mariannef]

Tracing route to 204.2.29.70 over a maximum of 30 hops


4 12 ms 10 ms 27 ms ool-4353f892.dyn.optonline.net [67.83.248.146]
5 13 ms 12 ms 17 ms 64.15.7.71
6 12 ms 15 ms 12 ms 451be0d2.cst.lightpath.net [65.19.120.210]
7 12 ms 41 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
8 12 ms 14 ms 11 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]

9 19 ms 15 ms 12 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.9
6]
10 29 ms 30 ms 29 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.1
66]
11 40 ms 29 ms 32 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.2
7]
12 * * * Request timed out.
13 82 ms 81 ms 88 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.5
7]
14 81 ms 84 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.2
41.2.18]
15 81 ms * * 204.2.29.241
16 92 ms 84 ms 80 ms 204.2.29.70

[NaiaLalita]

Imagine how much stress and frustration and wasted time could have been avoided if a single SE representative had stepped in here to acknowledge it was a bad node along the path to the northeast, and that they were working to redirect.

Don't get me wrong. I'm thrilled it appears fixed.

I just happen to also be super disappointed that the answers most people got from "support" on this issue were "your isp sucks idk" and the folks on SE's end who were actually capable, held their complete silence rather than providing any updates or answers.

DDRDiesel, I'm not kidding when I say we all have YOU, SPECIFICALLY, to thank for this being resolved. Without your know-how, independent investigation, and tenacious reporting with aforementioned knowledge, I doubt the rest of us would have gotten any response, much less this fix!

Edit to add: My own tracert results for this morning
Tracing route to 204.2.29.122 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms [redacted]
2 * * * Request timed out.
3 8 ms 9 ms 8 ms [redacted]
4 15 ms 11 ms 11 ms opti37-8.nassau.cv.net [167.206.37.8]
5 12 ms 11 ms 12 ms 451be0fc.cst.lightpath.net [65.19.99.252]
6 13 ms 11 ms 11 ms 64.15.1.88
7 25 ms 12 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
8 13 ms 12 ms 17 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
9 13 ms 14 ms 14 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
10 35 ms 35 ms 36 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
11 32 ms 32 ms 34 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
12 * 87 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 88 ms 84 ms 84 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
14 85 ms 83 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 83 ms 83 ms 83 ms 204.2.29.122

Trace complete.

[BettyHarlow]

Exactly! It was a simple peek in their forum!! We did all the work for them! Thank you DDRDiesel, fawlgaiy, Strider_xiii, NaiaLalita and so many more for all of their work!!

[fawlgaiy]

Checking in here to say that my ping/tracert to NA was successful and I was able to log in without issue today. I'll try it again later this evening, but based on these replies I have hope this is resolved for real and not just a fluke! Cheers for all your detective work DDRDiesel!