Quote Originally Posted by Janyd View Post
Hmm, this looks promising.

Usually, this would be the starting time for the latency to start showing itself, according to the patterns we've noted but I just ran a traceroute, and here's what I've got (starting at the NTT nodes in Dallas):

8 28 ms 26 ms 26 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * 25 ms * ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 * * * Request timed out.
11 60 ms 84 ms 64 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 63 ms 64 ms 61 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 72 ms 73 ms 76 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 64 ms * 204.2.29.241
15 64 ms 68 ms 68 ms 204.2.29.122


Ran a Ping command as well:

Pinging 204.2.29.122 with 32 bytes of data:
Reply from 204.2.29.122: bytes=32 time=59ms TTL=49
Reply from 204.2.29.122: bytes=32 time=60ms TTL=49
Reply from 204.2.29.122: bytes=32 time=59ms TTL=49
Reply from 204.2.29.122: bytes=32 time=58ms TTL=49

Ping statistics for 204.2.29.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 60ms, Average = 59ms
This does look promising. Been watching pings all morning. 65ms average (and normal behavior for me)

Right around 11:10AM EDT, pings jumped to 110ms (sigh) but so far are hanging around 70ms with a few spikes but a lot different than the last few days where it stayed at 120ms with packet loss.

Traceroutes on two of our problem nodes, 128.241.2.18 and 129.250.7.57, are also responding better than before (70-80ms down from 120ms)

Fwiw, after getting run around with ATT support last night, getting disconnected from their chat, and getting a phone call, they did say "should be fixed by Thursday morning" so lets hope so *fingers crossed*