Google brings their search engine to IPv6

[broquea]

This is making the rounds today: http://ipv6.google.com

Hopefully with the success of this move, it might pave the way to seeing GMail, Google Groups and maybe even Google Videos/YouTube made available to IPv6 adopters!

[xxconsult]

This is making the rounds today: http://ipv6.google.com
Hopefully with the success of this move, it might pave the way to seeing GMail, Google Groups and maybe even Google Videos/YouTube made available to IPv6 adopters!

Now it would be nice if HE could set up a peering with Google in Frankfurt (DE-CIX):

>traceroute to ipv6.l.google.com (2001:4860:0:1001::68) from 2001:470:1f0a:216::2, 30 hops max, 16 byte packets

1  heywow.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:216::1)  2.279 ms  2.286 ms  2.219 ms
2  2001:470:0:69::1 (2001:470:0:69::1)  1.878 ms  1.677 ms  1.13 ms
3  10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1)  8.488 ms  9.164 ms  8.27 ms
4  10g-5-3.core1.ash1.ipv6.he.net (2001:470:0:4f::2)  112.828 ms  109.25 ms  104.409 ms
5  pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1)  104.923 ms  104.713 ms  104.563 ms

Right now the IPv6 packets travel to Google's datacenter in Washington.

Just for comparison the trace from the DFN (German research network) to Google with an ipv6 peering in place, reaching Google's datacenter in Ireland via DE-CIX:

Code Select Expand

3  zr-fra1-te0-7-0-5.x-win.dfn.de (2001:638:c:c037::2)  17.286 ms   17.096 ms   17.150 ms
4  * 2001:450:2002:25::1 (2001:450:2002:25::1)  17.511 ms   16.774 ms
5  * 2001:4860:0:1001::68 (2001:4860:0:1001::68)  31.149 ms   31.045 ms


Google peers IPv6 both at DE-CIX and AMS-IX.

BTW: Other destination networks are routed even worse, for example HE->DFN:

Code Select Expand

1  heywow.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:216::1)  2.199 ms  2.159 ms  2.291 ms
2  2001:470:0:69::1 (2001:470:0:69::1)  1.587 ms  1.42 ms  1.954 ms
3  10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1)  10.441 ms  8.172 ms  16.231 ms
4  10g-1-4.core1.lon1.ipv6.he.net (2001:470:0:3f::1)  16.373 ms  16.244 ms  16.425 ms
5  10g-2-3.core1.ny4.ipv6.he.net (2001:470:0:3e::1)  84.897 ms  84.899 ms  84.78 ms
6  10g-3-1.core1.sjc2.ipv6.he.net (2001:470:0:33::1)  171.744 ms  171.868 ms  171.902 ms
7  10g-3-2.core1.pao1.ipv6.he.net (2001:470:0:32::2)  172.001 ms  171.851 ms  172.641 ms
8  100m-0-0.pao.ipv6.ipv6.he.net (2001:470:0:1::2)  172.459 ms  171.85 ms  172.096 ms
9  3ffe:80a::c (3ffe:80a::c)  172.585 ms  172.138 ms  172.175 ms
10  2001:450:2002:25::2 (2001:450:2002:25::2)  331.131 ms  333.545 ms  331.169 ms
11  2001:450:2002:25::2 (2001:450:2002:25::2)  331.211 ms  331.147 ms  331.044 ms
12  xr-bir1-te1-1.x-win.dfn.de (2001:638:c:c037::1)  333.147 ms  332.926 ms  333.088 ms

Source & destination are both located in Frankfurt. Because of a missing peering between HE and DFN at the DE-CIX we see a "short" detour via Palo Alto (California)...

Jens

[broquea]

We're already talking to Google about bringing up additional sessions at different locations.
I've also sent an email to dfn.de about peering so we can work on cleaning that up.