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_zone99.226.25.84,99.226.25.86,CA,Canada,CA-ON,Ontario,Brampton,L6X1C4,43.68341,-79.76633,America/Toronto2409:4089:2d83:c600:0:0:0:0,2409:4089:2d83:c6ff:ffff:ffff:ffff:ffff,IN,India,IN-OD,Odisha,Puri,752017,19.79818,85.82499,Asia/Kolkata86.179.248.88,86.179.248.111,GB,United Kingdom,GB-ENG,England,Chester,CH1,53.19044,-2.89195,Europe/London173.163.14.240,173.163.15.15,US,United States,US-PA,Pennsylvania,Leacock Township,17534,40.03763,-76.10499,America/New_York2401:4900:44d6:c8ff:e900:0:0:0,2401:4900:44d6:c8ff:f92f:ffff:ffff:ffff,IN,India,IN-UP,Uttar Pradesh,Sultanpur,227806,26.25785,82.07266,Asia/KolkataThe 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. | |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | |
| MMDB | Binary format for instant lookups with standard MMDB readers. |
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.