It's been mostly broken since December 5 and my notes to my contact at their
NOC go unanswered.
Here's this year's stats:
[mailto:firstname.lastname@example.org] On Behalf Of
Sent: Wednesday, February 29, 2012 8:21 AM
To: Ryan Rawdon
Subject: Re: ipv6.cnn.com serving 0B response
On Wed, Feb 29, 2012 at 01:32:07AM -0500, Ryan Rawdon wrote: > <http://ipv6.cnn.com> http://ipv6.cnn.com
> Currently serving a 0B response to any request it looks like - anyone
> know if they are abandoning ipv6.cnn.com or if this is transient
> brokenness (that they may not be aware of)?
I haven't even been able to connect to port 80 at all since early
December, 2011 from some locations. I figured they had some IPv6
project that fizzled and nobody cares anymore. % traceroute6 -I -q1 ipv6.cnn.com.
12 vl-80.car2.washington1.level3.net (2001:1900:15:7::4) 260.305 ms
13 vl-4040.car1.atlanta2.level3.net (2001:1900:4:1::b1) 27.387 ms
14 vl-51.car1.atlanta1.level3.net (2001:1900:1c:1::5) 27.419 ms
There have been a few companies that this has happened to in the past,
Netflix being one that stands out in my mind. It's unfortunate.