The GeoIP web services are fast and reliable, with around 99.9% uptime since 2014. In the table below, you can see more precise uptime measurements per service, and internal latency for the services at the 50th, 90th, 99th, and 99.9th percentile:
| GeoIP web service | Uptime | Internal Latency by Percentile | |||
|---|---|---|---|---|---|
| 50% | 90% | 99% | 99.9% | ||
| GeoIP Insights web service | 99.99% since 2014 | 1 ms | 1 ms | 2 ms | 7 ms |
| GeoIP City Plus web service | 99.987% since 2018 | 1 ms | 1 ms | 2 ms | 7 ms |
| GeoIP Country web service | 99.987% since 2018 | 1 ms | 1 ms | 2 ms | 8 - 10 ms |
| GeoIP Legacy web services | 99.988% since 2014 | 1 ms | 2 ms | 3 ms | 7 - 9 ms |
These metrics last updated June 2024 based on a 90 day lookback.
Understanding latency
The internal latency metrics given above are the time it takes for MaxMind’s servers to process your request and send a response. Latency numbers in a given percentile mean that that percent of web service requests are processed by MaxMind’s servers within the given timeframe. For example, latency in the 99.9th percentile means that 99.9% of requests are processed in the time shown, and 0.1% of requests (1 in 1,000) may take longer.
Latency can be impacted by a number of issues, including your integration and the speed and location of your servers relative to MaxMind's servers. Depending on the location of your servers, you may want to add 20-60 ms for the transit time of your request. MaxMind serves GeoIP web service requests from servers in the following locations, and routes your requests to the nearest server:
- Oregon, United States
- Virginia, United States
- London, United Kingdom
- Singapore
If there are interruptions to MaxMind's web services or infrastructure issues that are slowing down MaxMind's response times, we will post about it on our Status page. You can subscribe to get updates about Status alerts.
This page was last updated on .