Thank you Ben and Abdullah for joining the discussion. I understand the balance IPinfo has to make, but hopefully what I have explained to Abdullah on LinkedIn and your support team about the nature of hub and spoke EVPL/NNI networks, point to point IP assignments in /31 ranges, and automatic geofeeds from IPAM product like Netbox helps clarify how your probes do not paint the whole Geo IP picture. For example from my support case, an IPinfo probe in Charlotte, NC sends data to my customer also Charlotte, but has to traverse Internet providers to first get to my network hub in Dallas, and then make the trip over my EVPL/NNI back to my end user in Charlotte who is the one that needs accurate Geo IP location for content providers. I am sure this ping time should be about twice the expected 25-30ms round trip latency expected. Meanwhile, an IPinfo probe in Dallas pings the other end of the /31 with < 1ms latency, which is just on a gateway on a router with no users, and simply concludes I am lying in the geofeed, the /31 must be in Dallas and not Charlotte. You are only half correct in that one end of /31 is in Dallas, but it's not the end that matters to your clients or mine. The end that matters is in Charlotte who is looking at content provided by your clients to my clients. I have offered to Abdullah that I would be willing to work with your developers in any way to make this operationally sound for all that are involved. Thank you again, Mark Blackford On Wed, Oct 22, 2025 at 6:32 PM ben--- via NANOG <nanog@lists.nanog.org> wrote:
Hey all,
Ben, founder of IPinfo here. We care deeply about the quality and accuracy of our data, so I definitely want to get the issues flagged on this thread fixed.
The best way to submit geolocation feedback to us in general is via https://ipinfo.io/corrections.
By default we perform a lot of verification and filtering to geofeeds, and there's a surprising amount of adversarial data in geofeeds, from providers who are incentivised to pretend their IPs are in locations that they're not (mostly from proxy and vpn providers, and some hosting providers). It sounds like that creating problems for some operators though, and we'll look into how we can balance that.
Happy to jump on a call to discuss our data quality and approach to geolocation with anyone. And feel free to escalate any data quality issues you see directly to me over email too - ben@ipinfo.io
Thanks, Ben _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/CO2TITVY...