- May 9, 2017
- Effective May 9, 2017, we are providing a GeoLite2 ASN database in a CSV format suitable for importing into a SQL database as well as a GeoLite2 ASN database in our MaxMind DB binary format. You can download the database here. GeoLite2 databases may also be downloaded and updated with our GeoIP Update program.
- May 8, 2017
- Effective May 7th, 2017, we are updating the ISP and Organization data to replace the Charter Communications and Bright House Networks data points with the data point Spectrum, as these two ISPs have merged and been rebranded as Spectrum.
- March 5, 2017
Effective March 5th, 2017, we’ve updated GeoIP databases and services providing ISP and Organization data. The change is to a number of European and Latin Americans ISPs. We’ve updated the ISP name to use the common trade name instead of the legal name. This will make it easier to recognize the ISP.
Please note that if you use this data point, for example, to flag a visitor if they change ISP, you may need to adjust your implementation in order to avoid false positive flags.
The ISP name changes include the following:
Telefonica Movil De Chile S.A.to
Movistar Movil Chile
- November 8, 2016
Effective November 8th 2016, we’ve updated any GeoIP database or service providing ISP and Organization data to return Comcast Business rather than Comcast Business Communications. We are doing so in order to use the trade name of the ISP and also because it is shorter.
Please note that if you use this data point, for example, to flag a visitor if they change ISP, you may need to adjust your implementation in order to avoid false positive or negative flags.
The following GeoIP databases and services are affected by this change:
- GeoIP2 ISP database
- GeoIP2 Enterprise database (Update will apply to November 15th release)
- GeoIP Legacy ISP and Organization databases
- GeoIP2 Precision and Legacy City Service
- GeoIP2 Precision and Legacy Insights Service
- September 15, 2016
- Starting with the July 31st 2016 build, the GeoIP City databases provide significantly improved accuracy for countries outside the US, especially China, India, and Japan. See more information about GeoIP accuracy on https://www.maxmind.com/en/geoip2-city-database-accuracy
- April 26, 2016
MaxMind will be adding accuracy radius to the GeoLite2 City and GeoIP2 City databases as well as the GeoIP2 Precision City service.
The Accuracy Radius is an indication in kilometers of geolocation accuracy for the latitude and longitude coordinates we return for an IP address. The actual location of the IP address is likely within the area defined by this radius and the latitude and longitude coordinates.
As a reminder, the latitude and longitude coordinates we return for a given IP address are near either the population or geographic center of the most granular location data we return for that IP address (i.e., country, region/state, city, or postal code) and should not be used to identify a particular address or household.
For the binary databases and web service, this field will be available at
/location/accuracy_radius. All official GeoIP2 client APIs already support this field.
For the CSV databases, a new
accuracy_radiuscolumn will be added to the end of the IPv4 and IPv6 blocks files. Please test your integration to ensure compatibility before updating. You may test your integration by downloading the latest copy of the GeoLite2 CSV database, which already has the accuracy_radius column appended.
Target availability dates:
- GeoLite2 City – May 3, 2016
- GeoIP2 City – May 17, 2016
- GeoIP2 Precision City – May 19, 2016
- April 11, 2016
- Effective April 12th, we are changing the latitude and longitude for two locations in our GeoIP and GeoLite databases. For IPs in the United States that we are unable to locate to a particular state or city, we will return 37.751, -97.822. For IPs that resolve to Ashburn, Virginia with zip code 20147, we will return 39.018, -77.539. We would like to remind customers that latitude and longitude values contained in the GeoIP databases are not precise and should not be used to identify a particular address or household.
- February 26, 2016
Effective March 1st, we are updating the GeoIP ISP and Organization databases to return
Verizon Fiosinstead of
Verizon FiOS, due to a change in how Verizon capitalizes Fios. If you reference
Verizon FiOSin code or a custom rule, note that you may need to revise these references to
- August 10, 2015
- We are updating the GeoIP ISP and Organization databases today to return AT&T Internet Services instead of BellSouth.net, due to a merger with AT&T. We are renaming Bouygues Telecom Division Mobile to Bouygues Mobile. There is also a bug fix to return Frontier Communications instead of AT&T Wireless for Frontier customers in Connecticut.
- January 27, 2015
We are working on improving the accuracy in Crimea.
Approximately 60% of website visitors who are from Crimea are currently located by GeoIP as being in Crimea. We plan to increase this to 75% in the next couple of months.
Approximately 95% of the visitors who are located in Crimea by GeoIP are actually in Crimea.
We currently locate Crimea in Ukraine, as we use GeoNames data and they locate Crimea in Ukraine. If GeoNames locates Crimea in Russia in the future, we will follow their change and post an announcement here as well as on https://twitter.com/maxmind
In legacy GeoIP, we return a FIPS region code of 11 or 20. In GeoIP2, we return a iso code of 40 or 43 in the subdivision object.
Due to the nature of geolocation technology and other factors beyond our control, we cannot guarantee any specific future accuracy level. Further, accuracy figures are subject to change as IP networks are reallocated.
- December 16, 2014
As part of our ongoing work to return more data, MaxMind has increased the number of IP addresses that map to a postal code.
An ISP may allocate an IP range over multiple postal codes. In such cases, MaxMind cannot accurately determine the exact postal code associated with an IP address in that range. Previously we only included a postal code if we were confident of the resolution. Now, we include more postal codes, returning a postal code within a 50km radius.
We are doing this as a convenience to our customers who want to use the postal code instead of the city to link to other data.
In addition, we’ve added Poland and Portugal to the list of countries for which we return postal codes. The full list of countries for which we provide postal codes now includes the following:
Argentina, Australia, Austria, Belgium, Brazil, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Finland, France, Germany, Hungary, Iceland, India, Italy, Malaysia, Mexico, Netherlands, New Zealand, Norway, Pakistan, Poland, Portugal, Russia, Slovakia, South Africa, Spain, Sweden, Switzerland, Thailand, United Kingdom, United States.
- November 25, 2014
We have improved the coverage and accuracy for GeoIP City in Japan, South Korea and Venezuela. We expect to make further improvements to the accuracy in South Korea over the next few weeks.
If we are unable to determine the city or region for IP addresses in Argentina, Austria, Bangladesh, Belgium, Bulgaria, Brazil, Canada, Chile, Colombia, Czech Republic, Denmark, Egypt, Spain, Finland, Greece, Hungary, Indonesia, Ireland, Iran, Netherlands, Norway, Peru, Philippines, Poland, Portugal, Russia, Sweden, Thailand, Turkey, Ukraine, we will return a latitude and longitude of the largest city in the country.
- July 18, 2014
MaxMind has released version 2.1 of the GeoIP2 Precision web service. Changes include:
- The Omni endpoint was renamed Insights. The path for this endpoint has changed accordingly.
- The City/ISP/Org endpoint was removed. The City endpoint now returns all of the data previously returned by City/ISP/Org.
- In v2.0,
autonomous_system_number, and all of the
confidencevalues were incorrectly returned as strings. These are now returned as integers.
To upgrade, please use the updated service URIs specified in our developer documentation.
For the version 2.0 endpoints, the City endpoint will now include ISP/Org data. The other output for the 2.0 endpoints was unchanged.
- April 1, 2014
In previous GeoIP2 databases, the
metro_codewas incorrectly represented as a string. This has been corrected and now
metro_codeis internally represented as an
uint16. This should not affect users of the official Java, .NET, Perl, or PHP GeoIP2 APIs. The Python API will now return an integer rather than a string for
metro_code. Users of libmaxminddb or third-party APIs may be affected.
- January 21, 2014