I found https://geolocatemuch.com/ to be a great resource in setting up our geofeed. Very easy to publish the feed through your whois info for providers that support RFC9092 as well. Otherwise you can reach out to the providers directly and ask them to pull your feed.

On Tue, Aug 27, 2024 at 10:05 PM Josh Luthman <josh@imaginenetworksllc.com> wrote:

How are you publicizing your rfc8805?  I only found two organizations that pull our feed.

On Tue, Aug 27, 2024 at 9:36 PM Tim Burke <tim@mid.net> wrote:

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 <mehmet@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 <jason@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: CTIAEngineers@hbo.com
>>  Lee
>>   From: NANOG <nanog-bounces+leehoward=hilcostreambank.com@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 mehmet@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