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_zone188.120.130.64,188.120.130.116,IL,Israel,IL-Z,Ash Shamālī,Afula,,32.60905,35.28918,Asia/Jerusalem37.206.170.192,37.206.170.203,IT,Italy,IT-25,Lombardia,Milan,20121,45.46418,9.18955,Europe/Rome212.20.248.184,212.20.248.187,GB,United Kingdom,GB-ENG,England,Manchester,M99,53.48102,-2.23746,Europe/London2600:480a:9093:0:0:0:0:0,2600:480a:909f:ffff:ffff:ffff:ffff:ffff,US,United States,US-NY,New York,Yonkers,10701,40.9304,-73.89788,America/New_York102.96.120.232,102.96.120.242,MA,Morocco,MA-06,Casablanca-Settat,Casablanca,29640,33.58825,-7.61139,Africa/Casablanca The 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. | 2.8 GB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 285 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 501 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.