Outlook and Exchange Online outage, 12 November 2026: what happened
Exchange Online and Outlook failed for about 24 hours from 16:20 UTC on 12 Nov 2026. Microsoft blamed a latent bug in its connection systems.
- From 16:20 UTC on Thursday 12 November 2026 to 16:10 UTC on Friday 13 November, users could not reliably connect to Exchange Online, Outlook and other Microsoft 365 services.
- Microsoft's preliminary cause was a latent bug in the systems that establish connections to Exchange Online, exposed by traffic shifts during network maintenance.
- Microsoft said it was a technical fault, not a cyber attack, and held delayed mail for up to 48 hours instead of bouncing it.
| Field | Detail |
|---|---|
| Provider | Microsoft 365 (Exchange Online, Outlook) |
| Started | 12 November 2026, 16:20 UTC |
| Ended | 13 November 2026, 16:10 UTC (official window) |
| Services | Exchange Online, Outlook, Teams, SharePoint Online, Copilot, Defender XDR, Purview, Intune and more |
| Status | Resolved |
| Official reference | EX1550543 (Exchange Online) |
Microsoft first posted on X that users in the Americas could not reach Exchange Online mailboxes through several connection methods, and pointed admins to incident EX1550543 in the Microsoft 365 admin center. It later widened the warning to users in any region (KSAT, embedding the @MSFT365Status post).
Downdetector logged nearly 130,000 US reports of Outlook problems just after 1 p.m. EST, and reports came from 74 countries and territories within about an hour. The UK NHS, Deutsche Bahn and the Japanese government's IT infrastructure were among those hit (DW).
AP reported that a number of servers had failed automated health checks, that early recovery attempts did not take effect, and that users in Asia were still reporting problems on Friday morning local time (AP).
The public incident listed 20 affected services. Microsoft stopped listing it at 05:44 UTC on 14 November with the note "sustained service recovery" (MicrosoftRadar archive).
- Exchange Online: Outlook on the web, Outlook desktop, Exchange ActiveSync and REST access, plus delayed delivery.
- Teams features that depend on Exchange, such as calendar.
- SharePoint Online, Microsoft 365 Copilot, Defender XDR, Purview, Intune, Planner, Power Apps, Graph, Fabric and Power BI, To Do, Universal Print and Windows 365 (Customer Key).
Microsoft extended the email timeout to 48 hours so that delayed mail would be kept rather than returned (The Verge).
Microsoft's preliminary root cause was "a failure in the systems responsible for establishing connections to the Exchange Online service". Traffic shifts during standard network maintenance and upgrades exposed a latent bug. Requests queued rapidly until the affected servers ran out of processing capacity and could not accept new connections (status mirror).
The final status said the issue was introduced during an earlier network capacity upgrade and surfaced after a recent network change, and that it was not related to cyber activity or AI agents. Microsoft said a full post-incident report would follow; we could not confirm the MO-series ID for the wider incident.
- Do not resend everything. Mail held in the 48-hour window should arrive on its own; check message trace first.
- Ask senders who saw bounces to resend only those messages.
- Note the incident ID in your own records in case you need it for an SLA conversation.
- Keep a second way to reach customers and staff for urgent messages when email is down.
| Date | Incident | Reported length | Source |
|---|---|---|---|
| 25-26 Nov 2024 | MO941162 | About 33 hours | BleepingComputer |
| 9-10 Jul 2025 | Mailbox access | About 19-21 hours | The Register |
| 22 Jan 2026 | MO1221364 | About 8 hours | TechRepublic |
| 31 Aug 2026 | EX1464935 | Nearly 12 hours | Tom's Guide |
| 12-13 Nov 2026 | EX1550543 | About 24 hours | Status mirror |
The fault was not a single broken server that could be swapped out. Requests queued faster than servers could clear them, so servers ran out of capacity and then failed automated health checks. AP reported that a number of servers had failed automated health checks and that early recovery attempts did not take effect.
The 12 November outage was not the only Exchange problem in November 2026. An aggregator that mirrors Microsoft's status page records two smaller ones (IsDown); their incident IDs were not confirmed:
- 9 November: some users in Europe, the Middle East and Africa saw errors in Outlook on the web for about 4 hours, put down to unexpected connection terminations in part of Exchange Online.
- 6 November: some users could intermittently not send to Outlook.com, Hotmail.com and Live.com addresses for about 3 days, with SPF-related bounce codes.
When did the November 2026 Outlook outage start and end?
Microsoft's official window ran from 16:20 UTC on 12 November to 16:10 UTC on 13 November 2026. Some users saw residual delays into 14 November.
Was the Outlook outage a cyber attack?
No. Microsoft said it was not aware of malicious activity and described a technical issue not related to cyber or AI agents.
Did I lose email during the outage?
Microsoft extended the email timeout to 48 hours to preserve delayed mail, so most messages should have arrived late rather than bounced.
What is the incident ID?
EX1550543 for Exchange Online. We could not confirm the ID of the wider Microsoft 365 incident.