The minFraud web services are fast and reliable, with around 99.9% uptime since 2013. 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:
| minFraud web service | Uptime | Internal Latency by Percentile | |||
|---|---|---|---|---|---|
| 50% | 90% | 99% | 99.9% | ||
| minFraud Score web service | 99.985% since 2018 | 17 - 19 ms | 46 - 50 ms | 80 - 84 ms | 154 - 170 ms |
| minFraud Insights web service | 99.981% since 2017 | 30 - 36 ms | 64 - 68 ms | 108 - 122 ms | 225 - 255 ms |
| minFraud Factors web service | 99.982% since 2018 | 46 - 50 ms | 80 - 88 ms | 136 - 166 ms | 226 - 303 ms |
| minFraud Legacy web services | 99.987% since 2013 | 34 - 36 ms | 58 - 62 ms | 95 - 101 ms | 195 - 239 ms |
These metrics last updated August 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 and the kinds of data you send to minFraud.
Depending on the location of your servers, you may want to add 20-60 ms for the transit time of your request. MaxMind serves minFraud web service requests from servers in the following locations, and routes your requests to the nearest server:
- Oregon, United States
- Virginia, United States
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 .