> > Lookup their execs on LinkedIN (Ben Dowling) and send them messages > letting them know how much their support sucks. Continue to do that until > you get a resolution. > > I have found that doing this works with companies where i can’t get > resolution elsewhere.
IP geolocation database providers have zero incentive to care about an individual ISP's data being incorrect, UNLESS the companies that are paying them for access to that data complain about it. Yelling at their execs changes nothing ; this is the business model. On Tue, Oct 21, 2025 at 11:11 PM Mike Lyon via NANOG <[email protected]> wrote: > Lookup their execs on LinkedIN (Ben Dowling) and send them messages > letting them know how much their support sucks. Continue to do that until > you get a resolution. > > I have found that doing this works with companies where i can’t get > resolution elsewhere. > > Good luck! > > -Mike > > > On Oct 21, 2025, at 19:42, Mark Blackford via NANOG < > [email protected]> wrote: > > > > Hi Josh, > > > > Thanks for the reply. I should have mentioned that I have been feeding > > them manual corrections and opening support tickets the past few days, > but > > they pride themselves on ignoring ISPs in favor of their own probes and > > ping times. I'm at a total loss at what to do since IPinfo ignores the > > geofeed, ignores all the other providers that are correct, and takes > pride > > in being wrong because they ping the wrong end. > > > > I was hoping another point to point provider has had success in getting > > their data corrected with IPinfo. It's odd to me how IPinfo can be > highly > > recommended by developers on this list, but their data is so far off. I > > can see how their method would work for an enterprise, BNG or cable > > provider, but not at all for an NNI ISP provider. > > > > Thanks again, > > Mark Blackford > > > > > >> On Tue, Oct 21, 2025 at 9:16 PM Josh Luthman < > [email protected]> > >> wrote: > >> > >> 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/G3AA2MLFY4DV4R2HXHJMOLXS25GKTG75/ > _______________________________________________ > NANOG mailing list > > https://lists.nanog.org/archives/list/[email protected]/message/J7EMHH6APHJRDIHY6JI23LIXD6GF4LAN/ _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/DIVNHBFRECK6W6QUVOD3I3TDVCQEM4XC/
