Tracing route to 204.2.29.122 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 8 ms 22 ms 10.30.96.1
3 14 ms 10 ms 36 ms 100.122.142.84
4 11 ms 8 ms 11 ms 100.122.141.96
5 23 ms 21 ms 20 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 25 ms 21 ms 21 ms dls-b23-link.ip.twelve99.net [62.115.14.38]
7 23 ms 22 ms 21 ms ntt-ic-325660.ip.twelve99-cust.net [62.115.156.249]
8 23 ms 19 ms 21 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
9 64 ms 68 ms 51 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 186 ms 169 ms 170 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 168 ms 164 ms 163 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 168 ms 169 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 165 ms * * 204.2.29.241
14 164 ms 164 ms 166 ms 204.2.29.122

Experiencing the same thing now (this is the first time I've had this problem at all in all of this)