Netflix VPN detection - actual engineer needed

Sat Jun 4 00:07:45 UTC 2016

I don't remember the source, but I do remember that even with Comcast's
deployment, HE still represented the majority of IPv6 traffic in the US.

Of course, it could just be a bunch of us heavy IPv6 users.

On Fri, Jun 3, 2016 at 8:03 PM Spencer Ryan <sryan at arbor.net> wrote:

> Comcast is near 100% on their DOCSIS network (Busniess and residential).
> That should be the largest single ISP for IPv6 for end users in the USA.
>
>
> *Spencer Ryan* | Senior Systems Administrator | sryan at arbor.net
> *Arbor Networks*
> +1.734.794.5033 (d) | +1.734.846.2053 (m)
> www.arbornetworks.com
>
> On Fri, Jun 3, 2016 at 7:49 PM, Cryptographrix <cryptographrix at gmail.com>
> wrote:
>
>> Depends - how many US users have native IPv6 through their ISPs?
>>
>> If I remember correctly (I can't find the source at the moment), HE.net
>> represents something like 70% of IPv6 traffic in the US.
>>
>> And yeah, not doing that - actually in the middle of an IPv6 project at
>> work at the moment that's a bit important to me.
>>
>>
>>
>>
>> On Fri, Jun 3, 2016 at 7:45 PM Baldur Norddahl <baldur.norddahl at gmail.com
>> >
>> wrote:
>>
>> > Den 4. jun. 2016 01.26 skrev "Cryptographrix" <cryptographrix at gmail.com
>> >:
>> > >
>> > > The information I'm getting from Netflix support now is explicitly
>> > telling
>> > > me to turn off IPv6 - someone might want to stop them before they
>> > > completely kill US IPv6 adoption.
>> >
>> > Not allowing he.net tunnels is not killing ipv6. You just need need
>> native
>> > ipv6.
>> >
>> > On the other hand it would be nice if Netflix would try the other
>> protocol
>> > before blocking.
>> >
>>
>
>