Netomics

Comprehensive routing analytics platform

ASN Information

All prefixes IPv4 only IPv6 only

Partial match

First Hop

Transit

Prepended

Origin

Geofeed (RFC 8805) lets network operators publish authoritative geolocation data for their IP prefixes in a simple CSV file.

Accurate geolocation — commercial geo-IP databases often mislocate prefixes. A geofeed gives you direct control over what location is reported.
Faster corrections — instead of filing tickets with every geo-IP vendor, publish once and major providers (Google, Cloudflare, MaxMind, etc.) pick it up automatically.
Content delivery — CDNs use geolocation to route traffic; wrong location means suboptimal routing and higher latency for your users.
Regulatory compliance — some content is geo-restricted; incorrect geolocation can block your users or expose you to compliance issues.

Create a CSV file with your prefix geolocation data (one line per prefix):

192.0.2.0/24,US,US-CA,Los Angeles,90001
2001:db8::/32,DE,DE-BE,Berlin,10115

Host the file on a web server over HTTPS (e.g. https://example.com/geo/geofeed.csv).

Add a geofeed: attribute to your inetnum/inet6num RPSL object at your RIR:

remarks:        Geofeed https://example.com/geo/geofeed.csv
geofeed:        https://example.com/geo/geofeed.csv

Once published, geo-IP providers and tools like this one will automatically discover and use your geofeed data.

You can search by different input types:

AS-SET name (e.g. AS-GOOGLE) — exact lookup showing members, child sets, and parent sets.
ASN (e.g. 15169 or AS15169) — find all AS-SETs this ASN is a member of.
IP address (e.g. 8.8.8.8 or 2001:4860::1) — finds the origin ASN via BGP, then shows its AS-SET memberships.

Partial match checkbox enables substring search across all AS-SET names (e.g. searching GOOGLE finds AS-GOOGLE, AS-GOOGLE-CLOUD, etc.).