Top Websites Running IPv6

[Mike Leber]

Dan Wing wrote:
>> -----Original Message-----
>> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
>> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
>> Behalf Of Mike Leber
>> Sent: Tuesday, November 17, 2009 2:18 AM
>> To: ipv6-ops at lists.cluenet.de
>> Subject: Top Websites Running IPv6
>>
>>
>> I updated the report that we run at 
>> http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1 
>> million websites.  We now also check www. and ipv6. for each 
>> domain as 
>> well.  It reveals that quite a few major websites have either 
>> added AAAA 
>> records for their main website or are testing ipv6 at an 
>> ipv6. subdomain.
>>
>> Below is copy of the new section for your entertainment.
> 
> Thanks.
> 
> You might also try connecting to port 80 of those sites.  Afterall,
> if they were on Alexa's top-one million list yesterday they should
> be listening on port 80.

Yep, that is a great idea and we will add an HTTP survey in the near future.

> From the information currently posted at
> http://bgp.he.net/ipv6-progress-report.cgi, I found the following sites didn't
> accept connections to port 80 via their AAAA records:
> 
> die.net                        2607:f820:42::4 (failed)
> netbynet.ru                    2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
> luc.edu                        192:192:168:168:1:1:1:1 (failed)
> pcc.edu                        192:192:168:168:1:1:1:1 (failed)
> bayimg.com                     2a01:298:3:1:1337::13 (failed)
> tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
> proua.com                      2a01:d0::10:1 (failed)
> worldofwatches.com             2002:4087:6747:: (failed)
> essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
> fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
> 2002:84b0:8101::84b0:8101 (failed)
> 
> I noticed that essex.ac.uk was failing for IPv4, too, so they might be having
> a site outage at the moment.  The others, however ...

And now that they have added AAAA records and some sites are reporting 1 
percent of accesses coming in via IPv6 (ripe for example) they have a 
vested interest in fixing it so that their site works correctly.

I suppose this reveals that there is a lack of production web site 
monitoring in IPv6 land, hmmmm opportunity??? ;)

I'm alluding to the SaaS model of pingdom, webmetrics, and panopta.  Not 
"can you configure cacti etc" since I know you can! :)

Mike.