[REVISION HISTORY]
Microsoft 365 global service outage and economic impact
79 recorded revisions of this situation.
What changed
2026-11-19 15:39 UTC → 2026-11-21 14:52 UTC ·
added
removed
On November 12, 2026, Microsoft experienced a widespread global outage affecting key services including Outlook, Microsoft Teams, Copilot, Exchange Online, SharePoint, and Defender XDR. The disruption, which lasted approximately 36 to 38 hours, impacted more than 430 million people across approximately 74 countries. Microsoft ruled out cyberattacks or malicious activity, cyberattacks, attributing the failure to a latent software flaw triggered during a network capacity upgrade. Technical investigations revealed the disruption was triggered by a previously undetected bug in a network gateway update. Microsoft reported update that the bug had existed undetected in its data centers since July. Charles Lamanna, Microsoft Executive Vice President, stated the failure resulted from a traffic rerouting event. Following a capacity upgrade and an unrelated incident that reduced gateway capacity by approximately 14%, traffic from Teams was automatically rerouted to servers managing Outlook traffic. This surge caused server Outlook, causing a memory to overflow, leading to overflow and a cascade of system failures. Microsoft noted that standard Standard load testing failed to detect the bug because laboratory hardware used fewer processor cores than the production servers affected. servers. The outage resulted in caused significant real-world consequences. operational shifts. In Australia, the Queensland government agencies, courts, reported disruptions to public servants, with the Health and schools lost email access, Ambulance Services Minister stating that while the UK’s health system relies on Outlook, there was no significant impact on patient care. The Queensland Police Service transitioned to phones and radios, while some Brisbane schools used text messages to notify families. In the United Kingdom, the National Health Service had to reschedule certain procedures. procedures and revert to paper records. In Taiwan, financial firms utilized fax machines to conduct operations. In Germany, 15 hotel guests were reportedly injured by chlorine gas after a pool safety system failed to send warnings via email. email warnings. Economic impact estimates vary widely, vary, with the Anderson Economic Group estimating losses at approximately $7 billion. Insurance-related estimates range from $100 million to $700 million depending on the provider and policy coverage. Microsoft has fully since restored services. Following the incident, Microsoft apologized for the impact on customer operations. The company services and noted that affected customers may be eligible for service credits under Microsoft’s Service Level Agreement (SLA), provided they submit requests by December 31, 2026. credits.
Versions
- 2026-11-21 14:52 UTC Microsoft 365 global service outage and economic impact
- 2026-11-19 15:39 UTC Microsoft 365 global service outage and economic impact
- 2026-11-19 07:58 UTC Microsoft 365 global service outage and economic impact
- 2026-11-18 13:55 UTC Microsoft 365 global service outage and economic impact
- 2026-11-18 10:00 UTC Microsoft 365 global service outage and economic impact
- 2026-11-18 02:25 UTC Microsoft 365 global service outage and economic impact
- 2026-11-17 21:23 UTC Microsoft 365 global service outage and economic impact
- 2026-11-17 17:06 UTC Microsoft 365 global service outage and economic impact
- 2026-11-17 03:56 UTC Microsoft 365 global service outage
- 2026-11-16 21:25 UTC Microsoft 365 global service outage
- 2026-11-16 19:25 UTC Microsoft 365 global service outage
- 2026-11-16 17:12 UTC Microsoft 365 global service outage
- 2026-11-16 16:21 UTC Microsoft 365 global service outage
- 2026-11-16 16:17 UTC Microsoft 365 global service outage
- 2026-11-16 16:16 UTC Microsoft 365 global service outage
- 2026-11-16 14:34 UTC Microsoft 365 global service outage
- 2026-11-16 14:02 UTC Microsoft 365 global service outage
- 2026-11-16 10:55 UTC Microsoft 365 global service outage
- 2026-11-16 10:41 UTC Microsoft 365 global service outage
- 2026-11-16 10:38 UTC Microsoft 365 global service outage
- 2026-11-16 06:45 UTC Microsoft 365 global service outage
- 2026-11-16 02:21 UTC Microsoft 365 global service outage
- 2026-11-15 21:05 UTC Microsoft 365 global service outage
- 2026-11-15 13:44 UTC Microsoft 365 global service outage
- 2026-11-15 13:06 UTC Microsoft 365 global service outage
- 2026-11-15 07:48 UTC Microsoft 365 global service outage
- 2026-11-15 04:13 UTC Microsoft 365 global service outage
- 2026-11-14 23:58 UTC Microsoft 365 global service outage
- 2026-11-14 23:27 UTC Microsoft 365 global service outage
- 2026-11-14 23:25 UTC Microsoft 365 global service outage
- 2026-11-14 21:44 UTC Microsoft 365 global service outage
- 2026-11-14 19:59 UTC Microsoft 365 global service outage
- 2026-11-14 18:05 UTC Microsoft 365 global service outage
- 2026-11-14 17:14 UTC Microsoft 365 global service outage
- 2026-11-14 16:51 UTC Microsoft 365 global service outage
- 2026-11-14 16:47 UTC Microsoft 365 global service outage
- 2026-11-14 15:23 UTC Microsoft 365 global service outage
- 2026-11-14 14:14 UTC Microsoft 365 global service outage
- 2026-11-14 12:55 UTC Microsoft 365 global service outage
- 2026-11-14 12:52 UTC Microsoft 365 global service outage
- 2026-11-14 12:42 UTC Microsoft 365 global service outage
- 2026-11-14 12:12 UTC Microsoft 365 global service outage
- 2026-11-14 11:48 UTC Microsoft 365 global service outage
- 2026-11-14 11:10 UTC Microsoft 365 global service outage
- 2026-11-14 10:56 UTC Microsoft 365 global service outage
- 2026-11-14 10:53 UTC Microsoft 365 global service outage
- 2026-11-14 10:06 UTC Microsoft 365 global service outage
- 2026-11-14 10:01 UTC Microsoft 365 global service outage
- 2026-11-14 09:29 UTC Microsoft 365 global service outage
- 2026-11-14 08:47 UTC Microsoft 365 global service outage
Showing the 50 most recent. Select a version to see what changed compared to the one before it.