ryuu.psg.com:/Users/randy> traceroute wrt-tokyo.rg.net
traceroute to wrt-tokyo.rg.net (210.138.216.50), 64 hops max, 52 byte packets
1 wrt-hawi.lan (192.168.0.1) 1.089 ms 0.838 ms 0.805 ms
2 cpe-72-130-240-1.hawaii.res.rr.com (72.130.240.1) 28.964 ms 27.591 ms 27.825 ms
3 tge7-5.klaohias-cer03.hawaii.rr.com (24.25.231.29) 40.011 ms 25.291 ms 48.273 ms
4 tge8-1.klaohias-cer02.hawaii.rr.com (72.129.46.144) 61.741 ms 62.058 ms 60.293 ms
5 tge0-4-0-2.kmlahi07-ccr01.hawaii.rr.com (72.129.46.128) 63.927 ms 74.082 ms 64.340 ms
6 agg31.tustcaft-ccr01.socal.rr.com (72.129.45.2) 71.929 ms 64.954 ms 64.037 ms
7 107.14.17.134 (107.14.17.134) 60.455 ms 65.103 ms 63.598 ms
8 ae-5-0.cr0.dca20.tbone.rr.com (66.109.6.3) 130.063 ms 133.030 ms 134.285 ms
9 107.14.17.178 (107.14.17.178) 133.206 ms
ae-0-0.cr0.dca10.tbone.rr.com (66.109.6.30) 130.485 ms
107.14.17.178 (107.14.17.178) 132.164 ms
10 ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 185.126 ms
ae1.pr1.dca10.tbone.rr.com (107.14.17.202) 132.416 ms
ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 132.197 ms
11 209.48.38.225 (209.48.38.225) 153.804 ms 149.394 ms 152.942 ms
12 vb2000d2.rar3.washington-dc.us.xo.net (207.88.13.66) 158.140 ms 168.326 ms 168.755 ms
13 te-11-0-0.rar3.sanjose-ca.us.xo.net (207.88.12.69) 156.495 ms 160.694 ms 158.592 ms
14 207.88.14.226.ptr.us.xo.net (207.88.14.226) 158.936 ms 161.480 ms 149.665 ms
15 216.98.100.253 (216.98.100.253) 142.506 ms 141.179 ms 140.945 ms
16 sjc002bf02.iij.net (206.132.169.9) 141.301 ms 143.095 ms
sea001bf00.iij.net (206.132.168.1) 157.606 ms
17 tky009bf01.iij.net (206.132.169.122) 409.387 ms
tky008bf00.iij.net (206.132.169.110) 325.051 ms
tky008bf01.iij.net (206.132.169.174) 248.289 ms
18 tky001bb11.iij.net (58.138.80.42) 259.764 ms
tky001bb10.iij.net (58.138.80.10) 243.385 ms
tky001bb11.iij.net (58.138.80.42) 352.163 ms
19 tky001lip20.iij.net (58.138.100.214) 409.185 ms 406.441 ms
tky001lip20.iij.net (58.138.100.210) 409.536 ms
20 tokyo10-ntteast0.flets.2iij.net (210.149.34.98) 257.222 ms 409.180 ms 314.596 ms
21 tokyo10-f03.flets.2iij.net (210.149.34.158) 299.887 ms 306.765 ms 307.255 ms
22 50.216.138.210.bn.2iij.net (210.138.216.50) 409.697 ms 409.540 ms 409.365 ms
well, i guess it could have gone through europe after dca to get to
their xo peering. i guess the root cause is that roadrunner is poorly
peered. are they not actually twt?
randy