OUTBU DELIVERY OBSERVATORY
How mail is reaching the receiving networks.
A rolling 24-hour view of real outbound mail, measured from SMTP responses.
Snapshot
- Complaints / delivered
- Expired
- MX acceptance p95
Volume, bounces and delays by hour
Bars show each hour’s share of accepted recipients. Lines show bounce and deferral rates on a 0–100% scale.
Times use your browser’s local timezone.
Why delivery failed or slowed
Each recipient contributes at most one observation per kind. A deferral can later become a delivery.
No bounces, deferrals or expiries were observed in this accepted-traffic window.
Limited sample
100.00%
Delivered
Microsoft / Outlook
No accepted traffic
—
Delivered
Yahoo / AOL
No accepted traffic
—
Delivered
Apple iCloud
No accepted traffic
—
Delivered
GMX
No accepted traffic
—
Delivered
Zoho
No accepted traffic
—
Delivered
Proton Mail
No accepted traffic
—
Delivered
Unidentified network
No accepted traffic
—
Delivered
What these numbers mean
Delivered means the receiving SMTP server accepted the message. It does not establish inbox placement or a human read.
Delivery, bounce, expiry and pending are separate final outcomes. Deferrals overlap them; a message can be delayed and then delivered.
Rates and percentiles describe every available observation, even with a small sample. Health verdicts need at least 20 recipients: issues at 5% bounces, 20% deferrals or 0.3% complaints; degraded at 2%, 5% or 0.1%. A limited sample is different from no accepted traffic. A healthy verdict also requires a measurable complaint rate.
Public data contains aggregate rates, hourly shares and broad failure categories, with no account, project, domain, IP or recipient identifiers, exact volumes or raw SMTP responses. Complaint rates require 100 deliveries across three accounts; a hidden complaint rate does not mean zero. Statistics refresh every 15 minutes.
Open your workspace