Share via

Delay in Receiving emails

Sales Team 0 Reputation points
2026-05-19T10:11:38.9833333+00:00

We would like to report an issue where we are occasionally receiving emails with a significant delay of around 4–5 hours. This delay is impacting our communication and project timelines.

Could you please investigate the cause of these delays and advise on corrective measures? If needed, we can provide message headers from affected emails to help with troubleshooting.

Thank you for your prompt attention to this matter.

Outlook | Web | Outlook.com | Email
0 comments No comments

2 answers

Sort by: Most helpful
  1. EmilyS726 240.4K Reputation points Independent Advisor
    2026-05-19T12:18:08.78+00:00

    Are you using personal outlook.com/hotmail.com address?

    Any chance these delays are from email addresses such as Yahoo/Gmail.com?

    If so, there has been issue the last few days, and these incoming emails were queued and sent when the issue was cleared, hence the delay.

    Let me know if that might be your case.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-05-19T10:12:02.7466667+00:00

    Delayed email delivery can have several causes across Outlook.com and Exchange Online. Based on the provided information, use the following steps to investigate and mitigate:

    1. Run message traces for delayed messages
      • As a Microsoft 365 admin, use the message trace tool to see where messages are being delayed in the pipeline.
      • Message trace data is typically available 10–60 minutes after a message is sent.
      • Use as many criteria as possible (sender, recipient, approximate send time) to narrow results.
      • Review the events and timestamps to see:
        • Whether the destination server was unresponsive.
        • Whether the message was large and took longer to process.
        • Whether there was service latency or filtering.
      • This will show exactly where the delay occurs and whether it is recurring for specific senders or domains.
    2. Interpret common delay causes from trace results When reviewing message trace details, pay particular attention to:
      • Destination responsiveness: If the intended destination is not responsive, this is the most likely cause of delay.
      • Message size: Large messages can take longer to process.
      • Service latency: Latency in the service can cause temporary delays.
      • Filtering: The message might have been blocked or held by filtering services.
    3. Use admin tools if delays persist
      • If Support and Recovery Assistant or basic checks do not resolve the issue, continue using the Exchange admin tools and message trace to monitor for patterns.
      • For messages older than seven days, use the “View pending or completed traces” option in the message trace tool to review historical traces. Note that traces with data older than seven days are automatically deleted.
    4. Monitor for priority or high‑impact users
      • If delays are affecting executives or other high‑impact users, and the organization meets the licensing and usage requirements, use the Email issues for priority accounts report in the new Exchange admin center.
      • This report shows failed events from the last 15 minutes and delayed messages from the last 6 hours for priority accounts, helping quickly identify systemic issues.
    5. Collect and share message headers
      • For each delayed message, collect full message headers and correlate them with message trace results.
      • The headers and trace together will show hop‑by‑hop timestamps and where the delay is introduced (sending system, intermediate filtering, or Exchange Online/Outlook.com).
    6. Typical remediation actions based on findings
      • If destination servers are slow or unresponsive: Work with the destination mail provider or internal mail gateway team to address performance or connectivity issues.
      • If messages are large: Encourage users to reduce attachment sizes or use file‑sharing services instead of large attachments.
      • If filtering or blocking is involved: Adjust anti‑spam/anti‑malware policies or allow‑lists as appropriate, based on what the trace and filtering logs show.

    These steps provide an end‑to‑end path: identify delayed messages, trace them through the pipeline, determine the cause (destination responsiveness, size, latency, or filtering), and then apply targeted corrective actions.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.