If your issue is only with IPinfo, you should try to reach out to them. I'll say I've seen that name come up recently and they've had some pretty bad data/poor customer experiences.
On Tue, Oct 21, 2025 at 8:24 PM Mark Blackford via NANOG < [email protected]> wrote: > Greetings, > > Does anyone have any suggestions on how to get IPinfo to properly report > Geolocation for NNI pint to point type circuits? I have a geofeed that > they are ignoring, but I have two prevailing theories. > > One - someone put our entire ARIN aggregate in it last month and now it > overlaps everything in the feed. I read that overlapping prefixes cause > confusion. I took it out of the feed today, but IPinfo is so secretive I > have no idea if they will remove it. > > Two, and the more likely theory based on their boast on how they beat the > competitor by thousands of miles, is they are reporting on the wrong end > based on their ping scans. They ping the hub end of a /31 and disregard > the other end that is usually two to three states away. Therefore , they > are the ones horrible off an their competitors are spot on. > > Should I not be reporting the point to point /31 and only use he customer > /32 end? > > Any other advice in properly identifying the location for Ipinfo would be > awesome. All the other providers seem to properly follow my geofeed, and I > have no issues with them. > > Thank you very much, > Mark Blackford > _______________________________________________ > NANOG mailing list > > https://lists.nanog.org/archives/list/[email protected]/message/5FNHPXSU5CHZYFEDOXBCX6BUGGDJSDQH/ > _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/PPSOHD2WERZLEDHCOTEQB5QPKM2W6QO2/
