The Geofeed dataset is the Ipregistry geolocation database published in the geofeed format standardized by RFC 8805. Each line maps a CIDR prefix to its country, region, city and postal code, instead of the ip_start and ip_end ranges used by the Geolocation dataset.
Because it follows the geofeed standard, the file plugs directly into any tool or pipeline that already understands geofeeds: no conversion step, no custom parser, just the same data that powers the Ipregistry API in the format the ecosystem expects.
The data
Inside the file
One record per row, a commented header line first. This is what ipregistry-geofeed.csv looks like:
# subnet,country_code,region_code,city,postal191.62.90.123/32,BR,BR-SP,Igaratá,12350-0002409:40e0:40:d500:0:6000:0:0/83,IN,IN-MH,Mumbai City District,4001042001:268:9475:35ff:ffff:fffd:3f3c:0/110,JP,JP-11,Ageo,362-00242a02:a471:30ad:fff0:0:0:0:0/61,NL,NL-ZH,Gouda,28012804:18:173:a400:6f5e:4000:0:0/82,BR,BR-RS,Viamão,94800-000The rows above come from the free sample. Every build ships with MD5, SHA-1, SHA-256 and SHA-512 checksums so you can verify downloads.
| Column | Description |
|---|---|
subnet | IP prefix the entry applies to, in CIDR notation. |
country_code | ISO 3166-1 alpha-2 country code of the prefix. |
region_code | ISO 3166-2 code of the region. |
city | City associated with the prefix. |
postal | Postal code associated with the prefix. |
The MMDB variant carries the same data in a memory-mapped binary tree, compatible with the standard MMDB reader libraries available for every major programming language.
Downloads
Available formats
| Format | Description | Size |
|---|---|---|
| CSV | Plain text, one range per line. Import into any database or data warehouse. | |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | |
| MMDB | Binary format for instant lookups with standard MMDB readers. |
Use cases
What you can build
- Feed geofeed-aware tools and pipelines without writing a converter
- Work with CIDR prefixes when your tooling expects subnets rather than ranges
- Cross-check other geolocation sources against Ipregistry data in a standard format
- Distribute consistent location data to internal systems that ingest RFC 8805 files
Related use case: Compliance
Datasets are available with an Ipregistry subscription and download from your dashboard, or over a stable URL for automated syncs. Prefer live data? The same intelligence is served by the Ipregistry API.