ipv6.netflix.com and www.ipv6.cisco.com down

Minor on the grand scale of things, but ipv6.netflix.com has been down since Tuesday, 6:25 pm (Central) and www.ipv6.cisco.com since Saturday 10:50 am (Central). Of the roughly 15 IPv6 websites I monitor, ipv6.cogentco.com has had the greatest uptime over the last 31 days (100%), followed by ipv6.google.com. Please direct any comments to outages-discussion. Frank

On 5/1/2011 13:01, Frank Bulk wrote:
Minor on the grand scale of things, but ipv6.netflix.com has been down since Tuesday, 6:25 pm (Central) and www.ipv6.cisco.com since Saturday 10:50 am (Central).
Of the roughly 15 IPv6 websites I monitor, ipv6.cogentco.com has had the greatest uptime over the last 31 days (100%), followed by ipv6.google.com.
Please direct any comments to outages-discussion.
Both are working fine for me (AS11170). ~Seth

On Sun, May 1, 2011 at 1:01 PM, Frank Bulk <frnkblk@iname.com> wrote:
Minor on the grand scale of things, but ipv6.netflix.com has been down since Tuesday, 6:25 pm (Central) and www.ipv6.cisco.com since Saturday 10:50 am (Central).
Both working fine for me from HE (6939). Interestingly it looks like I'm getting to Cisco via a HE tunnel at their end : 7 pfs-1-pt.tunnel.tserv1.fmt.ipv6.he.net (2001:470:1f02:ab::2) 65.005 ms 65.739 ms 64.993 ms 8 2001:420:80:8::1 (2001:420:80:8::1) 66.202 ms 66.192 ms 66.183 ms (2001:420::/32 being Cisco) Of the roughly 15 IPv6 websites I monitor, ipv6.cogentco.com has had the
greatest uptime over the last 31 days (100%), followed by ipv6.google.com.
From where I sit Cogent has a 100% downtime over the past 31 days - but yes, that probably belongs more on -discuss or elsewhere...
Scott.

For those who aren't on outages-discuss, I should close the loop: ipv6.netflix.com: When I first set up NAGIOS checking I didn't create a service check but configured the host to perform the check_http check. I don't have any notifications for warnings on ipv6 hosts, which is what is returned when a redirect loop is present. I discovered the redirection loop on Saturday, April 23, but I don't know how long it was like that. At that time I removed the customized host check (so it does the default ping instead) and added a check_http service check, where it also returns a warning but I get notified. During the outage last week I changed my NAGIOS check_http to do a "-f follow". From the NAGIOS records it appears the issue with ipv6.netflix.com was resolved Friday, April 29 around 3:25 pm Central because that's when NAGIOS notes a change from a redirect loop to a failure. There was a failure on the check_http check because redirection started working, but to a v4-only site (this has always been the case). The NAGIOS check_http service check with "-6 -f follow" properly reports failure when a v6-site redirects to a v4-only site. That's why I didn't detect the recovery on Friday. I've now set up a custom NAGIOS check_http check to avoid this issue for ipv6.netflix.com. www.ipv6.cisco.com: came up at 4:16 pm Central, just 75 minutes after my posting. Perhaps someone from Cisco is lurking on outages.org. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Sunday, May 01, 2011 3:02 PM To: outages@outages.org Subject: [outages] ipv6.netflix.com and www.ipv6.cisco.com down Minor on the grand scale of things, but ipv6.netflix.com has been down since Tuesday, 6:25 pm (Central) and www.ipv6.cisco.com since Saturday 10:50 am (Central). Of the roughly 15 IPv6 websites I monitor, ipv6.cogentco.com has had the greatest uptime over the last 31 days (100%), followed by ipv6.google.com. Please direct any comments to outages-discussion. Frank _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Frank Bulk
-
Scott Howard
-
Seth Mattinen