On Tue, 27 Jan 2026, Mike via NANOG wrote:
In fact, geolocation providers should be using geofeed data as tier 1
data since they are self published. Are you saying you know more about
my prefixes than me?
Anyone else having deja vu? I feel like we had this topic (even with
Abdullah @ IPinfo) some months ago.
Having worked at various times for ISPs, CDNs, and VPN providers, I've
been (well, my customers have been) inconvenienced by incorrect IP Geo
sold by IP Geo providers, and I can understand Abdullah/IPinfo's
reluctance to simply "trust the feeds" because it is so much
easier/cheaper for a VPN provider to lie in their geofeed than to actually
build POPs all around the world.
I've also faced the frustration of IP Geo providers with
outdated/incorrect data relating to our IPs with either no clear way for
us to help update their data or a path is provided, but it takes weeks for
that update to get pushed out. The latter seems unnecessary and
unacceptable. The worst are the "set it up and forget it" installations
of IP Geo data that never gets updated. We have a /16 that was bought
years ago. Originally, it was RIPE space. I've dealt with a number of IP
Geo end users with years out of date local copies of some IP Geo
provider's data who have the /16 filtered as they don't want their
networks/websites accessed by non-domestic eyeballs.
For Abdullah, not knowing the layout of a service provider's network, I
don't care how many points around the Internet you can measure RTT from,
you're not going to accurately guess IP Geo from RTT down to the DMA. As
a FTTH ISP, that's the level of accuracy our customers demand, i.e. so
that if they're getting live TV from an over the Internet provider like
Hulu Live, they get the right local channel lineup.
----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
Blue Stream Fiber, Sr. Neteng | therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/[email protected]/message/5247XNPELV7M2DLHNE4FNJQJG7MYTKJP/
