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,postal2a02:9130:802f:cbff:e800:0:0:0/69,ES,ES-CT,l'Escala,171302409:4089:1e0d:b3c0:0:0:0:0/59,IN,IN-OD,Brahmapur,7610262401:4900:30c8:e3ff:6000:0:0:0/67,IN,IN-UP,Meerut,2500022409:40d2:47:a400:0:0:0:0/55,IN,IN-UP,Agra,2820052409:4050:2ec8:204:c540:0:0:0/75,IN,IN-DL,West Delhi,110041The 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. | 8.5 GB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 713 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 1.2 GB |
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.