I'm getting very long routes to Google from gblon02 (>300ms RTT, routeing via the Far East). Of course you might get a different IPv6 address when you look up ipv6.google.com than I do (Google DNS doesn't appear to be IPv6-enabled yet so I think the resolution might depend on where on the IPv4 Internet you are). Right now I'm resolving ipv6.google.com to 2001:4860:a005::68 ping and traceroute to that IPv6 address below are via T15800. This same IPv6 address is 18ms away from me via a Hurricane Electric tunnel to HE's London POP. Thanks, -roy ------------------------------- darla# ping6 2001:4860:a005::68 PING6(56=40+8+8 bytes) 2a01:348:16f::1 --> 2001:4860:a005::68 16 bytes from 2001:4860:a005::68, icmp_seq=0 hlim=57 time=328.683 ms 16 bytes from 2001:4860:a005::68, icmp_seq=1 hlim=57 time=326.995 ms 16 bytes from 2001:4860:a005::68, icmp_seq=2 hlim=57 time=327.009 ms 16 bytes from 2001:4860:a005::68, icmp_seq=3 hlim=57 time=343.009 ms darla# traceroute6 2001:4860:a005::68 traceroute6 to 2001:4860:a005::68 (2001:4860:a005::68) from 2a01:348:16f::1, 64 hops max, 12 byte packets 1 gw-252.lon-02.gb.sixxs.net 10.760 ms 10.860 ms 10.999 ms 2 ae0-1235.rt2.the.uk.goscomb.net 11.973 ms 11.646 ms 11.986 ms 3 2001:728:0:5000::6d 119.984 ms 208.745 ms 18.973 ms 4 ae-1.r22.londen03.uk.bb.gin.ntt.net 11.977 ms 11.581 ms 11.978 ms 5 as-0.r20.nycmny01.us.bb.gin.ntt.net 79.984 ms 83.611 ms 79.977 ms 6 as-2.r21.sttlwa01.us.bb.gin.ntt.net 150.974 ms 154.567 ms 159.976 ms 7 as-2.r21.osakjp01.jp.bb.gin.ntt.net 363.971 ms 282.607 ms 295.939 ms 8 ae-4.r21.tokyjp01.jp.bb.gin.ntt.net 297.969 ms 329.565 ms 295.970 ms 9 p64-2-0-0.r21.newthk01.hk.bb.gin.ntt.net 344.974 ms 364.628 ms 331.902 ms 10 xe-1-1.a04.newthk01.hk.ra.gin.ntt.net 346.972 ms 332.543 ms 485.962 ms 11 * * * 12 * * * 13 * * *