Higher ping, can confirm ff14 only

TraceRt results

Tracing route to 204.2.229.116 over a maximum of 30 hops

1 3 ms 2 ms 2 ms 10.0.0.1
2 3 ms 6 ms 3 ms dsldevice.attlocal.net [192.168.1.254]
3 7 ms 4 ms 4 ms 104-14-76-1.lightspeed.jcsnms.sbcglobal.net [104.14.76.1]
4 6 ms 10 ms 7 ms 99.24.65.104
5 * * * Request timed out.
6 31 ms 33 ms 36 ms 12.83.102.9
7 27 ms 32 ms 31 ms 12.122.157.6
8 31 ms 32 ms 30 ms gar3.brhal.ip.att.net [12.122.141.189]
9 23 ms 23 ms 25 ms 192.205.36.158
10 24 ms 29 ms 25 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
11 34 ms 31 ms 28 ms ae-8.r24.atlnga05.us.bb.gin.ntt.net [129.250.2.85]
12 46 ms 44 ms 41 ms ae-4.r25.asbnva02.us.bb.gin.ntt.net [129.250.4.165]
13 * 73 ms 72 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
14 74 ms 71 ms 83 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
15 81 ms 83 ms 80 ms ae-5.r01.scrmca02.us.bb.gin.ntt.net [129.250.2.7]
16 81 ms 80 ms 80 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.5.6]
17 83 ms 83 ms 84 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
18 * * * Request timed out.
19 83 ms 82 ms 81 ms 204.2.229.116

Throwing in my traceroute as well. Seems we're getting rerouted to a Los Angeles hop that seems to be the problem.
Usually, it's one in San Jose that is having issues, but today that doesn't seem to be the case.


1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 19 ms 18 ms 19 ms 76-250-152-1.lightspeed.snantx.sbcglobal.net [76.250.152.1]
3 19 ms 18 ms 19 ms 64.148.112.49
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 34 ms 31 ms 31 ms 32.130.25.67
8 27 ms 29 ms 28 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 28 ms 27 ms 27 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 202 ms 201 ms 212 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 245 ms 253 ms 250 ms ae-5.r01.scrmca02.us.bb.gin.ntt.net [129.250.2.7]
12 218 ms 231 ms 233 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.5.6]
13 239 ms 250 ms 246 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 182 ms * * 204.2.229.230
15 196 ms 190 ms 192 ms 204.2.229.116

Guessing theres nothing we can do?