- Level
- confirmed
- Worst impact
- Degraded
- Components
- O365
- Regions
- us, us-west-1, us-west-2
- Down Index
- 32of 100
What to do
Check whether you use Front O365 in us, us-west-1, us-west-2. 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 2h 41m it lasted.
Anything that failed between 2026-09-14 08:20 UTC and 2026-09-14 11:01 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 5
- investigating
We're observing some Office 365 channels experience delays in sending and receiving messages. We're currently investigating.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We have established that channel sync error rate is <1%, but remains above our expected baseline rate. We are continuing to investigate.
provider
- monitoring
We are seeing error rates return to normal. We are continuing to monitor the health of our systems.
provider
- 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-15136e2a87
Is Front still down?
No, this incident was resolved 2026-09-14 11:01 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
2h 41m, from 2026-09-14 08:20 UTC to 2026-09-14 11:01 UTC, by the times Front posted.
What was affected?
Front named O365 in us, us-west-1, us-west-2.
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.