MaxMind DB (or MMDB) files facilitate the storage and retrieval of data in connection with IP addresses and IP address ranges, making queries for such data very fast and easy to perform. While MMDB files are usable on a variety of platforms and in a number of different programming languages, this article will focus on building MMDB files using the Go programming language.Continue reading
Several data changes are coming to the legacy web services outlined below due to the Retirement of GeoIP Legacy Downloadable Databases in May 2022. We will continue to support these web services with data from our more modern GeoIP2 data set.Continue reading
If the databases you use begin with `GeoIP2-` then the following is not applicable to you and can be ignored. This would most likely be true if you started using MaxMind databases after October 2017 and did not request access to the Legacy databases.
We are planning to retire the GeoIP Legacy databases at the end of May 2022. This means that neither updates nor older versions of the Legacy databases will be available after that date. We recommend migrating to our GeoIP2 databases at your earliest convenience.Continue reading
As the situation around the Coronavirus (COVID-19) continues to develop and impact communities around the globe, the whole MaxMind team wishes you and your loved ones safety and health.
We have been relying on our business continuity and contingency plans amidst the uncertainty, and we want to assure you that we are committed to providing service to our valued user community. Our team is distributed across North America and everyone is telecommuting to ensure safety and service. We have also confirmed with our key vendors that they are prepared to fulfill their obligations with regards to our contracts.
Any impacts to MaxMind service will be posted on our status webpage, https://status.maxmind.com/, and our Twitter feed, https://twitter.com/maxmind. If you have any questions or concerns, please do not hesitate to reach out to us at email@example.com.
The MaxMind module for HAProxy Enterprise enables you to perform geolocation lookups from a single point at the edge of your network allowing you to offload this work from your backend servers. This native module integration lets you analyze real-time traffic and assign GeoIP properties to requests as they pass through your HAProxy Enterprise load balancer in order to make decisions on this data. You can package the values up as HTTP request headers before the request is proxied. The integration also allows GeoIP2 databases to be updated quickly and seamlessly without the need for scripts across your application fleet.
HAProxy Enterprise combines HAProxy, the world’s fastest and most widely used, open-source load balancer, with enterprise-class features, services, and premium support. By placing it at the edge of your network, you instantly gain access to improved observability over the load placed upon your servers, whether there is any suspicious client behavior, and how quickly your services are responding to requests.Continue reading
It always starts with an innocent observation. “We get a lot of traffic from Boston,” your boss remarks. You naturally throw out a guess or two and discuss why that might be. Until your boss drops the bomb —
“Can you dig into that?”
Darn it. You walked right into that one.
Now you’re in a predicament. You know Google Analytics has traffic by geographic location, but that’s not gonna cut it. If you want to report on those retention rates, lifetime values, or repeat behaviors by geo, you need something you can query with SQL, something that lives in your data warehouse. But you don’t have anything like that. You know there’s user IP addresses in your log data, you just need to turn them into locations. But Redshift doesn’t have a way to do that.Continue reading
We get a lot of questions here at MaxMind about IPv6, and it’s not hard to imagine why. Accuracy is top of mind for every user of IP geolocation and this topic introduces questions about how effective geolocation can be for certain user segments. In this post, we explain a key reason for IPv6 addresses, how they’re allocated, and provide information about IPv6 geolocation accuracy.Continue reading
Reasons For Changes
MaxMind has always been committed to an individual’s right to privacy on the internet. We welcome the burgeoning privacy regulations, such as GDPR and CCPA, for the benefit they can provide to internet citizens. However, these new legislative measures place restrictions that impact our ability to continue distributing our GeoLite2 databases on a public page under the Creative Commons Attribution-ShareAlike 4.0 International License.
We recognize the impact of these changes on the open source community and we do not take these decisions lightly. We want to communicate these changes with transparency and ensure we are balancing your business needs with the privacy needs of individuals.
The California Consumer Privacy Act (CCPA) mandates that businesses honor valid “Do Not Sell” requests from California residents. In this context, complying with a valid request involves MaxMind removing IP addresses from the GeoLite2 data and communicating to GeoLite2 users that the IP addresses in question should (immediately) not be utilized for uses covered under the CCPA. Serving GeoLite2 database downloads on a public page simply does not allow us to communicate and honor valid “Do Not Sell” requests we receive from individuals.
The solution we have chosen is to introduce a new end-user license agreement containing the relevant data processing provisions that both we, as the business providing data, and you, as the third party user of the data, need to comply with applicable data privacy regulations. Additionally, by requiring a MaxMind account and contact information from you, we will be able to communicate all valid “Do Not Sell” requests to you as we receive them.
With this approach, we can continue to offer GeoLite2 databases, without charge, while remaining responsible stewards of data that improves the experience of countless users across the internet.Continue reading
October 16, 2019:
We retired support for TLS v1.0/v1.1 and unencrypted HTTP requests to minFraud services on October 16, 2019, as part of our commitment to securing and protecting your data. Please ensure you are using TLS v1.2+ to connect to MaxMind services.
May 8, 2020:
We retired the legacy minFraud SOAP API on May, 2020. Please integrate with the legacy minFraud service directly, or use our newer minFraud services.
In the coming months, we will be retiring the following:
- TLS v1.0 and 1.1 support across MaxMind products and services (October 16, 2019);
- Unencrypted HTTP requests to our legacy minFraud services (October 16, 2019); and
- The legacy minFraud service SOAP API (January 31, 2020 – revised to May 8, 2020).
Read on below for more information. MaxMind is deeply committed to information security and protecting customer data, and taking these steps will allow us to ensure your data is as safe and secure as possible. If you have any questions, please do not hesitate to contact us.
MaxMind and Dosh will be presenting at the Merchant Risk Council’s annual fraud prevention conference, MRC Vegas, on Tuesday, March 19, from 4:15pm – 5pm. Read on below for the details and what you’ll take away from the session.Continue reading