GeoIP Release Notes

November 6, 2017
There was an issue with the GeoIP-133_20171107.tar.gz download resulting in invalid data. We have released an updated, corrected GeoIP-133_20171107.tar.gz file.
October 31, 2017
We have discontinued the legacy GeoIP JavaScript services, which used the endpoints http://js.maxmind.com/js/country.js and http://js.maxmind.com/js/geoip.js.

If you still have not upgraded your integration to use the GeoIP2 JavaScript Client API or are encountering problems with your legacy GeoIP JavaScript services, you can find more information about what to do by clicking here.

September 27, 2017
We completed our most recent review and update of Geolocation for Crimea. Our accuracy has increased as follows:

Approximately 89% of website visitors who are from Crimea are currently located by GeoIP as being in Crimea. Approximately 97% 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.

August 17, 2017
On October 31, 2017, we will discontinue our legacy GeoIP JavaScript services, which use the endpoints http://js.maxmind.com/js/country.js and http://js.maxmind.com/js/geoip.js. Please upgrade your legacy GeoIP integration to use our GeoIP2 JavaScript Client API before that date.

July 24, 2017
We will be mapping additional mobile (cellular) networks to a region (subdivision) rather than city level. This change will only occur where the confidence in the city data is low due to the mobile provider allocating IPs over a wide area.

July 10, 2017
The geographical location for anycast CloudFlare networks: 104.16.0.0/12, 162.159.0.0/16, 190.93.244.0/22, 198.41.192.0/19 have been removed.

June 23, 2017
Our Account Portal has been updated to include the ability for our customers to create and manage multiple license keys.

June 11, 2017
We are removing the geographical location for the anycast CloudFlare network 141.101.112.0/20. Anycast networks can be routed to a number of different locations all around the world, typically based on what is the nearest location. Over the next few weeks, we may remove the geographical location for additional anycast networks, including more CloudFlare networks as well as Google public DNS servers 8.8.8.8 and 8.8.4.4.
May 9, 2017
Our GeoLite2 ASN database is now provided 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
We’ve updated 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

The GeoIP databases and services providing ISP and Organization data have been updated. 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:

  • Proximus Skynet to Skynet Belgium
  • Telefonica Germany to O2 Deutschland
  • Telefonica Movil De Chile S.A. to Movistar Movil Chile
  • Tele Danmark to TDC Danmark
November 8, 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
The GeoIP City databases now 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 11, 2016
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
We are updating the GeoIP ISP and Organization databases to return Verizon Fios instead of Verizon FiOS, due to a change in how Verizon capitalizes Fios. If you reference Verizon FiOS in code or a custom rule, note that you may need to revise these references to Verizon Fios.