GeoIP2 Release Notes

November 19, 2018

We have added Node.js as a MaxMind Supported GeoIP2 API (NPM, GitHub). It provides an API for the GeoIP2 databases, and will provide an API for the GeoIP2 Precision web services. This API also works with MaxMind’s free GeoLite2 databases.

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.
May 25, 2018
Effective May 29, 2018, we will be adding Åland Islands, Martinique, Mayotte, Guadeloupe, French Guiana, Réunion, and Saint Martin to the list of European Union locations identified by the GeoIP2 Country, GeoIP2 City, and GeoIP2 Enterprise databases and GeoIP2 Precision services responses.
April 18, 2018
We have decided to discontinue the GeoLite Legacy databases on January 2, 2019. As part of that process, updated versions of the GeoLite Legacy databases are now only available to redistribution license customers, although anyone can continue to download the March 2018 GeoLite Legacy builds. Starting January 2, 2019, the last build will be removed from our website. GeoLite Legacy database users will need to switch to the GeoLite2 or commercial GeoIP databases and update their integrations by January 2, 2019.

Correspondingly, we have decided against removing latitude and longitude coordinates from the GeoLite2 databases. We are in the process of reviewing coordinates used in all of our GeoLite2 and GeoIP databases to ensure there is no risk of misuse.
February 13, 2018
We have added additional outputs to the GeoIP2 Country, GeoIP2 City, and GeoIP2 Enterprise databases and to the GeoIP2 Precision Services. The outputs are:

  • EU Country: /country/is_in_european_union – Country of the location of the IP address in an EU member state
  • EU Registered Country: /registered_country/is_in_european_union – Country registered by the ISP or organization is an EU member state

GeoIP2 Country, GeoIP2 City, and GeoIP2 Enterprise CSV databases will have a new column added to the location files named “is_in_european_union”. This will be “1” if the country is in the European Union and “0” otherwise.
November 2, 2017

GeoIP2 Precision Insights now includes anonymizer-type outputs. These outputs are:

  • /traits/is_anonymous – whether the IP address belongs to any sort of anonymous network.
  • /traits/is_anonymous_vpn – whether the IP address belongs to an anonymous VPN system.
  • /traits/is_hosting_provider – whether the IP address belongs to a hosting provider.
  • /traits/is_public_proxy – whether the IP address belongs to a public proxy.
  • /traits/is_tor_exit_node – whether the IP address is a Tor exit node.

Please see our GeoIP2 Precision Web Services documentation for more information.

October 31, 2017
We have discontinued the legacy GeoIP JavaScript services, which used the endpoints and

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.

October 10, 2017
Our Singapore server is now live. GeoIP2 Precision and GeoIP web service customers – if you hardcode any of our IPs in your application or your firewall, please make sure you have added the new server IP addresses to your list:

  • IPv4 address:
  • IPv6 address: 2607:f0d0:3:2d::4
  • hostname:

  • 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

    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 and 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:,,, have been removed.