blocks.
>
> John
>
> From: NANOG On Behalf Of Cassidy B. Larson
> Sent: Tuesday, November 12, 2019 3:54 PM
> To: Michael Crapse
> Cc: nanog@nanog.org
> Subject: Re: Disney+ Geolocation issues
>
> We're seeing the same thing. Actually we saw it during pre-signup.
nt:* Tuesday, November 12, 2019 3:54 PM
> *To:* Michael Crapse
> *Cc:* nanog@nanog.org
> *Subject:* Re: Disney+ Geolocation issues
>
>
>
> We're seeing the same thing. Actually we saw it during pre-signup.
> Reached out to Disney+ weeks ago as well, with no response.
Subject: Re: Disney+ Geolocation issues
We're seeing the same thing. Actually we saw it during pre-signup. Reached
out to Disney+ weeks ago as well, with no response. Now it's launched, our
support lines are flooded with people unable to give Disney all their moneys.
We finally g
The word on the street (that Disney pushed) was that "we are seeing higher
than expected demand"
WTF, you are in AWS, don't know how to autoscale?
On Thu, Nov 14, 2019 at 11:06 AM Ethan O'Toole wrote:
> > For Disney, isn't it the same "house" ?
>
> They're trying to control different pricing fo
For Disney, isn't it the same "house" ?
They're trying to control different pricing for different markets. Similar
to how Spotify costs a lot less in Indonesia and the Philippines.
This is where a VPN comes in handy.
- Ethan
It is amazing how much variance there is between different IP GEO data sets, we
recently switched from MaxMind to Neustar, there was a huge difference between
the two….
-John
On Wed, Nov 13, 2019, at 15:49, Matthew Huff wrote:
> It’s not about optimization, it’s about the contract with the content
> providers.
For Disney, isn't it the same "house" ?
That email (cl...@disneystreaming.com) bounced back as undeliverable.
-Aaron
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Michael Crapse
Sent: Tuesday, November 12, 2019 7:27 PM
Cc: NANOG list
Subject: Re: Disney+ Geolocation issues
There has been a continued flurry of
We're seeing the same thing. Actually we saw it during pre-signup.
Reached out to Disney+ weeks ago as well, with no response. Now it's
launched, our support lines are flooded with people unable to give Disney
all their moneys.We finally got through to Disney+ support after 2.5hrs
on hold to
For all those in the current and future thread. We were successful in
reaching to Disney by emailing them with our subnet
netad...@disneystreaming.com
On Wed, 13 Nov 2019 at 08:26, Robert Blayzor wrote:
> On 11/13/19 9:49 AM, Matthew Huff wrote:
> > It’s not about optimization, it’s about the co
On 11/13/19 9:49 AM, Matthew Huff wrote:
> It’s not about optimization, it’s about the contract with the content
> providers. The agreement is to restrict content by geographical regions
> mainly for marketing purposes. They block VPN access to keep people from
> bypassing those restrictions. It
It’s not about optimization, it’s about the contract with the content
providers. The agreement is to restrict content by geographical regions mainly
for marketing purposes. They block VPN access to keep people from bypassing
those restrictions. It’s true of all the streaming providers.
> On Nov
On 11/12/19 5:28 PM, Michael Crapse wrote:
> Myself and a few other ISPs are having our eyeballs complain about
> disney+ saying that they're on a VPN. Does anyone have any idea, or who
> to contact regarding this issue?
> This is most likely improper geolocation databases. Anyone have an idea
> wh
On Tue, Nov 12, 2019 at 9:18 PM Michael Crapse wrote:
> IPv6 is a lot more granular when it comes to geolocation data. It is also
> very very unlikely that the block has been used before, and you never know
> what the previous owner did or what geolocation/VPN blacklists it was added
> to. Let me
Using a TPIA provider here at home in Nova Scotia same issue.
-jim
On Tue., Nov. 12, 2019, 6:29 p.m. Michael Crapse,
wrote:
> Myself and a few other ISPs are having our eyeballs complain about
> disney+ saying that they're on a VPN. Does anyone have any idea, or who to
> contact regarding this
IPv6 is a lot more granular when it comes to geolocation data. It is also
very very unlikely that the block has been used before, and you never know
what the previous owner did or what geolocation/VPN blacklists it was added
to. Let me put it this way, this is a familiar song and dance for us, and
> IPv6 support by disney(using AWS) would obviate this issue.
ok. i give. exactly how? i mean technically.
randy
I sent an email there too, I think that this should be very apparent by
now, but IPv6 support by disney(using AWS) would obviate this issue.
Imagine if a multibillion dollar company can't implement ipv6, what hope do
the smaller ones have? /s
On Tue, 12 Nov 2019 at 20:37, Aden Dragulescu wrote:
Try netad...@disneystreaming.com. Was on their whois.
--
*Aden Dragulescu*
fiberdrop, LLC
a...@fiberdrop.net
On Tue, Nov 12, 2019 at 10:27 PM Michael Crapse wrote:
> There has been a continued flurry of trouble tickets from our eyeballs. I
> did find a contact cl...@disneystreaming.com that i
There has been a continued flurry of trouble tickets from our eyeballs. I
did find a contact cl...@disneystreaming.com that i have reached out to in
hope that they can hear our pleas.
On Tue, 12 Nov 2019 at 16:53, Cassidy B. Larson wrote:
> We're seeing the same thing. Actually we saw it durin
20 matches
Mail list logo
