I'm on Excalibur. I'm aware there's a NTT node that has been acting up the past few days. Basically if you have Spectrum (though other ISPs seem to get it too) and are based in like KY, OH, WI, and probably other states then it's probably hitting you.
Are y'all as tired of this as I am?
EDIT: I'm based in Central KY and using Spectrum. Seems like the East Coast in general is being hit. This is actually the worst night in the past 3 nights, as I can't even get back in. The previous two nights, it tempted me with a 90k but never hit me with it.
Ping:
Pinging 204.2.29.6 with 32 bytes of data:
Reply from 204.2.29.6: bytes=32 time=165ms TTL=45
Request timed out.
Request timed out.
Request timed out.
Reply from 204.2.29.6: bytes=32 time=171ms TTL=45
Request timed out.
Reply from 204.2.29.6: bytes=32 time=165ms TTL=45
Request timed out.
Reply from 204.2.29.6: bytes=32 time=165ms TTL=45
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 204.2.29.6: bytes=32 time=168ms TTL=45
Reply from 204.2.29.6: bytes=32 time=164ms TTL=45
Reply from 204.2.29.6: bytes=32 time=168ms TTL=45
Request timed out.
Request timed out.
Reply from 204.2.29.6: bytes=32 time=168ms TTL=45
Ping statistics for 204.2.29.6:
Packets: Sent = 20, Received = 8, Lost = 12 (60% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 171ms, Average = 166ms
Trace Route:
15 167 ms * * ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
16 * 166 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
17 * 168 ms 167 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
18 * * 166 ms 204.2.29.241
19 * * * Request timed out.
20 * * * Request timed out.
21 168 ms * 175 ms 204.2.29.6
I'm tired boss.
External link →