Microsoft Outlook Office 365 Down

Incident Report for Life School

Resolved

Microsoft issues apology statement after lengthy outage, says it was a 'technical issue'

"We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.

"This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.

"Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.

"We will provide a full post-incident report once our review is complete."
Posted Nov 13, 2026 - 11:37 CST

Identified

Microsoft has revealed the cause of the massive outage:
"Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery. The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic."
Posted Nov 13, 2026 - 11:36 CST

Investigating

We are currently investigating this issue.
Posted Nov 12, 2026 - 12:24 CST
This incident affected: Office 365.