Latency and uptime for the minFraud web services
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
| Internal latency by percentile | |||||
| minFraud web service | Uptime | 50% | 90% | 99% | 99.9% |
|---|---|---|---|---|---|
| minFraud Score web service | 99.987% since 2018 | 22 ms | 65 ms | 112 ms | 181 ms |
| minFraud Insights web service | 99.983% since 2017 | 33 ms | 81 ms | 138 ms | 223 ms |
| minFraud Factors web service | 99.985% since 2018 | 73 ms | 119 ms | 181 ms | 259 ms |
These metrics are provided to give you an idea of MaxMind's response time. Actual latency will vary and can depend on a number of different factors, including the kind of data that you send to minFraud. Read more about latency below.
These metrics last updated August 2026 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.
How do we support customers during higher traffic and transaction volumes throughout the holiday season?
Load testing
Fraud prevention shouldn't disrupt the checkout process. Each year, we begin preparing our servers in late October so we can easily handle higher traffic levels and maintain consistent performance.
Code freeze
To help ensure reliability during the busiest weeks of the year, we'll pause code changes from mid-November through early December. Regular feature updates and improvements to our services will resume after the code freeze.
Incident response
We don't expect issues, but we're prepared if they occur.
- Site Reliability Engineers on call 24/7
- Continuous logging and monitoring of all web services
- A regularly tested and updated Incident Response Plan
Don't run out of service credit!
Enable auto-recharge to prevent interruptions caused by low service credit. Here's how to set it up.
Contact options
If you experience an integration issue, please check our Status page for any known incidents and updates.
If your issue isn't listed there, please submit a support request.