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 <a...@fiberdrop.net> 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 <mich...@wi-fiber.io> > wrote: > >> 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 <alanda...@gmail.com> >> wrote: >> >>> 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 supply them the error code, IP address, and zip code.. we'll see >>> if it's passed to the right folks. >>> >>> On Tue, Nov 12, 2019 at 3:30 PM Michael Crapse <mich...@wi-fiber.io> >>> 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 >>>> who they use? >>>> >>>> Mike >>>> >>>
