Skip to main content
Front

Exchange Online mailboxes sync delay [office365]

Degraded Lasted 18h 11m · started · Front's page

Level
confirmed
Worst impact
Degraded
Components
O365
Down Index
24of 100

What to do

  • Check whether you use Front O365. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 18h 11m it lasted.

    Anything that failed between 2024-11-25 08:41 UTC and 2024-11-26 02:52 UTC may need a replay.
  • Subscribe to Front's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=front works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Front 6

  1. identified

    Our partner Microsoft is experiencing a service degradation affecting Exchange Online mailboxes. You can follow Microsoft Issue ID MO941162 for more details. This may cause outbound/inbound delays for customers using Office 365, as Front cannot connect to Microsoft servers.

    provider

  2. identified

    Microsoft is still investigating the issue; here is their latest update. > We’re continuing to investigate recent changes, service telemetry and the failure paths to determine the root cause of impact. Source: https://portal.office.com/Adminportal/Home#/servicehealth/:/alerts/MO941162 (You need to be an O365 admin to be able to access it)

    provider

  3. identified

    Microsoft is deploying a fix > At 15:27 CET > We’re monitoring the progress of the fix, which has been deployed to approximately 60% of the affected environments. We’re continuing our manual restarts on the remaining impacted machines. We are closely monitoring our systems for signs of recovery; however, we have not observed any significant progress at this time.

    provider

  4. monitoring

    Microsoft deployed a fix. Our systems are recovering. Latest update from Microsoft: > At 20:52 CET > We're continuing to redirect traffic and apply targeted remediation to impacted servers. > We've observed initially positive results in some areas, and we're monitoring service health closely as our mitigation workstreams continue in parallel.

    provider

  5. monitoring

    Our systems have fully recovered. We are now retrying failed tasks.

    provider

  6. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-f3432d8c47

Is Front still down?

No, this incident was resolved 2024-11-26 02:52 UTC. For Front's live state, see https://down.guide/front.

How long did it last?

18h 11m, from 2024-11-25 08:41 UTC to 2024-11-26 02:52 UTC, by the times Front posted.

What was affected?

Front named O365.

What caused it?

Front hasn't published a root cause. If it does, it shows here.

Where does this come from?

Front's official status page, https://www.frontstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.