The Geolocation dataset maps the entire routable IPv4 and IPv6 address space to physical locations. Every range resolves to a country, and most ranges resolve further to a region, city, postal code, latitude and longitude, and time zone.
It is the same data that powers the Ipregistry API, built from authoritative registry data, operator-published geofeeds, network measurements and continuous quality checks, then packaged for offline use in your own infrastructure.
Available formats
| Format | Description | Size |
|---|---|---|
| CSV | Plain text, one range per line. Import into any database or data warehouse. | 4.0 GB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 379 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 1.1 GB |
Latest build: 32,735,379 records. Files are regenerated every day and published with MD5, SHA-1, SHA-256 and SHA-512 checksums so you can verify every download.
What's inside
The CSV file starts with a header line and contains one record per row, with the following fields:
| Column | Description |
|---|---|
city | City associated with the range. |
country_code | ISO 3166-1 alpha-2 country code, e.g. US or DE. |
country_name | English name of the country. |
ip_end | Last IP address of the range, inclusive. |
ip_start | First IP address of the range, IPv4 or IPv6. |
latitude | Approximate latitude of the range location. |
longitude | Approximate longitude of the range location. |
postal | Postal or ZIP code associated with the range. |
region_code | ISO 3166-2 code of the region, e.g. US-CA. |
region_name | English name of the region, state or province. |
time_zone | IANA time zone identifier, e.g. America/Los_Angeles. |
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.
What you can build
- Localize content, currencies and languages without calling an external API on each request
- Enrich analytics events, logs and data warehouses with location at ingestion time
- Apply geo-based access rules and compliance restrictions in latency-sensitive paths
- Batch process historical traffic where per-request API lookups are impractical
Related use cases: Web personalization · 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.