GeoIP Release Notes

August 20, 2019

8-hour interruption of old TLS and unencrypted minFraud requests on August 28, 2019

There will be a planned service interruption for all requests to MaxMind services that use TLS versions 1.0 and 1.1, and for unencrypted HTTP requests to MaxMind legacy minFraud services (e.g. minFraud Standard, minFraud Premium, Proxy Detection web service, IIN service). This will take place for up to 8 hours from 14:00-22:00 UTC on August 28, 2019.

During the interruption, requests using TLS v1.0 and v1.1 and unencrypted HTTP requests to legacy minFraud endpoints will fail with an error.

To avoid service interruption, you may need to upgrade some part of your technology stack to a later version, or you may need to make code changes. If you have any questions, please do not hesitate to contact us. Additional info is available on our blog.

July 24, 2019

There will be a planned service interruption for all requests to MaxMind services that use TLS versions 1.0 and 1.1, and for unencrypted HTTP requests to MaxMind legacy minFraud services (e.g. minFraud Standard, minFraud Premium, Proxy Detection web service, IIN service). This will take place for up to 2 hours starting at 14:00 UTC on the three dates below:

  • Monday, July 29, 2019
  • Wednesday, July 31, 2019
  • Friday, August 2, 2019

During the interruption, requests using TLS v1.0 and v1.1 and unencrypted HTTP requests to legacy minFraud endpoints will fail with an error.

To avoid service interruption, you may need to upgrade some part of your technology stack to a later version, or you may need to make code changes. If you have any questions, please do not hesitate to contact us. Additional info is available on our blog.

July 15, 2019

We are adding postal code data for Singapore and South Korea. Effective July 22nd 2019, we will return the first 2 digits of Singapore postal codes and 5-digit South Korea postal codes where we have reasonable confidence in postal resolution.

July 2, 2019

We’ve updated the direct download URLs for GeoIP databases in your account portal to use security tokens instead of license keys. If you are a new user and wish to use your own script or program to automate GeoIP downloads instead of using our GeoIP Update Program, there are additional steps to take after copying the direct download URL from your account portal.

If you are an existing user that has already set up your own script or program to automate GeoIP downloads, this change should not affect you, unless you add new databases to your script or program. Instructions on additional steps are here.

April 18, 2019

In order to ensure your data is as safe and secure as possible, we will be retiring support for TLS v1.0 and 1.1, unencrypted HTTP requests to our legacy minFraud services, and our legacy minFraud SOAP API in the coming months. Please see our blog for more info.

April 8, 2019

To enhance the security of your MaxMind account, Chrome users can enable two-factor authentication (2FA). You can now add and require a (FIDO U2F) security key on top of your account credentials for a more secure log-in. See our support center user guide for information on how to set up 2FA.

January 24, 2019

We completed our most recent review and update of Geolocation for Crimea. Our accuracy has increased as follows:
Approximately 93% of website visitors who are from Crimea are currently located by GeoIP as being in Crimea. Approximately 99% 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.

January 14, 2019

We’ve released a new major version of GeoIP Update. This release adds support for Windows and has a new code base. You can find it on GitHub. We’ve written an upgrade guide if you’re running an older version.

January 14, 2019

In order to address new legal requirements, including the European Union’s General Data Protection Regulation (GDPR), we will be limiting availability of archived GeoIP databases to 30 days. This change will be effective March 18, 2019 and applies to all GeoIP2, GeoIP, and GeoLite2 databases. You may need to change your processes or applications to download more recent databases once this change occurs.

January 4, 2019

On Monday, January 7, 2019 at approximately 15:00 UTC (10:00am EST), we will be switching to static server IP addresses for traffic to our website and to downloads.maxmind.com (used for GeoIP database downloads). The IP for the hostname used by our web services or geoipupdate tool won’t change immediately, but if you whitelist IPs for any of our services we encourage you to add the new IP addresses to your whitelist. The static IP addresses will be a subset of what we list on https://dev.maxmind.com/maxmind-server-ip-addresses/. We will update the list of IP addresses on that page following the change. Please sign up for the email list on that page if you want a notification when our server IP addresses change.

January 3, 2019

On January 2, 2019, we discontinued our GeoLite Legacy databases. This discontinuation was first announced on January 2, 2018.

GeoLite Legacy databases are no longer available for download. Attempting to download a GeoLite Legacy database file will result in the error: “Database edition not found”.

Free geolocation data is still available through our GeoLite2 databases. See our support center for more information.

September 21, 2018

On Monday, October 1st, we will be changing a large amount of our U.S. coordinate (latitude & longitude) data* to use GeoNames coordinates for postal codes. This change will ensure greater consistency during our build processes. Around 95% of US coordinates will change with most moving about 1 mile. About 5 to 10% of US coordinates will move by more than 10 miles.

* Coordinate data is approximate and is not precise. It should not be used to identify a particular street address or household as it refers to a larger geographical area instead of a precise location.

August 14, 2018

Effective August 21st, we will be mapping IP addresses to Districts (Gu) of Seoul instead of Seoul. This will allow customers to have a more precise mapping, similar to how we map IPs to New York City and London boroughs, and Tokyo’s special wards. We will continue to map some IPs to Seoul if we are unable to determine the specific district the IP is located in. We will also continue to map IPs located in the central Jung District to Seoul, similar to how we map IPs in Manhattan to New York and IPs in Chūō to Tokyo.

July 17, 2018

Effective July 24th, we will be mapping more IP addresses to special wards of Tokyo instead of Tokyo itself. This will allow customers to have a more precise mapping, similar to how we map IPs to New York City and London boroughs. We will continue to map some IPs to Tokyo if we are unable to determine the specific special ward the IP is located in.

July 3, 2018
Effective July 10th, we will update the ISP and Organization data to replace the Time Warner Cable name with the name Spectrum, as these two ISPs have merged and Time Warner Cable has been rebranded as Spectrum.