I know that the IETF sometimes is running around in circles, but this is rediculous... bygg2> traceroute www.ietf.org traceroute to optimus.ietf.org (132.151.1.19), 30 hops max, 40 byte packets 1 acc-noc.fh.ietf.innovationslab.net (130.128.20.1) 5.889 ms 5.840 ms 6.284 ms 2 bln-2.bone.ietf.innovationslab.net (130.128.96.2) 4.520 ms 4.495 ms 4.484 ms 3 206.24.232.205 (206.24.232.205) 5.254 ms 5.447 ms 5.138 ms 4 acr2-loopback.Washingtondck.cw.net (206.24.226.62) 6.084 ms 5.688 ms 5.681 ms 5 corerouter2.WashingtonEast.cw.net (204.70.9.134) 6.209 ms 6.712 ms 6.052 ms 6 bordercore1.WashingtonEast.cw.net (166.48.244.1) 10.835 ms 13.506 ms 10.446 ms 7 corerouter2.WashingtonEast.cw.net (204.70.9.134) 11.556 ms 12.225 ms * 8 bordercore1.WashingtonEast.cw.net (166.48.244.1) 15.731 ms 15.578 ms 15.017 ms 9 corerouter2.WashingtonEast.cw.net (204.70.9.134) 15.737 ms 15.492 ms 15.542 ms 10 bordercore1.WashingtonEast.cw.net (166.48.244.1) 20.379 ms 32.391 ms 31.373 ms 11 corerouter2.WashingtonEast.cw.net (204.70.9.134) 30.327 ms 29.101 ms 20.415 ms 12 bordercore1.WashingtonEast.cw.net (166.48.244.1) 25.312 ms 80.096 ms 29.160 ms 13 corerouter2.WashingtonEast.cw.net (204.70.9.134) 25.514 ms * 25.417 ms
