connection errors

[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.