Microsoft says July software defect caused multi-day Exchange Online outage
Microsoft published a preliminary incident report saying a code change made in July 2026 to its network gateway servers contained a defect that passed load testing but went unnoticed. A surge in traffic combined with roughly 14% of server capacity being offline triggered lock contention that exhausted CPU and memory on affected machines, causing a cascading failure that left more than 80% of servers unresponsive at its worst and knocked out Microsoft 365 email for customers.
GoKawiil's interpretation of the reporting above, not reported fact.
The incident highlights how load testing that focuses on older, weaker hardware can miss defects that only appear on newer, higher-core machines, a gap Microsoft itself acknowledges in its report. Because engineers had to patch the flawed fix rather than roll it back, the episode suggests resolving large-scale cloud outages can require riskier, slower remediation than simple reversion, which may raise questions for enterprises relying heavily on Microsoft 365 availability.
- Microsoft attributes the outage to a defect introduced in a July 2026 update to network gateway servers.
- The flaw caused lock contention that exhausted CPU and memory, worsened on newer, higher-core hardware.
- A traffic surge plus 14% capacity loss triggered cascading failures, leaving over 80% of servers unresponsive at the peak.
Source: theregister.com — Richard Speed, 2026-11-16
Published there as: “Microsoft blames monster email outage on software defect introduced in July fix”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.