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_zone24.39.236.8,24.39.236.11,US,United States,US-NY,New York,Cobleskill,12043,42.67779,-74.48546,America/New_York2400:2200:8f8:6100:0:0:0:0,2400:2200:8f8:61ff:ffff:ffff:ffff:ffff,JP,Japan,JP-12,Chiba,Urayasu,279-0004,35.65876,139.90062,Asia/Tokyo27.254.104.32,27.254.104.63,TH,Thailand,TH-21,Rayong,Rayong,21000,12.6809,101.25801,Asia/Bangkok2a02:1210:6c1c:0:0:0:0:0,2a02:1210:6c1e:ffff:ffff:ffff:ffff:ffff,CH,Switzerland,CH-VD,Vaud,Payerne,1530,46.82202,6.93817,Europe/Zurich94.62.83.38,94.62.83.38,PT,Portugal,PT-15,Setúbal,Almada,2800-000,38.67904,-9.15699,Europe/LisbonThe 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. | 5.0 GB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 445 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 1.6 GB |
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.