Release Notes for GeoIP Web Services

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.
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.

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: 169.55.62.55
  • IPv6 address: 2607:f0d0:3:2d::4
  • hostname: geoip-as-southeast.maxmind.com

  • 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