Free tools Windows power users keep installed
One-click scans. No signup required.
To measure email delivery latency, subtract a clearly defined sender-side submission or handoff time from an observed arrival time in the recipient’s mailbox. Keep SMTP acceptance, provider processing, and mailbox arrival as separate events: they measure different parts of the journey. If you cannot observe the mailbox, report the proxy you used rather than calling it inbox delivery.
Define the interval before you measure it
Choose the start and end events to match the question you need to answer. For a user-facing send-to-inbox measurement, use a timestamp for the message’s submission or handoff from the sending application to its outbound mail service, and an independently observed timestamp for its arrival in the recipient’s mailbox.
As an Amazon Associate I earn from qualifying purchases.
For each message and recipient, calculate:
Latency = observed mailbox-arrival time − sender-side submission or handoff time
Name the actual events and timestamp sources in any report. If the recipient mailbox cannot be observed, state the last event you can verify—for example, acceptance by a receiving SMTP server—and label the result accordingly. An SMTP server’s successful completion response means it accepted responsibility for the message; it does not establish when the message became visible in the inbox. RFC 5321
#1 Best Overall
Measure a message from start to finish
- Record the sender-side start. Capture when the application submitted the message or when the outbound service accepted the handoff. Specify which event you chose; “sent” alone is ambiguous.
- Observe the recipient-side arrival. Record when the message appears in the recipient’s mailbox, if that event is available to you. Keep it distinct from an SMTP acceptance timestamp or an internal provider event.
- Correlate the same message across systems. Save the complete raw headers from the recipient copy, plus available provider message IDs and event timestamps. Exchange message traces can be narrowed using sender, recipient, and the general sending time. Microsoft’s Exchange Online Message Trace FAQ
- Calculate elapsed time per recipient. Subtract the chosen start timestamp from the observed arrival timestamp. Preserve individual results rather than combining different recipients or routes into one unexplained number.
- Describe the sample. For repeated messages, state the observation window, recipient-provider mix, number of observations, and any excluded failures. Report a clearly defined distribution rather than presenting one message as representative.
Use Received headers to locate slow hops
Mail servers add Received trace fields as they accept a message for delivery or further processing. The newest field is at the top of the header, with earlier relay entries below it. Compare adjacent entries to estimate the time between those hops. RFC 5321 requires receiving SMTP servers to insert trace information and says explicit timezone offsets should be used where feasible. RFC 5321
Normalize timestamps before subtracting them: use each header’s numeric timezone offset to convert its timestamp to a common basis, such as UTC. A large apparent interval between two adjacent entries can point to delay around that relay interval, but it is not proof of fault by itself. Different servers may have skewed or inaccurate clocks; headers can be missing, changed by gateways, or nonconforming. Check provider-side records and related events before assigning a cause.
Rank #2
A header analyzer can make the chain easier to read. Twilio SendGrid’s troubleshooting guide describes using Google Admin Toolbox Message Header Analyzer for this purpose. Twilio SendGrid: Troubleshooting Email Delivery Delays and Latency
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteInterpret provider traces and metrics by their boundaries
Provider traces can show what happened inside that provider’s pipeline, but they do not necessarily cover the full route from the sending application to the recipient’s mailbox. Microsoft says Exchange message-trace timestamps can show how long the service takes to process each event. Use them to identify where the message spent time inside Exchange, then combine them with sender-side and recipient-side evidence for an end-to-end measurement. Microsoft’s Exchange Online Message Trace FAQ
Rank #3
In Exchange, the MessageLatency property has a narrower definition: the time from the message’s first entry into the Submission queue until it is placed in the queue. It is not the total time through remote relays and into a recipient’s mailbox. Microsoft: Properties of messages in queues
Similarly, the Delivered-To header annotates a delivery event, not a universal timestamp for final inbox visibility. Aliases, mailing lists, and address transformations may produce multiple delivery transitions, so interpret the field in context. RFC 9228
Rank #4
Compare measurements without mixing unlike intervals
| Evidence or metric | What interval or event it describes | What it does not establish |
|---|---|---|
| Observed send-to-inbox latency | Chosen sender-side submission or handoff to observed mailbox arrival, when both endpoints are available. | It does not identify the responsible hop on its own. |
| SMTP positive completion response | The receiving SMTP server accepts responsibility after the message data is completed. | It does not show when the message appeared in the recipient’s mailbox. RFC 5321 |
Adjacent Received timestamps |
An estimate of elapsed time between two recorded relay events, subject to timestamp and header limitations. | It is not necessarily the whole delivery path or a definitive attribution of delay. RFC 5321 |
| Exchange trace event timestamps | Events and processing intervals visible within Exchange Online’s service. | They do not automatically include the path from the sending application through remote relays to observed mailbox arrival. Microsoft’s Exchange Online Message Trace FAQ |
Exchange MessageLatency |
First entry into the Submission queue until placement in the queue. | It is not remote-relay or recipient-inbox latency. Microsoft: Properties of messages in queues |
Delivered-To |
A delivery transition recorded in a header field. | It is not a universal final-visibility timestamp. RFC 9228 |
Troubleshoot a delayed message
Start with the message evidence
For a single delayed message, preserve its raw headers and identify the sender, recipient, and relevant time window. Parse the Received chain, normalize its offsets, and compare the events with any provider trace. In Exchange Online, run a message trace and inspect event timestamps and details; combine its service-side sequence with the headers and recipient-side observation if the question is end-to-end latency. Microsoft’s Exchange Online Message Trace FAQ
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Look for a gap, then investigate its context
A long interval between recorded relay events suggests where to investigate, but first account for clock accuracy, missing trace fields, and gateway changes. Provider event details can help distinguish service processing from an unresponsive destination, a large message, or blocking; Microsoft lists these among possible reasons for slow arrival. Microsoft’s Exchange Online Message Trace FAQ
Escalate to network-level evidence only when needed
If headers and provider traces do not explain a protocol stall, packet capture may help investigate the network exchange. SendGrid discusses it as a deeper troubleshooting step; it is not required for routine timestamp-based latency measurement. Twilio SendGrid: Troubleshooting Email Delivery Delays and Latency
Report results so others can interpret them
Include enough detail for a reader to understand what your number covers:
- The exact start and end events, and where their timestamps came from.
- How timestamps were converted to a common timezone and whether the evidence uses clocks from multiple systems.
- Whether the result is for one recipient, one provider route, or a sample across multiple providers.
- The observation window, sample size, distribution reported, and any excluded failures.
- Whether you measured actual mailbox arrival, provider processing, SMTP acceptance, or only selected relay intervals.
The standards and vendor documentation cited here do not establish a universal normal send-to-inbox latency or a cross-provider benchmark. SMTP retry and timeout rules describe protocol behavior, not representative arrival times. Avoid comparing measurements until their endpoints, provider coverage, and timestamp sources match.
Recommended Free Tools
Quick Recap
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.
