I'm starting to think about emailing abuse@ntt.net until they get tired of hearing from me:
Code:
Tracing route to 204.2.229.88 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 2 ms 10.252.10.1
3 17 ms 17 ms 16 ms 154.11.12.203
4 46 ms 46 ms 46 ms sea-b2-link.telia.net [213.248.74.220]
5 56 ms 55 ms 55 ms ntt-ic-327522-sea-b2.c.telia.net [80.239.195.59]
6 56 ms 55 ms 55 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
7 46 ms 46 ms 51 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
8 69 ms 68 ms 68 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
9 * * * Request timed out.
10 * * * Request timed out.
11 63 ms 63 ms 64 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
12 38 ms 37 ms 37 ms 204.2.229.242
13 37 ms 37 ms 37 ms 204.2.229.88
Trace complete.
The hop that is not responding is ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] in Sacramento CA.