Ah looks like a problem with MacOS’s whois utility when running "whois 142.248.40.0/22”. I just tried on another machine running Linux and the entry returned correctly this time. I see your Geofeed remark and that definitely looks correct and UTF-8 so that all looks good. Thanks for the catch! I use that tool almost daily and this is the first time I’ve seen it not work properly. Sorry for the confusion.
On Oct 23, 2025, at 10:46, Josh Luthman <josh@imaginenetworksllc.com> wrote:
Are you sure?
# whois 142.248.40.1|grep -i cidr CIDR: 142.248.40.0/22 <http://142.248.40.0/22> On Thu, Oct 23, 2025 at 10:31 AM Francis Booth <boothf@caramelfox.net <mailto:boothf@caramelfox.net>> wrote:
On Oct 23, 2025, at 10:13, Josh Luthman via NANOG <nanog@lists.nanog.org <mailto:nanog@lists.nanog.org>> wrote:
You can look at 142.248.40.0/22 <http://142.248.40.0/22> which was just allocated to us by ARIN a couple of weeks ago.
Looking at that range via whois I am not seeing a Geofeed remark as specified in RFC 9632.
If I was a geolocation provider I would 100% ignore an IP range listed in someone else’s feed unless the geofeed URL matches the entry specified in the whois database, in your current case there is none on that IP range.
I’d highly recommend reading https://www.rfc-editor.org/rfc/rfc9632.html if you haven’t already and see if ARIN will fix your whois entry because right now they are returning the most specific entry at 142.0.0.0/8 <http://142.0.0.0/8> rather than 142.248.40.0/22 <http://142.248.40.0/22>.