Recommended Free Tools
To measure email delivery latency, subtract a clearly defined sender-side submission or handoff time from an observable arrival time in the recipient’s mailbox. Do not treat SMTP acceptance, a provider’s internal processing metric, or a single Received hop as proof of inbox arrival: each marks a different point in the mail path.
Define the start and end events
Choose observable events before collecting timestamps. For a user-facing send-to-inbox measurement, define the start as the message’s submission by the sending application or its handoff to the outbound mail service. Define the end as its observable arrival in the recipient’s mailbox. Calculate each message’s elapsed time as:
latency = recipient mailbox arrival time − sender-side start time
Record arrival separately from submission. If you cannot observe the recipient mailbox, name the proxy you use—such as SMTP acceptance or a provider trace event—and report it as that interval, not as inbox latency. Specify whether the result covers one recipient, one provider route, or a sample spanning several providers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Collect and correlate message evidence
- Save the recipient copy’s complete raw headers. Preserve the full
Receivedchain and any delivery-related fields before analyzing them. - Record the sender-side start time and its event definition. For example, distinguish application submission from handoff to the outbound mail service.
- Keep identifiers and timestamps from each system. Provider message IDs and event times help establish that sender, relay, trace, and recipient records refer to the same message.
- For Exchange Online traces, narrow the search. Microsoft describes using sender, recipient, and the general sending time to locate a message; inspect the trace’s event timestamps and details. Microsoft’s Message Trace FAQ explains that those timestamps show how long the service takes to process each event.
Read timestamps in the Received chain
SMTP servers add Received trace fields as a message is received for delivery or further processing. The newest field is at the top; earlier relay fields appear below it. Compare adjacent timestamps to estimate the time between those hops. RFC 5321 says servers creating these fields should use explicit timezone offsets where feasible.
- Read the timestamp and numeric timezone offset in each relevant field.
- Convert timestamps to a common basis, such as UTC, before subtracting them.
- Subtract adjacent times to estimate the interval between the corresponding relay events.
- Compare these intervals with sender-side, provider-trace, and recipient-side records before attributing a delay to a particular system.
These are hop-level estimates, not automatically the end-to-end time to mailbox visibility. Different systems write the fields, so clock skew, inaccurate clocks, missing fields, gateway transformations, or nonconforming headers can distort intervals. RFC 5321 also notes that gateways can carry trace fields from environments that do not conform exactly to its specification.
Rank #2
Know what each timestamp actually measures
| Evidence or metric | What it measures | What it does not establish |
|---|---|---|
| Observed recipient mailbox arrival | The end event for a send-to-inbox measurement, if the arrival is directly observed and correlated to the message. | It does not by itself explain which relay or processing step caused the elapsed time. |
| SMTP positive completion reply after message data | The receiving SMTP server has accepted responsibility for the message, as specified by RFC 5321. | It is not proof that the message is already visible in the recipient’s inbox; subsequent processing or forwarding can remain. |
Received fields |
Trace evidence for the times servers handled a message for delivery or further processing; adjacent fields can help estimate hop intervals. | They are not a universal inbox-arrival stopwatch, and their timestamps can be affected by clock or header problems. |
Delivered-To |
A delivery transition. RFC 9228 describes the field as annotating delivery and permits address transformations to be recorded in separate fields. | It is not a universal final-visibility timestamp. Aliases, mailing lists, and additional processing may create multiple transitions. |
Exchange MessageLatency |
In Exchange queue properties, the time from a message’s first entry into the Submission queue until it is placed in the queue, according to Microsoft’s definition. | It does not measure the full route through remote relays to the recipient mailbox. |
Use provider traces to locate a delay
A provider trace can reveal events and timestamps within that provider’s own pipeline. In Exchange Online, inspect the message trace’s event details to see the service’s processing sequence. Combine that evidence with raw headers and recipient-side observation when measuring end-to-end latency; a trace alone does not necessarily cover the sending application, every external relay, and mailbox arrival.
When aligned records show a long gap between two Received timestamps, investigate the relay interval between them, while accounting for timestamp limitations. Provider event details may help distinguish service processing from an unresponsive destination, a large message, or a blocked message. Microsoft lists these among possible reasons a message may take a long time to arrive; the trace is the place to inspect the relevant event details.
Rank #3
Troubleshoot one delayed message first
- Preserve the raw message headers from the recipient copy and collect the matching provider message ID and trace records.
- Parse the header path. Twilio SendGrid’s troubleshooting guide describes using the Google Admin Toolbox Message Header Analyzer to inspect
Receivedfields and compare timestamps. See SendGrid’s guidance on delivery delays and latency. - Inspect provider-side events. For Exchange Online, run a message trace with sender, recipient, and a suitable time window, then review timestamps and event details.
- Escalate only if the records leave a protocol stall unexplained. SendGrid discusses packet capture for deeper network-level analysis; it is an advanced diagnostic step, not a prerequisite for routine timestamp measurement.
Report measurements so they can be interpreted
For repeated observations, retain each message’s elapsed time and describe the sample window, recipient-provider mix, event definitions, timestamp sources, timezone normalization, and any excluded failures. State whether the measurement reflects internal processing, a set of relay intervals, or actual observed mailbox arrival. When comparing monitoring approaches, compare their start and end events, visible providers and hops, per-recipient coverage, and whether timestamps come from one system or multiple clocks.
The official standards and vendor documentation cited here do not establish a universal “normal” send-to-inbox latency figure. SMTP timeout and retry rules describe protocol behavior, not a representative inbox-delivery benchmark. A benchmark claim therefore needs a separately sourced measurement study with a clearly scoped route and method.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
