GeoIP Release Notes

We have made changes to how we build and package our MMDB files to be more efficient, which has significantly reduced file sizes. The size of CSV files will not change.

No data has been removed from the databases. You will continue to receive the same amount of data in a smaller package.

This is a non-breaking change.

The following databases will be released today, September 30, 2026 with a smaller file size:

We have made changes to how we build and package our MMDB files to be more efficient, which has significantly reduced file sizes. The size of CSV files will not change.

No data has been removed from the databases. You will continue to receive the same amount of data in a smaller package.

This is a non-breaking change.

The following databases from the GeoIP Anonymous Plus suite will be released today, Thursday, September 24, 2026 with a smaller file size:

Please note that there is no change to the GeoIP Anonymous Plus database MMDB today. The enhancement to that file will be applied in the near future.

Today, on September 11, 2026, between approximately 03:57 and 07:00 UTC, some requests to our minFraud and GeoIP web services saw elevated response times. The impact was greatest between about 04:15 and 04:50 UTC, when affected requests could take several seconds to complete.

This was limited to traffic routed through one network path into our US-East data center. Requests served from other regions and paths were not affected. Affected requests completed with correct responses. We saw elevated latency rather than failures.

Our investigation found packet loss on the network path between our edge network provider’s Ashburn point of presence and our US-East data center. Lost packets were retransmitted, which added delay. Our servers, databases, and application code were healthy throughout, and no change on our side triggered the event.

We are working with our network providers to identify the source of the loss and to prevent a recurrence. We are also improving monitoring of this kind of network degradation.

If you have questions about specific requests, please send the request times to our support team and we will review.

A number of GeoIP customers were unable to download GeoIP databases today, Monday August 31, 2026, between 18:50 UTC and 19:48 UTC.

We have identified the issue and the incident has been resolved.

The GeoIP Anonymous Plus suite now includes the GeoIP Residential Proxy database.

This database provides best-in-class detection of residential proxies, which have become the primary vehicle for circumventing geofencing restrictions and online fraud, as well as dramatically improved detection of VPNs. It helps to considerably expand the number of networks detected, reduces false positives, and provides metadata that can be used to fine tune proxy-aware decisioning and enrich logs.

The GeoIP Residential Proxy database is included with a license for the GeoIP Anonymous Plus suite. If you are interested in requesting access to the new dataset for your evaluation, please reach out to your Customer Success Manager or contact our Enterprise Business team.

We are updating the ISP name for some networks to provide further granularity regarding smaller downstream providers.

As an example, we will observe the change below in the ISP field for some networks:

We expect to release these changes in new database updates and web service requests beginning Tuesday, July 21, 2026.

These changes will be reflected in the following products and services:

• GeoIP Insights web service
• GeoIP City Plus web service
• GeoIP ISP database
• GeoIP Enterprise database

We have added a residential sub-object to the anonymizer object, providing data about residential proxy networks:

The residential object may be present even when none of the other anonymizer fields are populated.

This change will be reflected in the following products and services:

• GeoIP Insights web service
• minFraud Insights
• minFraud Factors

The GeoIP Legacy web service now returns meaningful HTTP status codes for error conditions, so you can act on them in your monitoring or an internal proxy, without parsing the response body:

• 400 Bad Request for a malformed request
• 401 Unauthorized for a missing or invalid license key
• 402 Payment Required when your account is out of queries
• 403 Forbidden when your account does not have permission to use the service
• 5xx for a server error

The response body and its error-code strings are unchanged. The IP_NOT_FOUND case continues to return a 200 OK status to avoid breaking existing integrations.

See the GeoIP Legacy documentation for details.

As of June 24, 2026, a number of networks have an anonymizer_confidence of 50, a new value that sits between our existing values of 30 and 99.

This change will be reflected in the following products and services:

• GeoIP Anonymous Plus database
• GeoIP Insights web service

Effective Monday, June 15, 2026, we will be blanking out the city field more often in the following cities/provinces in Saudi Arabia to reduce false positives when the end users of a network are dispersed all over the country.

This change will result in fewer resolutions in:

• Jeddah (city)
• Riyadh (city)
• Mecca (province)
• Riyadh (province)

We will also be blanking out the city field more often for cell networks in the United Kingdom. First- and second-level subdivisions will be retained.

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

The GeoIP database updates for Friday, May 29, 2026 for the following databases won’t be released as scheduled:

• GeoIP ISP database
• GeoIP Enterprise database

We are monitoring changes in our coverage of VPN providers and networks in our GeoIP Anonymous Plus database. A small reduction in total IP addresses and providers is expected as we fine-tune and remove lower confidence networks from our dataset.

You can expect to see fluctuations in the number of networks flagged with a VPN confidence, last seen date, and confidence score. These changes are ongoing improvements to the accuracy of our feed.

If these changes present challenges, please reach out to your Customer Success Manager.

These changes will be reflected in the following products and services:

• GeoIP Anonymous Plus database
• GeoIP Insights web service

We are skipping today’s release of the GeoIP Anonymous Plus database in order to review a decrease in the number of IPs with a VPN label.

We are not aware of any data quality issues in released GeoIP Anonymous Plus databases.

As of May 4, 2026, a number of networks with a provider_name have a lower anonymizer_confidence of 30.

Previously, all networks with provider_name had an anonymizer_confidence of 99.

This change will be reflected in the following products and services:

• GeoIP Anonymous Plus database
• GeoIP Insights web service

Effective Tuesday, April 7, 2026, we will be making a number of changes to reduce false positives when the end users of a network are dispersed all over the subdivision or country.

This change will result in fewer resolutions.

In Czechia (Czech Republic), we will be blanking out the subdivision, city, and postal fields more often.

In Japan, we will be blanking out the city and postal fields more often for cell networks.

In Mexico City, we will be blanking out the borough in the city field more often for cell networks.

This update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Insights web service
• minFraud Factors web service

The GeoIP Connection Type database is now updated every weekday, Monday through Friday. We recommend automating GeoIP database updates so that you can be sure that you always have the most accurate IP geolocation and IP intelligence data.

You can automate database updates with our GeoIP Update program or other methods. You can also download databases directly through the account portal.

Learn how to automate database updates in this knowledge base article.

As part of our ongoing efforts to improve our geolocation confidence factors, we have reduced the country-level confidence for some hosting networks in circumstances where we are less confident about where the data centers identified are deployed.

This change should not impact the confidence for residential, cellular, and other networks commonly used by end-users.

Starting tomorrow, Tuesday, March 24 2026, we’re deploying updates to our geolocation confidence factors to make them more accurate.

For networks located outside of the United States, we will be adjusting country level confidence to be higher in circumstances where those networks are used exclusively in a single country.

For all networks, we will be improving the accuracy of our subdivision, city, and postal confidence. These will be minor changes. Most significantly, some subdivision confidence values of 99 will be reduced to 95.

The following products and services will be improved:

• GeoIP Insights web service
• GeoIP Enterprise database
• minFraud Insights web services
• minFraud Factors web services

The GeoIP database updates for Monday, March 9, 2026 for the following databases were not released as scheduled:

• GeoIP Country database
• GeoIP City database
• GeoIP ISP database
• GeoIP Enterprise database
• GeoLite Country database
• GeoLite City database

These databases will return to their regular release schedule today (Tuesday), March 10, 2026.

Between Tuesday March 3 and Friday, March 6, 2026 (and possibly longer), we are making daily updates to the user count data to more often return a value of 0 or 1 for residential proxies.

Previously, approximately 50% of residential proxy IPs on single household IPs had a user count value of at least 2, and 50% had a value of 0 or 1. This update will make it easier to flag a high volume of customer profiles on a residential proxy as anomalous in relation to a lower user count value of 0 or 1.

Please see an explanation of user counts below:

Learn more about user counts on our Knowledge Base.

We are removing suffixes (e.g. AB, A/S, Co, Corp, eood, Pte, Pvt, S. de R.L. and others) and the LLC prefix from ISP/org names to match their current naming and branding conventions.

What should I do? If you have rules or lists that require updating, ensure that you match on ISP/org names that no longer have these suffixes or prefix.

You can download the list of ISP/orgs that will be changing.

We expect to release these changes in new database updates and web service requests beginning Tuesday, March 10, 2026.

These changes will be reflected in the following products and services:

• GeoIP Insights web service
• GeoIP City Plus web service
• GeoIP ISP database
• GeoIP Enterprise database

GeoNames monthly diff report (February 2026)

GeoIP and GeoLite 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 these changes as they apply to English place names for the month of February 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.

* * In this month’s update, the country name for The Netherlands has been updated to Netherlands.

* * As previously noted, we have updated our GeoNames monthly diff report delivery method.

You can now download the GeoNames monthly diff report from the Download files section of your account portal (direct link, log in required). The report is available alongside your database downloads and can be downloaded automatically. You can also download the report manually.

For download best practices, including how to automate downloads using a license key, please review our documentation on the Dev Portal.

As a result of this update, we will no longer be posting monthly diff report release notes.

On January 21, 2026, we released data with significant changes to autonomous_system_organization and less significant changes to isp and organization data.

Customers can expect to see in many cases improved, more readable versions of autonomous_system_organization and, in some cases, small changes to isp and organization data.

This change is reflected in the following products and services:

• GeoLite ASN database
• GeoLite City web service
• GeoIP ISP database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Insights web service
• minFraud Factors web service

On Tuesday, January 27, 2026, we will be updating a number of NTT (Nippon Telegraph and Telephone) networks to reflect one of NTT’s consumer-facing brands. For these networks, the ISP name will change from NTT DOCOMO BUSINESS to Open Computer Network.

This change will be reflected in the following products and services:

• GeoIP Enterprise database
• GeoIP ISP database
• GeoIP Insights web service
• GeoIP City Plus web service

GeoNames monthly diff report (January 2026)

GeoIP and GeoLite 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 these changes as they apply to English place names for the month of January 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.

Effective tomorrow, Wednesday, January 7, 2026, we will be blanking out the city and postal fields more often for cell networks in the following countries:

• Argentina
• Australia
• Germany
• France
• Japan
• Poland
• Spain
• Turkey

We will also be blanking out the subdivision, city, and postal fields more often in:

• Finland
• Switzerland

This change is to reduce false positives when the end users of a network are dispersed all over the subdivision or country.

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

Effective tomorrow, Thursday, December 18, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following countries. This change will result in fewer resolutions in:

• Amman, Jordan
• Budapest, Hungary
• Reykjavik, Iceland
• All cities in Austria
• All cities in South Africa
• All cities in Vietnam

We will also be blanking out city and postal fields more often for cell networks in:

• India
• Mexico
• United States

This change is to reduce false positives when the end users of a network are dispersed all over the country.

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

Due to an issue we are currently investigating, the GeoIP database updates for Monday, December 15, 2025 for the following databases won’t be released as scheduled:

• GeoIP City database
• GeoIP Country database
• GeoIP Enterprise database
• GeoLite City database
• GeoLite Country database

The GeoIP Anonymous IP, GeoIP Anonymous Plus, GeoIP IP Risk, GeoIP ISP, and the GeoLite ASN databases will be released today as scheduled.

GeoNames monthly diff report (December 2025)

GeoIP and GeoLite 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 these changes as they apply to English place names for the month of December 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.

Effective Monday, December 1, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following countries. This change will result in fewer resolutions in:

• Belgium
• Israel
• Italy
• The Netherlands
• Portugal
• Sweden
• Ukraine

We will also be blanking out city and postal fields more often for cell networks in:

• Canada
• United States

This change is to reduce false positives when the end users of a network are dispersed all over the country. Many of the networks affected by this change are cell networks, which are often allocated across a wide area spanning one or more subdivisions.

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

We have added the ip_risk_snapshot to the traits object in our GeoIP Insights web service and our minFraud Insights and Factors web services. This field contains the risk associated with the IP address. The value ranges from 0.01 to 99. A higher score indicates a higher risk.

The IP risk snapshot is not a replacement for the minFraud IP risk score (ip_address/risk).

The IP risk snapshot is based on an analysis of historical risk on the IP address, while the minFraud IP risk score is a responsive data field that generates an IP risk score in real time based on the transactions you send and activity from across the minFraud network.

minFraud customers may find the IP risk snapshot output useful to determine whether an IP address is risky based on historical activity versus a current, emerging issue. A lower traits/ip_risk_snapshot score combined with a higher minFraud ip_address/risk score would mean that the IP address is becoming risky in real time based on the traffic on your and other customers’ networks. A high score in both ip_risk_snapshot and minFraud IP risk score would mean that the IP address has been risky for a longer time.

Client APIs have been updated to reflect this change.

We have added an anonymizer object to our web services. This object contains the anonymizer data previously found in the traits object together with new outputs.

Anonymizer data in the traits object is being marked as deprecated. However, for backwards compatibility, anonymizer data in the traits object will continue to be populated and the functionality remains the same. This will not be a breaking change.

We recommend updating your integrations to use the new anonymizer object, which contains data points not found in the traits object:

Client APIs have been updated to reflect this change, which applies to the following web services:

• GeoIP Insights
• minFraud Insights
• minFraud Factors

Effective tomorrow, Wednesday, November 19, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following cities and countries. This change will result in fewer resolutions in:

• Bangkok, Thailand
• Istanbul, Turkey
• All cities in Argentina
• All cities in France
• All cities in Germany
• All cities in Ireland
• All cities in Poland
• All cities in South Korea
• All cities in Switzerland
• All cities in Taiwan
• All cities in the United Kingdom
• All cities in Uruguay

This change is to reduce false positives when the end users of a network are dispersed all over the country.

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

GeoNames monthly diff report (November 2025)

GeoIP and GeoLite 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 these changes as they apply to English place names for the month of November 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.

The GeoIP database updates for Monday, November 10, 2025 for the following databases were not released as scheduled:

• GeoIP Country database
• GeoIP City database
• GeoIP ISP database
• GeoIP Enterprise database
• GeoLite Country database
• GeoLite City database

These databases will return to their regular release schedule today (Tuesday), November 11, 2025.

As previously announced, tomorrow, November 11, 2025, some networks previously labeled Verizon Wireless will have their ISP name updated to Verizon 5G Home to improve coverage and accuracy.

In addition, we will also be shortening the ISP name for Verizon 5g Home Internet to Verizon 5G Home.

This change will be reflected in the following products and services:

• GeoIP ISP database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

Effective Tuesday, November 11, 2025, we will be blanking out the subdivision, city, and postal fields more often in Austria, Denmark, Greece, Ireland, Norway, Spain, and Sweden where the end users are actually dispersed all over the country.

This change will result in fewer resolutions to the following cities:

• Vienna, Austria
• Copenhagen, Denmark
• Athens, Greece
• Dublin, Ireland
• Oslo, Norway
• All cities in Spain
• Stockholm, Sweden

The update will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

Effective tomorrow, Tuesday, November 4, 2025, we will be blanking out the subdivision, city, and postal fields in cases where the subdivision was previously mapped to Tokyo but end users are dispersed throughout Japan.

This change will result in fewer resolutions to the Tokyo subdivision and will be reflected in the following products and services:

• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service

We will soon be distinguishing Verizon 5G Home connections from the broader pool of Verizon networks.

Some networks previously labeled Verizon Wireless will have their ISP name updated to Verizon 5G Home.

This change will go live on Tuesday, November 11, 2025 and will be reflected in the following products and services:

• GeoIP ISP database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service
• minFraud Factors web service
• minFraud Insights web service