GeoIP2 Release Notes

February 27, 2020

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

February 18, 2020

We’ve released mmdbinspect, in beta, which gives GeoIP2 users an easier way to interface with multiple MMDB files. The mmdbinspect tool is a command-line interface built with Go, which allows a user to look up one or more IPs from one or more MMDB databases and receive the output in a parsable JSON format.

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.

January 6, 2020

Effective January 20, 2020, we will be flagging more Cable/DSL networks used by businesses (i.e. IP networks from ISPs that serve mid-small sized businesses) as Corporate in the GeoIP2 Connection Type database. Previously these types of networks were more often flagged as Cable/DSL.

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 18, 2019

Free GeoLite2 Database Users: Due to upcoming data privacy regulations, we are making significant changes to how you access free GeoLite2 databases starting December 30, 2019. Learn more on our blog.

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.

October 15, 2019

The following output has been added to the GeoIP2 Precision Insights web service, and minFraud Insights and Factors web services:

  • static_ip_score – An indicator of how static or dynamic an IP address is. The value ranges from 0 to 99.99 with higher values meaning a greater static association. For example, many IPs with a user_type of cellular have a score under one. Static Cable/DSL IPs typically have a score above thirty.

    This indicator can be useful for deciding whether an IP address represents the same user over time.

The static_ip_score output is present in the traits object.

October 14, 2019

This is a reminder that we are retiring support for requests using TLS 1.0/1.1, and unencrypted HTTP requests to MaxMind minFraud services on October 16, 2019. After October 16, 2019, these types of requests will always fail with an error. Please update to TLS 1.2+ to avoid service disruption. You may need to upgrade your technology stack to a later version, or make code changes to do so.

Contact us for support or if you have questions.

October 3, 2019

We have made improvements to how we identify cellular IPs for the connection_type field provided in the GeoIP2 Connection Type database, and the user_type field provided in the GeoIP2 Precision Insights web service and minFraud services. Accuracy for cellular identification should now be about 95% accurate globally.