GeoIP2 Release Notes

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:

  • 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

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_radius column 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 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.
November 17, 2015
MaxMind has released libmaxminddb 1.1.2, which includes a number of important security fixes. Among these fixes is improved validation of the database metadata. Unfortunately, MaxMind GeoIP2 and GeoLite2 databases created earlier than January 28, 2014, had an invalid data type for the record_size in the metadata. Previously these databases worked on little endian machines with libmaxminddb but did not work on big endian machines. Due to increased safety checks when reading the file, these databases will no longer work on any platform. If you are using one of these databases, we recommend that you upgrade to the latest GeoLite2 or GeoIP2 database.
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.
July 13, 2015

is_anonymous_proxy and is_satellite_provider are now deprecated in GeoIP2.

Use the GeoIP2 Anonymous IP Database to identify anonymous IPs and refer to the IP Risk Score to assess whether an IP address is high risk.

Due to the increased coverage by mobile carriers, very few satellite providers now serve multiple countries. As a result, the is_satellite_provider output does not provide sufficiently relevant data for us to maintain it.

June 29, 2015

GeoIP2 Precision Insights service now offers average_income and population_density fields within the location response. average_income represents the weighted average income in US dollars per person for the zip code(s) associated with the IP address. population_density represents the weighted population per square kilometer for the zip code(s) associated with the IP address. Note that these fields are returned for IP addresses located in the US only. These new fields are documented in the GeoIP2 Precision Web Services API documentation.

June 11, 2015
We’ve released the GeoIP2 Anonymous IP, ISP, Domain and Connection Type databases in CSV format. All GeoIP2 databases are now available in this format.
May 11, 2015
We’ve enhanced the GeoIP2 Precision City and GeoIP2 Precision Insights services to identify the organization associated with a business IP address in 10% more instances.
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.