- Level
- confirmed
- Worst impact
- Degraded
- Components
- O365
- Down Index
- 22of 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 4h 51m it lasted.
Anything that failed between 2025-04-25 10:28 UTC and 2025-04-25 15:19 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 3
- investigating
We are currently investigating delays for inbound messages on some Office365 channels.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
Issue is not resolved, opening a partner incident instead: https://front-partners.statuspage.io/incidents/sdln9wvbqdb7 Please contact Microsoft for assistance with an affected mailbox.
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-afc184ca16
Is Front still down?
No, this incident was resolved 2025-04-25 15:19 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
4h 51m, from 2025-04-25 10:28 UTC to 2025-04-25 15:19 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.