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.
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.
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.
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.
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.
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.
Anonymous IP addresses (sometimes incorrectly generalized as “proxies”) serve to hide a web user’s true IP address and obfuscate their geolocation. There are legitimate reasons, usually related to privacy or security, to use anonymous IPs, but many businesses find that fraudsters and other bad actors also use anonymous IPs in malicious ways that affect the bottom line.
After careful consideration, taking into account customer feedback, we have decided against removing latitude and longitude coordinates from the GeoLite2 databases. We are in the process of reviewing coordinates used in all of our GeoLite2 and GeoIP databases to ensure there is no risk of misuse.
Moving forward, we will still be discontinuing the GeoLite Legacy databases and will continue to support open source through our GeoLite2 databases. Please continue to check our blog, Support Center, websites, and ourTwitter andLinkedIn accounts for additional updates on our review of GeoLite2 database coordinates.
At MaxMind, “open communication” is one of our core values. We’re listening to you and we take your feedback seriously.
Digitally savvy consumers areincreasingly seeking online experiences tailored to their interests; meanwhile, web personalization companies likeGeoFli are increasingly seeking ways to deliver just the right experiences to those consumers, at the right time.
“We wanted to create a service to display website content based on a visitor’s IP address,” said GeoFli co-founder Nick Shontz. “Using MaxMind’s GeoIP2 City database combined with GeoFli’s custom software, we have seen conversion rates double for our customers. It’s great having an industry-leading tool like GeoIP2 City that’s so easy to integrate with our systems and have such great application and scalability,” Shontz added.
Free and open source code has been part of MaxMind’s technical and organizational foundation since our earliest days. As we continue to develop new products to better service our customers with a broader range of diverse and innovative offerings, we occasionally find it necessary to discontinue or phase out some of our products or services.
Accordingly, we have decided to discontinue the GeoLite Legacy databases on January 2, 2019. (Note that we will begin by discontinuing updates to the free GeoLite Legacy databases as of April 1, 2018. For info, see the “Important dates to consider” section.)