Microsoft details how three problems combined for a global outage
Summary
A defect in Microsoft’s cloud gateway, a shift in network traffic, and server capacity running 14% below optimal levels combined to cause a global outage from November 12 to November 13, 2026. The disruption affected Microsoft 365 and Exchange services, and more than 80% of the affected gateway servers froze. Microsoft said engineers needed to deploy a targeted system update because restarting the servers did not resolve the problem.Key Facts
- The outage began November 12 at 16:20 UTC and ended November 13 at 16:10 UTC.
- A cloud gateway change deployed starting in July introduced a defect that could exhaust CPU and memory resources under certain conditions.
- Microsoft said pre-release testing did not reveal the defect because the test hardware was less powerful than some production systems.
- About 15 hours before the outage, Microsoft shifted Teams traffic from an alternate gateway to the primary gateway, changing its traffic load and request mix.
- An existing fault left the gateway server fleet operating at 14% below optimal capacity.
- More than 80% of the affected gateway servers froze as requests accumulated.
- Restarting the servers did not work because queued requests quickly triggered resource exhaustion again.
- Microsoft classified the incident as a technical issue unrelated to cyberattacks or AI agents.
This is a fact-based summary from The Actual News. Click below to read the complete story directly from the original source.