On Thu, Oct 03, 2013 at 09:54:59AM CEST, Ask Bjørn Hansen <[email protected]> said: > You can reference this anecdote next time there's a discussion about why IPv6 > is (still) worse. > > I am testing from a "native" IPv6 connection on a cable provider in Northern > California, tracerouting to a server in Los Angeles, also with native IPv6. > > The route goes > > Cable modem > Comcast (Northern California, Seattle) > Highwinds (ch, ny, lo, am, fr) -- ?! Ping time jimps ~200ms here. > NTT (Frankfurt, Amsterdam, Ashburn, Los Angeles) > Server > > The return route goes > > Server (Los Angeles) > Telia (Los Angeles) > Tata (Los Angeles) > Comcast (Los Angeles, Northern California) > Cable modem > > If this happened with IPv4 all sorts of network engineers would be fixing it. > I'd not be surprised it it's the same in X days.
I've seen an IPv4 traceroute from Denmark to london going london, NY, SF, Tokyo, Hong-Kong, Singapore, London... _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
