Ben, Specifically to us, we found that some IPs come up as Troy, MI when we are in Troy, OH. I recognize the one in Ohio is a tiny town, but we still exist in this state! It was a short while ago a customer couldn't access some baseball thing (MLB?) because their service (our ticket did not specify how they were getting it - the customer just said it didn't work because of a location issue) said they were in the wrong state. We have a geofeed if you do a whois on the ip/block, I don't know if you're honoring it or not. To be frank, there's no way us or most any ISP is going to go through every single IP with a webform. Just look at the geofeed. For one customer or even many I would be unlikely to spend hours of my time fixing your service. You can look at 142.248.40.0/22 which was just allocated to us by ARIN a couple of weeks ago. You won't see much or any traffic in recent weeks. This is on our geofeed, however. On Wed, Oct 22, 2025 at 7: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...