Delivery latency, last 30 days
1.1 sfrom API call to the recipient’s server.
The median time between eusend accepting your request and the receiving mail server accepting the message. 95% are accepted within 8.9 s, 99% within 1.1 min. Updated every ten minutes, last at 16:56 UTC.
Deliveries drawn at random from the last 30 days. Each dot is one message, placed by how long it took.
Most of it is the receiving server.Our part takes about 323 ms.
- API to MTA
- Validated, queued, rendered, DKIM-signed and handed to our mail server
- 323 ms · p95 1.0 s
- MTA to remote 250
- Connection, TLS and the receiving server’s answer, retries included
- 1.0 s · p95 8.2 s
Per mailbox provider.European providers first.
EuropeanMedian, last 30 daysp50p95
GMX & WEB.DE
GlobalMedian, last 30 daysp50p95
Gmail
iCloud
Too few days
6.2 s15 sOutlook
Yahoo & AOL
Too few days
2.2 s5.5 sDay by day.The last 30 days, in UTC days.
18 Sept17 Oct
| 2026-09-18 | 2.9 s |
|---|---|
| 2026-09-19 | 1.2 s |
| 2026-09-20 | 1.1 s |
| 2026-09-21 | 1.2 s |
| 2026-09-22 | 1.4 s |
| 2026-09-23 | 1.2 s |
| 2026-09-24 | 1.1 s |
| 2026-09-25 | 1.3 s |
| 2026-09-26 | 1.1 s |
| 2026-09-27 | 2.8 s |
| 2026-09-28 | 1.1 s |
| 2026-09-29 | 1.1 s |
| 2026-09-30 | 1.0 s |
| 2026-10-01 | 1.2 s |
| 2026-10-02 | 1.0 s |
| 2026-10-03 | 821 ms |
| 2026-10-04 | 617 ms |
| 2026-10-05 | 1.2 s |
| 2026-10-06 | 1.1 s |
| 2026-10-07 | 1.2 s |
| 2026-10-08 | 1.4 s |
| 2026-10-09 | 1.4 s |
| 2026-10-10 | 1.2 s |
| 2026-10-11 | 1.1 s |
| 2026-10-12 | 1.2 s |
| 2026-10-13 | 1.2 s |
| 2026-10-14 | 1.0 s |
| 2026-10-15 | 1.1 s |
| 2026-10-16 | 1.2 s |
| 2026-10-17 | 1.2 s |
18 Sept17 Oct
| 2026-09-18 | 30 s |
|---|---|
| 2026-09-19 | 8.3 s |
| 2026-09-20 | 3.9 s |
| 2026-09-21 | 6.8 s |
| 2026-09-22 | 6.1 min |
| 2026-09-23 | 8.5 s |
| 2026-09-24 | 7.7 s |
| 2026-09-25 | 8.8 s |
| 2026-09-26 | 8.8 s |
| 2026-09-27 | 16 s |
| 2026-09-28 | 8.7 s |
| 2026-09-29 | 7.3 s |
| 2026-09-30 | 10 s |
| 2026-10-01 | 7.7 s |
| 2026-10-02 | 8.2 s |
| 2026-10-03 | 38 s |
| 2026-10-04 | 3.3 s |
| 2026-10-05 | 6.6 s |
| 2026-10-06 | 1.1 min |
| 2026-10-07 | 8.1 s |
| 2026-10-08 | 38 s |
| 2026-10-09 | 6.4 s |
| 2026-10-10 | 9.3 s |
| 2026-10-11 | 6.0 s |
| 2026-10-12 | 6.1 s |
| 2026-10-13 | 5.3 s |
| 2026-10-14 | 4.9 s |
| 2026-10-15 | 6.4 s |
| 2026-10-16 | 7.3 s |
| 2026-10-17 | 12 s |
How it is measured.And what it does not tell you.
What exactly is measured?
The time from eusend accepting your API request to the recipient’s mail server answering 250 — accepted for delivery. The end timestamp is our mail server’s own record of that answer. Scheduled sends are measured from their scheduled time, not from the API call.
Are deferrals and retries included?
Yes. When a receiving server defers a message and accepts it on a later attempt, the whole wait counts. That is most of the long tail: the 99th percentile is mostly providers rate-limiting, not eusend.
Does this show where the message ends up?
No. Accepted by the recipient’s server is the last point we can observe. How the provider then files the message is decided on their side, and we do not measure it.
What is left out?
Messages that bounced or were never accepted have no acceptance time, so they are not in these figures. Providers with too few deliveries in the window to give a stable percentile are hidden.
How often is it updated?
Every ten minutes, over a rolling 30-day window of UTC days. The dot strip is always the same number of randomly drawn deliveries, so it shows the shape of the distribution and nothing about volume.
For how we protect sending reputation, see Deliverability.