NANOG Mailing List

The North American Network Operators' Group discusses fundamental Internet infrastructure issues such as routing, IP address allocation, and containing malicious activity.

List Archives

Latest Posts

Re: IPinfo Geolocation Advice Needed devrel.ipinfo--- via NANOG (Oct 23)
Hi Tom,

We use a combination of ping, traceroute, and other network diagnostic measurements from the servers. For each IP
address, we take internet measurements for it across multiple different servers.

— Abdullah | DevRel, IPinfo

Re: IPinfo Geolocation Advice Needed Tom Beecher via NANOG (Oct 23)
It seems from a cursory glance that you guys are using RTT to IPs as your
primary signal for location. Is that accurate?

Re: IPinfo Geolocation Advice Needed devrel.ipinfo--- via NANOG (Oct 23)
Hi Jon,

Thank you for checking us out. It would be incredible if you could give some advice so we can establish a presence in
the ISP community.

I thought we were quite popular because we processed around 2 trillion requests last year. However, I believe I was
tunnel-visioned. So, any advice you can provide on helping us reach out to ISPs, particularly smaller ISPs, would be
greatly appreciated.

In terms of registering your geofeed, it is...

Re: IPinfo Geolocation Advice Needed devrel.ipinfo--- via NANOG (Oct 23)
Hi Josh,

I connected via LinkedIn with you. Currently, for you all your IPs (AS35860 and 142.248.40.0/22), we locate them to
Troy, Ohio.

Please see the results here: https://ipinfo.io/tools/summarize-ips/6fbbb955-0fa2-471f-9e69-66a2be55d915

If there are any issues, please flag them for our support team so they can investigate. They have the right tools.

---

Well, the issue with MLB is that they are not our customers (as far as I know)....

Re: IPinfo Geolocation Advice Needed devrel.ipinfo--- via NANOG (Oct 23)
Hi John,

Thank you for the idea. We have a research program and regularly present at NOG conferences. Ben, our founder, flagged
this to Oliver Gasser, our head of research. We will reach out to ARIN and NANOG soon.

Thank you.

— Abdullah | DevRel, IPinfo

Re: IPinfo Geolocation Advice Needed Mark Blackford via NANOG (Oct 23)
Hi Jon,

Thanks for weighing in.

I asked about using /32 in the beginning of the post, but in the essence of
why location matters, the /32 end in say Dallas is a gateway router and the
/32 end in Charlotte is where the proverbial eyeballs are.
Do we really need to be that granular to the host level for a router
that will not make any CDN requests? A /31 seems close enough for all
intents and purposes. I think following the geofeed RFCs should...

Re: IPinfo Geolocation Advice Needed Jon Lewis via NANOG (Oct 23)
This seems to be a common "error" in formatting. I see I did the same
thing...and am about to update all our records. :(

----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
Blue Stream Fiber, Sr. Neteng | therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

Re: IPinfo Geolocation Advice Needed Job Snijders via NANOG (Oct 23)
If I'm reading RFC 9632 section 3 correctly, that ':' between 'Geofeed'
and 'https://inxfiber..' should not be there.

DO THIS:

Comment: Geofeed https://inxfiber.com/geofeed/

NOT THIS:

Comment: Geofeed: https://inxfiber.com/geofeed/

I have no idea if omitting the colon will make a material difference to
the case at hand, I just wanted to point out this syntax issue.

Kind regards,...

Re: IPinfo Geolocation Advice Needed Josh Luthman via NANOG (Oct 23)
*shrug* works for every other provider, Google, etc...

Re: IPinfo Geolocation Advice Needed Francis Booth via NANOG (Oct 23)
Ah looks like a problem with MacOS’s whois utility when running "whois 142.248.40.0/22”. I just tried on another
machine running Linux and the entry returned correctly this time.

I see your Geofeed remark and that definitely looks correct and UTF-8 so that all looks good.

Thanks for the catch! I use that tool almost daily and this is the first time I’ve seen it not work properly. Sorry for
the confusion.

Re: IPinfo Geolocation Advice Needed Michael Greenup via NANOG (Oct 23)
Hi Ben,

I too would like to see this. Everybody knows IP geolocation is not a trivial task and is rife with inaccuracies. If
such a presentation were made, it would allow us poor operators a valuable insight into the minefield which is
geolocation and might even help some of us avoid some of the more common pitfalls.

Just food for thought...

Regards,

Michael

The views and opinions included in this email belong to the author and are not...

Re: IPinfo Geolocation Advice Needed Michael Greenup via NANOG (Oct 23)
Hi Francis,

I do not believe ARIN has the capability at present to comply with RFC 9632. At least, I'm not seeing where I can set a
geofeed attribute in my portal. Perhaps I am wrong though?

Regards,

Michael

The views and opinions included in this email belong to the author and are not representative of the views and opinions
of the company. If you find a spelling or grammatical error, you may keep it.

Re: IPinfo Geolocation Advice Needed Jon Lewis via NANOG (Oct 23)
NetRange: 142.248.40.0 - 142.248.43.255
CIDR: 142.248.40.0/22
NetName: INXFIBER-02
NetHandle: NET-142-248-40-0-1
Parent: NET142 (NET-142-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Imagine Networks (INL-18)
RegDate: 2025-10-10
Updated: 2025-10-10
Comment: Geofeed: https://inxfiber.com/geofeed/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ref:...

Re: IPinfo Geolocation Advice Needed Josh Luthman via NANOG (Oct 23)
Are you sure?

# whois 142.248.40.1|grep -i cidr
CIDR: 142.248.40.0/22

Re: IPinfo Geolocation Advice Needed Lu Heng via NANOG (Oct 23)
Maybe our approach with MaxMind could be relevant here. We previously had
major trust issues with them due to one problematic customer, so we changed
how we manage our geolocation data.

LARUS leases IPs to many types of customers. Some, like VPN or proxy
providers, may submit false or unclear location data. Others—mainly
regional ISPs and telecoms—serve real end users in fixed locations. To
handle this, we divided our geolocation data into...

More Lists

Dozens of other network security lists are archived at SecLists.Org.