<div dir="ltr">Confirmed from my POV in Texas, as well as v6 servers in NY, FL, and IL.<div><br></div><div>As a consumer, I've had to straight up disable IPv6 when I want to watch Netflix.</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 6:17 PM, Frank Bulk <span dir="ltr"><<a href="mailto:frnkblk@iname.com" target="_blank">frnkblk@iname.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The issue started happening today again. It sounds like Netflix is having<br>
some challenges with advertising AAAA's that are operating. When<br>
www.netflix response I get three AAAA's that on AWS East. When it's not<br>
working, I get eight AAAA's that are on AWS West.<br>
<br>
Here's the three AAAA's when it's good and the eight AAAA's when it's not<br>
good.<br>
<br>
<br>
nagios:/tmp# ./netflix.sh<br>
<br>
; <<>> DiG 9.7.3 <<>> AAAA <a href="http://www.netflix.com" target="_blank">www.netflix.com</a><br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26<br>
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 8, ADDITIONAL: 8<br>
<br>
;; QUESTION SECTION:<br>
;<a href="http://www.netflix.com" target="_blank">www.netflix.com</a>. IN AAAA<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://www.netflix.com" target="_blank">www.netflix.com</a>. 290 IN CNAME<br>
<a href="http://dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>.<br>
<a href="http://dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 50<br>
IN AAAA 2406:da00:ff00::b849:f83b<br>
<a href="http://dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 50<br>
IN AAAA 2406:da00:ff00::b849:fcb3<br>
<a href="http://dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 50<br>
IN AAAA 2406:da00:ff00::6b16:ebed<br>
<br>
;; AUTHORITY SECTION:<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-947.amazonaws.com" target="_blank">ns-947.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-927.amazonaws.com" target="_blank">ns-927.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-941.amazonaws.com" target="_blank">ns-941.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-925.amazonaws.com" target="_blank">ns-925.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-935.amazonaws.com" target="_blank">ns-935.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-934.amazonaws.com" target="_blank">ns-934.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-944.amazonaws.com" target="_blank">ns-944.amazonaws.com</a>.<br>
<a href="http://wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com" target="_blank">wwwservice--frontend-san-756424683.us-east-1.elb.amazonaws.com</a>. 1490 IN NS<br>
<a href="http://ns-916.amazonaws.com" target="_blank">ns-916.amazonaws.com</a>.<br>
<br>
;; ADDITIONAL SECTION:<br>
<a href="http://ns-916.amazonaws.com" target="_blank">ns-916.amazonaws.com</a>. 350 IN A 207.171.178.7<br>
<a href="http://ns-925.amazonaws.com" target="_blank">ns-925.amazonaws.com</a>. 590 IN A 72.21.208.213<br>
<a href="http://ns-927.amazonaws.com" target="_blank">ns-927.amazonaws.com</a>. 590 IN A 72.21.204.209<br>
<a href="http://ns-934.amazonaws.com" target="_blank">ns-934.amazonaws.com</a>. 590 IN A <a href="tel:87.238.84.215" value="+18723884215">87.238.84.215</a><br>
<a href="http://ns-935.amazonaws.com" target="_blank">ns-935.amazonaws.com</a>. 590 IN A <a href="tel:87.238.80.213" value="+18723880213">87.238.80.213</a><br>
<a href="http://ns-941.amazonaws.com" target="_blank">ns-941.amazonaws.com</a>. 7532 IN A <a href="tel:204.246.160.5" value="+12042461605">204.246.160.5</a><br>
<a href="http://ns-944.amazonaws.com" target="_blank">ns-944.amazonaws.com</a>. 1772 IN A <a href="tel:205.251.228.6" value="+12052512286">205.251.228.6</a><br>
<a href="http://ns-947.amazonaws.com" target="_blank">ns-947.amazonaws.com</a>. 590 IN A 204.246.162.10<br>
<br>
;; Query time: 0 msec<br>
;; SERVER: 127.0.0.1#53(127.0.0.1)<br>
;; WHEN: Tue Oct 1 17:58:05 2013<br>
;; MSG SIZE rcvd: 496<br>
<br>
PING 2406:da00:ff00::6b16:ebed(2406:da00:ff00::6b16:ebed) 56 data bytes<br>
64 bytes from 2406:da00:ff00::6b16:ebed: icmp_seq=1 ttl=48 time=57.7 ms<br>
64 bytes from 2406:da00:ff00::6b16:ebed: icmp_seq=2 ttl=48 time=58.9 ms<br>
64 bytes from 2406:da00:ff00::6b16:ebed: icmp_seq=3 ttl=48 time=57.8 ms<br>
<br>
--- 2406:da00:ff00::6b16:ebed ping statistics ---<br>
3 packets transmitted, 3 received, 0% packet loss, time 2004ms<br>
rtt min/avg/max/mdev = 57.709/58.149/58.938/0.624 ms<br>
PING 2406:da00:ff00::b849:f83b(2406:da00:ff00::b849:f83b) 56 data bytes<br>
64 bytes from 2406:da00:ff00::b849:f83b: icmp_seq=1 ttl=49 time=58.6 ms<br>
64 bytes from 2406:da00:ff00::b849:f83b: icmp_seq=2 ttl=49 time=58.4 ms<br>
64 bytes from 2406:da00:ff00::b849:f83b: icmp_seq=3 ttl=49 time=58.4 ms<br>
<br>
--- 2406:da00:ff00::b849:f83b ping statistics ---<br>
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br>
rtt min/avg/max/mdev = 58.468/58.537/58.646/0.212 ms<br>
PING 2406:da00:ff00::b849:fcb3(2406:da00:ff00::b849:fcb3) 56 data bytes<br>
64 bytes from 2406:da00:ff00::b849:fcb3: icmp_seq=1 ttl=49 time=74.8 ms<br>
64 bytes from 2406:da00:ff00::b849:fcb3: icmp_seq=2 ttl=49 time=58.7 ms<br>
64 bytes from 2406:da00:ff00::b849:fcb3: icmp_seq=3 ttl=49 time=65.3 ms<br>
<br>
--- 2406:da00:ff00::b849:fcb3 ping statistics ---<br>
3 packets transmitted, 3 received, 0% packet loss, time 2003ms<br>
rtt min/avg/max/mdev = 58.732/66.318/74.827/6.606 ms<br>
nagios:/tmp# ./netflix.sh<br>
<br>
====================================================<br>
<br>
; <<>> DiG 9.7.3 <<>> AAAA <a href="http://www.netflix.com" target="_blank">www.netflix.com</a><br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38593<br>
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 8, ADDITIONAL: 0<br>
<br>
;; QUESTION SECTION:<br>
;<a href="http://www.netflix.com" target="_blank">www.netflix.com</a>. IN AAAA<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://www.netflix.com" target="_blank">www.netflix.com</a>. 124 IN CNAME<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>.<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::3270:5c77<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::3270:5c7b<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36d6:752<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36d6:20b0<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36d6:22b2<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36d6:24e1<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36f4:7696<br>
<a href="http://dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com" target="_blank">dualstack.wwwservice--frontend-san-608070354.us-west-2.elb.amazonaws.com</a>. 4<br>
IN AAAA 2620:108:700f::36f4:e97a<br>
<br>
;; AUTHORITY SECTION:<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-925.amazonaws.com" target="_blank">ns-925.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-947.amazonaws.com" target="_blank">ns-947.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-916.amazonaws.com" target="_blank">ns-916.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-934.amazonaws.com" target="_blank">ns-934.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-941.amazonaws.com" target="_blank">ns-941.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-935.amazonaws.com" target="_blank">ns-935.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-944.amazonaws.com" target="_blank">ns-944.amazonaws.com</a>.<br>
<a href="http://us-west-2.elb.amazonaws.com" target="_blank">us-west-2.elb.amazonaws.com</a>. 124 IN NS <a href="http://ns-927.amazonaws.com" target="_blank">ns-927.amazonaws.com</a>.<br>
<br>
;; Query time: 0 msec<br>
;; SERVER: 127.0.0.1#53(127.0.0.1)<br>
;; WHEN: Tue Oct 1 18:10:51 2013<br>
;; MSG SIZE rcvd: 508<br>
<br>
PING 2620:108:700f::36f4:e97a(2620:108:700f::36f4:e97a) 56 data bytes<br>
<br>
--- 2620:108:700f::36f4:e97a ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2000ms<br>
<br>
PING 2620:108:700f::3270:5c77(2620:108:700f::3270:5c77) 56 data bytes<br>
<br>
--- 2620:108:700f::3270:5c77 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2008ms<br>
<br>
PING 2620:108:700f::3270:5c7b(2620:108:700f::3270:5c7b) 56 data bytes<br>
<br>
--- 2620:108:700f::3270:5c7b ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 1999ms<br>
<br>
PING 2620:108:700f::36d6:752(2620:108:700f::36d6:752) 56 data bytes<br>
<br>
--- 2620:108:700f::36d6:752 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2016ms<br>
<br>
PING 2620:108:700f::36d6:20b0(2620:108:700f::36d6:20b0) 56 data bytes<br>
<br>
--- 2620:108:700f::36d6:20b0 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2014ms<br>
<br>
PING 2620:108:700f::36d6:22b2(2620:108:700f::36d6:22b2) 56 data bytes<br>
<br>
--- 2620:108:700f::36d6:22b2 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2013ms<br>
<br>
PING 2620:108:700f::36d6:24e1(2620:108:700f::36d6:24e1) 56 data bytes<br>
<br>
--- 2620:108:700f::36d6:24e1 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2009ms<br>
<br>
PING 2620:108:700f::36f4:7696(2620:108:700f::36f4:7696) 56 data bytes<br>
<br>
--- 2620:108:700f::36f4:7696 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2013ms<br>
<br>
nagios:/tmp#<br>
<div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: Outages [mailto:<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>] On Behalf Of Frank Bulk<br>
Sent: Monday, September 30, 2013 12:26 PM<br>
To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
Subject: [outages] Netflix over IPv6<br>
<br>
Friday evening, Sunday morning, and Sunday evening, our monitoring system<br>
has seen sporadic HTTPv6 access issues to <a href="http://www.netflix.com" target="_blank">www.netflix.com</a>. Starting since<br>
10:36 am Central this morning, I've seen sporadic ICMPv6 failures to<br>
<a href="http://www.netflix.com" target="_blank">www.netflix.com</a>.<br>
<br>
Now <a href="http://www.netflix.com" target="_blank">www.netflix.com</a> has many AAAA records that are likely different around<br>
the world and I don't have our monitoring system set up to individually<br>
monitor each AAAA record, but wondering if anyone else has seen the same<br>
thing?<br>
<br>
Regards,<br>
<br>
Frank<br>
<br>
================<br>
Current AAAA's, currently pingable:<br>
<br>
2406:da00:ff00::b849:f83b<br>
2406:da00:ff00::b849:fcb3<br>
2406:da00:ff00::6b16:ebed<br>
<br>
=================<br>
Former AAAA's during non-working state:<br>
<br>
2620:108:700f::36f4:7696<br>
2620:108:700f::36f4:dd14<br>
2620:108:700f::36f4:e97a<br>
2620:108:700f::3270:5c77<br>
2620:108:700f::3270:5c7b<br>
2620:108:700f::36d6:752<br>
2620:108:700f::36d6:b87<br>
2620:108:700f::36d6:22b2<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</div></div></blockquote></div><br></div>