[outages] Netflix IPv6 high packet loss on AWS

Joe O'Meara jomeara at blackfoot.net
Fri May 22 11:42:38 EDT 2015


I can confirm that Level3 has some issues out of Seattle. Vandalized 
copper in California took down one of our PTP links last night.

Blackfoot Tech support
support at blackfoot.net
877-881-1155

On 5/21/2015 8:52 PM, Ca By via Outages wrote:
> Anyone else seeing very high packet loss to www.netflix.com 
> <http://www.netflix.com> on IPv6?
>
> I have seen loss from Level3. Zayo, and NTT looking glass, so it 
> appears to be an AWS IPv6 issues internal to them since many networks 
> see loss.
>
> From Comcast in Seattle
>
> $ ping6 2620:108:700f::36f5:605f
> PING 2620:108:700f::36f5:605f(2620:108:700f::36f5:605f) 56 data bytes
> 64 bytes from 2620:108:700f::36f5:605f: icmp_seq=1 ttl=49 time=35.3 ms
> ^C
> --- 2620:108:700f::36f5:605f ping statistics ---
> 5 packets transmitted, 1 received, 80% packet loss, time 4001ms
> rtt min/avg/max/mdev = 35.336/35.336/35.336/0.000 ms
>
>
>  traceroute6 www.netflix.com <http://www.netflix.com>
> traceroute to www.us-west-2.prodaa.netflix.com 
> <http://www.us-west-2.prodaa.netflix.com> (2620:108:700f::36d6:1cd2) 
> from 2601:8:b281:xxxx, 30 hops max, 24 byte packets
>
>  3 te-0-2-0-14-sur03.seattle.wa.seattle.comcast.net 
> <http://te-0-2-0-14-sur03.seattle.wa.seattle.comcast.net> 
> (2001:558:a2:ac::1)  14.652 ms  13.437 ms  13.378 ms
>  4 be-1-sur02.seattle.wa.seattle.comcast.net 
> <http://be-1-sur02.seattle.wa.seattle.comcast.net> 
> (2001:558:a0:213::1)  13.39 ms  13.161 ms  12.57 ms
>  5 ae-20-0-ar03.burien.wa.seattle.comcast.net 
> <http://ae-20-0-ar03.burien.wa.seattle.comcast.net> 
> (2001:558:a0:217::1)  13.41 ms  13.642 ms  15.927 ms
>  6 ae-1-0-ar03.seattle.wa.seattle.comcast.net 
> <http://ae-1-0-ar03.seattle.wa.seattle.comcast.net> 
> (2001:558:a0:10d::2)  14.888 ms  13.737 ms  13.56 ms
>  7  2001:558:0:f769::1 (2001:558:0:f769::1)  13.972 ms  17.637 ms *
>  8 he-0-6-0-0-cr01.350ecermak.il.ibone.comcast.net 
> <http://he-0-6-0-0-cr01.350ecermak.il.ibone.comcast.net> 
> (2001:558:0:f626::2)  12.81 ms  14.89 ms  12.372 ms
>  9 as16509-3-c.seattle.wa.ibone.comcast.net 
> <http://as16509-3-c.seattle.wa.ibone.comcast.net> (2001:559::8b6) 
>  12.023 ms  11.558 ms  12.807 ms
> 10  * * *
> 11  2620:108:7000::d (2620:108:7000::d)  33.996 ms  34.985 ms  61.817 ms
> 12  2620:108:7000::11 (2620:108:7000::11)  34.026 ms  34.131 ms  35.089 ms
> 13  2620:108:7000::2 (2620:108:7000::2)  37.309 ms  33.341 ms  37.257 ms
> 14  2620:107:4000:4200:8000:0:6440:10d0 
> (2620:107:4000:4200:8000:0:6440:10d0)  33.538 ms  34.596 ms  34.177 ms
> 15  2620:107:4000:4200::6440:22d3 (2620:107:4000:4200::6440:22d3) 
>  36.159 ms  38.305 ms  33.958 ms
> 16  2620:107:4000:4200::6440:2287 (2620:107:4000:4200::6440:2287) 
>  34.267 ms  35.276 ms  34.834 ms
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
>
>
>
>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20150522/a76d1736/attachment.htm>


More information about the Outages mailing list