for what it’s worth, I have seen an almost complete drop in content sources mis-categorizing us as VPN or with the improper location, since implementing a geofeed (https://datatracker.ietf.org/doc/rfc8805/) for our prefixes. There are a few stragglers, but it has been a success for the most part.
> On Aug 27, 2024, at 8:18 PM, Mehmet <meh...@akcin.net> wrote: > > thank you, these are super useful > > i do not know how hbo/disney choose to block ISPs or classify them as VPN.. > any idea of the logic behind this? > > On Tue, Aug 27, 2024 at 1:55 PM Jason Canady <ja...@unlimitednet.us> wrote: > We've had HBO blocked at same time as Hulu and Digital Element helped: > https://www.digitalelement.com/contact-us/ > On 8/27/24 13:16, Howard, Lee via NANOG wrote: >> My source for geolocation updates is >> https://thebrotherswisp.com/index.php/geo-and-vpn and they say: >> HBO: ctiaengine...@hbo.com >> Lee >> From: NANOG <nanog-bounces+leehoward=hilcostreambank....@nanog.org> On >> Behalf Of Mehmet >> Sent: Tuesday, August 27, 2024 12:00 PM >> To: nanog <nanog@nanog.org> >> Subject: hbo max geolocation issue >> >> You don't often get email from meh...@akcin.net. Learn why this is important >> This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with >> links and attachments. >> hello there >> >> i am dealing with hbo max geolocation issue, is there anyone on the list >> from HBO team who can assist (or point me where i can look for a solution) >> >> thank you
