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.
The data
Inside the file
One record per row, a commented header line first. This is what ipregistry-geolocation.csv looks like:
# ip_start,ip_end,country_code,country_name,region_code,region_name,city,postal,latitude,longitude,time_zone94.246.10.0,94.246.10.255,NO,Norway,NO-50,Trööndelage,Vang,7600,63.74646,11.29953,Europe/Oslo50.74.104.56,50.74.104.71,US,United States,US-NY,New York,New York,10007,40.71435,-74.00604,America/New_York32.142.103.0,32.142.103.34,US,United States,US-TX,Texas,San Antonio,78205,29.42418,-98.49357,America/Chicago201.182.96.48,201.182.96.63,BR,Brazil,BR-RS,Rio Grande do Sul,Taquara,95600-000,-29.65056,-50.78058,America/Sao_Paulo80.12.86.32,80.12.87.239,FR,France,FR-IDF,Île-de-France,Paris,75004,48.85339,2.34887,Europe/ParisThe 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 |
|---|---|
ip_start | First IP address of the range, IPv4 or IPv6. |
ip_end | Last IP address of the range, inclusive. |
country_code | ISO 3166-1 alpha-2 country code, e.g. US or DE. |
country_name | English name of the country. |
region_code | ISO 3166-2 code of the region, e.g. US-CA. |
region_name | English name of the region, state or province. |
city | City associated with the range. |
postal | Postal or ZIP code associated with the range. |
latitude | Approximate latitude of the range location. |
longitude | Approximate longitude of the range location. |
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.
Downloads
Available formats
| Format | Description | Size |
|---|---|---|
| CSV | Plain text, one range per line. Import into any database or data warehouse. | 3.1 GB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 303 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 638 MB |
Use cases
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.