Release Notes for GeoIP2 Web Services

June 22, 2020

We’ve updated our Two-Factor Authentication (2FA) implementation to the FIDO2 standard, which supports more web browsers and more types of security keys (e.g. supported biometrics keys). See our Two-Factor Authentication (2FA) User Guide for more information.

June 12, 2020

GeoNames Monthly Diff Report (June 2020)

GeoIP2 and GeoLite2 databases incorporate GeoNames geographical data, which is made available under the Creative Commons Attribution 4.0 License.

Monthly updates to GeoNames data are incorporated into our databases as we refresh them. Above you will find a CSV report of upcoming changes for the month of June as they relate to the following fields:

  • geoname_id
  • country_name
  • country_code
  • city_name
  • subdivision_1_iso_code
  • subdivision_2_iso_code

Note that the values for the ‘old’ and ‘new’ columns for a given field only differ for the field defined in the ‘diff_in’ column.

May 11, 2020

GeoNames Monthly Diff Report (May 2020)

GeoIP2 and GeoLite2 databases incorporate GeoNames geographical data, which is made available under the Creative Commons Attribution 4.0 License.

Monthly updates to GeoNames data are incorporated into our databases as we refresh them. Above you will find a CSV report of upcoming changes for the month of May as they relate to the following fields:

  • geoname_id
  • country_name
  • country_code
  • city_name
  • subdivision_1_iso_code
  • subdivision_2_iso_code

Note that the values for the ‘old’ and ‘new’ columns for a given field only differ for the field defined in the ‘diff_in’ column.

May 5, 2020

Effective May 11, 2020, we will begin resolving IPs that currently return the neighborhood of Astoria (Queens, NY) to the corresponding borough of Queens in the city name field. We will then resolve the remaining Queens neighborhoods to Queens starting May 18, 2020.

For more granular place identification (such as neighborhood), we recommend using the postal code where provided.

April 27, 2020

We updated our GeoIP2 accuracy statistics page to allow filtering by broadband IPs. This builds on top of existing filters that allow you to filter by IPv6 or cellular IPs.

April 15, 2020

GeoIP2 and GeoLite2 databases incorporate GeoNames geographical data, which is made available under the Creative Commons Attribution 4.0 License.

Monthly updates to GeoNames data are incorporated into our databases as we refresh them. Below you will find a CSV report of these changes for the month of April as they relate to the following fields:

  • geoname_id
  • country_name
  • country_code
  • city_name
  • subdivision_1_iso_code
  • subdivision_2_iso_code

Note that the values for the ‘old’ and ‘new’ columns for a given field only differ for the field defined in the ‘diff_in’ column.

GeoNames Monthly Diff Report (April 2020)

*There are several subdivision code changes of note in South Africa due to recent ISO updates. These changes will show up in this month’s GeoIP2 builds.

February 27, 2020

We have added support for web service lookups to the MaxMind Supported Ruby API (RubyGems, GitHub).

February 14, 2020

We’ve released a Privacy Exclusions API. This API allows you to retrieve a list of IP addresses associated with valid “Do Not Sell” or opt-out of sale requests in accordance with the California Consumer Privacy Act (CCPA). You may view this list, along with more information, in your account portal.

January 21, 2020

Effective January 21, 2020, many records for the autonomous_system_organization data field in GeoIP2 databases and web services will change from full ISP names to abbreviated codes, due to changes in a third-party data feed that contributes to building this data. We recommend using the isp and organization data fields as they should be more stable over time and reflect the full ISP brand name.

December 23, 2019

Our web services, including GeoIP2 Precision web services and minFraud services, now return the error code ACCOUNT_ID_REQUIRED instead of USER_ID_REQUIRED when the account ID parameter is missing.

December 19, 2019

Effective December 23, 2019, we will begin resolving more Australian IP addresses to large cities instead of suburbs (e.g. to Sydney instead of Rushcutters Bay).

December 17, 2019

You can now filter by license key when viewing the query usage report [login required] in your account portal.

December 10, 2019

Effective December 16, 2019, we will return 1 as the last digit for all 7 digit postal codes in Japan. The last digit refers to street-level resolution and should not be relied upon for IP geolocation.

November 8, 2019

Effective November 12, 2019, we will return -001 as the last 3 digits for all 7 digit postal codes in Lisbon, Portugal. Our postal code resolution in Portugal is accurate for the first 4 digits and we include the -001 at the end for backwards compatibility for customers to join the data with 7 digit Portuguese postal code databases. We may extend this convention to other large Portuguese cities in the future.

October 16, 2019

We retired support for TLS v1.0/v1.1 and unencrypted HTTP requests to minFraud services today, as part of our commitment to securing and protecting your data. Please ensure you are using TLS v1.2+ to connect to MaxMind services.