Bad IPv6 connectivity to commercial networks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bad IPv6 connectivity to commercial networks



On Tue, 11 Jul 2006, Iljitsch van Beijnum wrote:
traceroute6 to www.isc.org (2001:4f8:0:2::d) from 2001:510:102:100:20a:95ff:fecd:987a, 30 hops max, 12 byte packets
1 2001:510:102:100:206:d6ff:fe0f:b806 2.201 ms 7.626 ms 1.444 ms
2 2001:410:101:13::1 1.846 ms 1.736 ms 3.85 ms
3 2001:410:101:5::1 24.331 ms 24.983 ms 102.792 ms
4 2001:410:101:30::2 239.214 ms 96.351 ms 96.318 ms
5 2001:320:1b00:1::1 210.57 ms 210.528 ms 210.714 ms
6 2001:320:1a05::10 211.26 ms 220.1 ms 210.472 ms
7 2001:320:1a05::20 211.47 ms 254.317 ms 211.431 ms
8 2001:320:1a09::1 214.655 ms 214.478 ms 214.43 ms
9 2001:320:1a07::2 216.013 ms 216.143 ms 215.784 ms
....

FWIW, I complained about this issue (lack of commercial peering/transit, e.g., NTT or GBLX or their customers) to RISQ and Canarie (v6 upstreams) on Saturday, but have seen no response or improvement.

Routing to Europe or the US through various networks in Japan leaves room to improvement..

(Connectivity to academic networks is excellent, though..)

--
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.