In order to better ensure that out-of-date IP data is not being used, MaxMind will no longer allow customers to continue to download old GeoIP and GeoLite databases once their subscription expires. This will help us to ensure compliance with digital privacy laws, protecting our business and yours.
This change will come into effect on February 8, 2021. No action is required on the part of customers.
In the past, we have allowed customers to continue to download databases past their subscription date as a courtesy, removing access only when the latest version of the databases they have paid for are 30 days old. Moving forward, customers will not be able to download paid databases once their subscription has expired. By removing access to these databases, we are working to ensure that only the latest versions of our databases, which regularly incorporate critical updates, corrections, and changes based on digital privacy rights, are being used in production.
In December MaxMind released the new GeoLite2 web services, an IP geolocation API available free of charge.
IP geolocation services provide information about the geographic location of an IP address. MaxMind offers such free web services, GeoLite2 City and GeoLite2 Country, which are comparable to, but less accurate than, MaxMind’s paid GeoIP2 Precision City and GeoIP2 Precision Country web services. GeoLite2 is fully compatible with GeoIP2, using the same API and integration method, making it easy to switch between the free and paid services as your needs change. You can compare accuracy of the GeoLite2 and GeoIP2 web services by selecting a country on the GeoIP2 City Accuracy page.
In this blog post, we are going to review how to build a simple web page in PHP that uses GeoLite2 City. We will learn how to easily upgrade to the paid GeoIP2 Precision City web service, for greater accuracy and unlimited queries (GeoLite2 web service users are limited to 1,000 queries per day).
We are happy to announce the release of the GeoLite2 web service, a limited free IP geolocation API. You may use up to 1000 look-ups per day for the GeoLite2 web service.
Since 2002 MaxMind has been trusted by hundreds of thousands of developers to provide IP geolocation data for projects of passion to enterprise-grade applications and everything in between.
We’ll keep this brief: why should you use the GeoLite2 web service?
We have been at this for 18 years and our web service infrastructure serves tens of billions of requests annually with 99.99% uptime.
We know that IP geolocation has its limitations and we strive to be as transparent as possible about our accuracy numbers for both our free and paid solutions.
Our APIs are public and widely adopted which is why you have probably seen MaxMind integrated in some of the platforms you use, and probably why you know about us.
If you need more accurate or other kinds of IP data all you need to do is switch out the URL to call one of our paid web services. We don’t require a subscription or commitment. You can pay as you go and service credits don’t expire.
To sign up for GeoLite2, head over to our GeoLite2 page.
If you’re an existing GeoLite2 database user, you can generate a license key and start using the service immediately. Our GeoIP2 Precision web service client APIs may be used with the GeoLite2 web services.
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.
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.
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.
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.
by TJ Murphy, @teej_m on Twitter
This article was originally published on Towards Data Science on Jan 18, 2019.
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.