# API latency, measured live.

URL: https://email-validation.org/status/latency/
Updated: 2026-10-21

> Documentation index: https://email-validation.org/llms.txt

This page shows our monitor's timings of a real API request for an address already in our result cache, failures included. You can also time the API from your browser.

The page loads its figures in the browser from [/api/public/latency](https://email-validation.org/api/public/latency) (JSON, updated every minute while the monitor runs; a 60-minute summary is at [/api/public/latency/summary](https://email-validation.org/api/public/latency/summary)). It shows:

- the median (p50) response time of the last 60 minutes, and the 95th percentile of the same window;
- the 99th percentile and the probe counts of the last 24 hours (cache hits, misses and failures);
- a chart of the last 24 hours, 7 days or 30 days, with failed probes marked, and the same figures as tables.

When there is no fresh measurement the page says so (Measuring, Stale or Failed) and shows no figure.

## How we measure

- **What is timed**: One real, authenticated `POST /v1/validate` every 60 seconds, over HTTPS through the public API host.
- **The address**: A fixed test address on a reserved .invalid domain that belongs to nobody. Its result is in our 12-month cache, so this times our API, not a mail server.
- **Cache check**: Each answer is checked to be a cache hit. Percentiles (nearest rank) count hits only; misses are shown apart.
- **From where**: Cloudflare's network to our API, which runs in one US East region. Your own requests add your distance to us.
- **What it leaves out**: A first-time check waits for the mail server, up to 15 seconds; if it runs out of time, it is unknown and free.
- **Cost**: A cached answer costs 1 credit, like any completed check. The monitor pays for its probes.
- **Every probe counts**: Failed probes stay in the chart and in the counts.

## Test from your browser

The page can time 5 requests from your browser to `GET https://api.email-validation.org/v1/latency`, which looks the same test address up in our cache (no key, no credits). It shows your round trip, the time inside our API and the Cloudflare data centre your requests entered. The API runs in one US East region, so your round trip includes the distance between you and us.

## Measure it yourself

With your own API key (each request uses 1 credit, cached or not; sandbox test addresses are answered on the spot, so they do not time the cache):

```bash
curl -s -o /dev/null -w "%{time_total}\n" \
  -H "Authorization: Bearer $EV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"name@example.com"}' \
  https://api.email-validation.org/v1/validate
```

## Built for speed

- **A first-round-trip budget**: Every build checks our home page, the free checker and this page against 14,600 bytes with headers: about what arrives in the first network round trip.
- **No third-party requests**: Our pages load nothing from other companies' servers. The bot check loads only when a form needs it.
- **Nothing blocks the first paint**: No external stylesheet, font download or blocking script before you see the page.
- **Next page, already loaded**: Pages you are likely to open next are fetched before you click, in browsers that support it.
- **Repeat checks come back at once**: Checked recently? The answer comes from our result cache, with no mail server to wait on.
- **A 15-second ceiling**: No check runs past 15 seconds. Slower ones are unknown and free.
- **Up to 500 requests per second**: Per account after your first purchase; 20 per second before that.
- **One pass through your list**: Up to 1,000,000 rows. Each unique address is checked once, with no second pass.

No uptime percentage is shown until there are enough measurements to back it.

Live status of every component: [System status](https://email-validation.org/status/).