Sunday, 22 November 2026

MobilesTechLand

Why Was Outlook Down? Microsoft’s Final Outage Report Explained

Microsoft's final report on the November 12 Outlook outage blames a months-old bug on its own email servers. Here is what failed, which emails bounced, and what to do now.

Quick answer

Outlook went down on November 12, 2026 because a hidden bug in a Windows update, used only on Microsoft's own email gateway servers, made them freeze under heavy load. Microsoft's final report says no business email was lost and it was not a cyberattack, but some messages to personal mailboxes inactive for 30+ days bounced.

Man typing on a laptop with a web page open on the screen
In this guide (9 sections)
  1. Why Was Outlook Down on November 12?
  2. How One Bug Took Down Outlook Worldwide
  3. Who Was Affected by the Microsoft 365 Outage?
  4. Was Any Email Lost?
  5. What to Do Now
  6. How to Check If Outlook Is Down Next Time
  7. What Microsoft Says It Will Change
  8. Was It Connected to the Other Outages That Week?
  9. Quick Answers

Updated November 22, 2026

The Outlook outage of November 12, 2026 was caused by a hidden bug in a Windows update that ran only on Microsoft’s own email gateway servers, not on your PC. Microsoft’s final report, dated November 20, says no business email was lost and it was not a cyberattack. One group did lose mail: some messages to personal mailboxes unused for 30+ days bounced. Below is what failed, who was affected, and the three things worth doing now.

What we know

  • Microsoft has published its final post-incident report for the Microsoft 365 outage, under incident IDs EX1550543 and MO1550821. GeekWire was first to report on the final version on November 21.
  • The outage started at 11:20 a.m. Eastern on Thursday, November 12. Microsoft says customers stopped seeing active problems at 11:10 a.m. Eastern the next day, and it closed the incident late on November 13.
  • The cause was a defect that had been live since July. It only broke things when three ordinary conditions hit at once.
  • Microsoft says it found no malicious activity and that the faulty change “was not caused by AI tooling.”
  • It lists 13 follow-up fixes, some due by the end of 2026 and others by the end of March 2027.

What we don’t know yet

  • What the July update was originally meant to fix. The report does not say.
  • How many messages bounced, or how many people were affected in total.
  • Whether business customers will get service credits. The report does not mention compensation.
  • Delivery dates for several of the fixes, which the report lists as “TBD.”

Why Was Outlook Down on November 12?

Every connection to Exchange Online mailboxes, the ones behind Outlook for work and school accounts, passes through what Microsoft calls its network gateway: a large fleet of servers that acts as the front door to Exchange Online and other Microsoft 365 services. In July, Microsoft turned on a Windows update on those gateway servers that changed how they handle incoming connections.

That update carried a bug. Under heavy load, parts of the connection process got stuck waiting on each other until a server ran out of processing power and memory and stopped responding. The newer servers, which have more processor cores and take on more work at once, were hit hardest. Microsoft’s load tests ran mostly on older hardware with fewer cores, so the bug slipped through and ran quietly for more than three months.

The three conditions that set it off

  1. Less capacity than usual. Close to 14% of the gateway servers were out of service for routine maintenance. Microsoft normally keeps enough spare capacity for that.
  2. Extra traffic from Teams. At 8:07 p.m. Eastern on November 11, a routing problem in Microsoft’s US East region made Teams switch automatically to the gateway that Exchange Online also uses. All Teams traffic worldwide moved over.
  3. The US workday. As North American traffic climbed toward its daily peak, broad failures began around 11 a.m. Eastern.

Microsoft says any one of these, or even all three together, would normally be routine. With the July bug in place, they were enough to tip servers over.

How One Bug Took Down Outlook Worldwide

When a server stops responding, Microsoft’s systems move its users to healthy servers nearby. Usually that keeps the service up. This time the healthy servers had the same bug, so the extra load knocked them over too. At the worst point, more than 80% of the gateway servers in North America were unresponsive.

Once a region runs low on healthy servers, traffic is sent to other regions. That spread the failure further, and within about two hours of the first broad failures, servers in every region were affected.

Recovery was slow for three reasons. Servers that came back online were swamped by waiting traffic and froze again. Because the faulty change was months old, the usual “undo the latest change” tools could not quickly reverse it. And every one of the affected servers had to be taken out of service, restarted, patched, restarted again and returned, region by region.

Who Was Affected by the Microsoft 365 Outage?

According to the report, most users could not open their mailboxes in Outlook, Outlook on the web, or Outlook for iPhone and Android, and email delivery was delayed for most users. The damage spread to anything that depends on Exchange Online:

  • Teams, OneDrive and SharePoint moved to a second, separate gateway early on and recovered sooner. Calendar, search and people features in Teams could still fail because they pull data from Exchange.
  • Microsoft 365 Copilot apps mostly would not load, and most prompts failed or timed out.
  • Planner, To Do, Power BI and Universal Print could fail where they rely on Exchange data, and Universal Print users may have been unable to create or retrieve print jobs.
  • IT admins may have had trouble reaching the Microsoft 365 admin center and some security tools.

Why did Teams come back first? Microsoft runs two independent gateways. Teams and the file services could switch to the second one. Exchange Online could not, so email stayed down longest.

One thing this outage was not: a problem with Windows on your own computer. Microsoft says neither the bug nor the update applies to normal Windows installations. If your PC has trouble after this month’s patch, that’s a separate issue, covered in our guide to Windows 11 November update problems.

Was Any Email Lost?

For work and school accounts, Microsoft says no. To stop delayed mail bouncing during the outage, it doubled the time Exchange Online keeps retrying delivery, from 24 to 48 hours, before sending back a failure notice. It says all queued messages were delivered and it found no business messages that were permanently lost.

There is one exception. Some delayed messages to personal mailboxes that had been inactive for more than 30 days expired instead of being delivered, and the people who sent them got a bounce message. If you sent something important on November 12 or 13 and later got a “delivery failed” email, that message never arrived.

What to Do Now

  1. Look for bounce messages from November 12–14. Search your inbox for “Undeliverable” or “Delivery has failed.” Microsoft calls these non-delivery reports. Resend only the messages that bounced; anything that did not bounce should have arrived.
  2. Chase replies you are still waiting for. Invoices, contracts and time-limited codes sent during the outage may have landed hours late and been missed. A short “did this reach you?” saves guesswork.
  3. Be wary of “outage” emails. Scammers used the outage as bait with fake notices about lost or held mail. Our guide to fake Microsoft 365 outage phishing emails shows what they look like.

How to Check If Outlook Is Down Next Time

  • Public status page: Microsoft’s service status page lists known Microsoft 365 issues, and Microsoft points people to it when they can’t sign in to their admin center.
  • Admin center: If you manage a work or school account, Microsoft’s service health guide explains where to find live incidents in the Microsoft 365 admin center. People with the Service Support admin or Helpdesk admin role can view it too. Microsoft also posts updates on X at @MSFT365status.
  • Rule out your own setup: If Outlook on the web works but the app doesn’t, the problem is more likely on your device than at Microsoft.

For a personal Gmail problem that looks similar, see why Gmail is not receiving emails.

What Microsoft Says It Will Change

The report lists 13 fixes. These are the ones that matter most for everyday users:

Fix Due
Stop a failure in one region from spreading to others End of 2026
Teams fails over only in the affected region, not worldwide End of 2026
Spot long capacity shortfalls before they become risky End of 2026
Faster first notice to customers (it took about 20 minutes this time) End of 2026
Split gateway servers into separate pools so Teams traffic can’t swamp email End of March 2027
Load testing on the newest, highest-core servers with real-world traffic End of March 2027
More spare server capacity End of March 2027
Ease traffic back gradually when servers rejoin No date yet

The final report also corrects the preliminary one, which BleepingComputer covered on November 16. That version blamed the missing 14% of capacity on an unrelated problem. The final version says it was routine maintenance.

Was It Connected to the Other Outages That Week?

Microsoft’s outage was the first in a rough week that also saw problems at US banks on November 16 and the Apple outage of November 17. Each company has blamed its own internal software, and none has reported evidence of a link or an attack. Microsoft’s report puts its outage down to its own bug and its own safety systems.

Quick Answers

Why was Outlook down on November 12, 2026? A Windows update that Microsoft ran only on its email gateway servers had a hidden bug. Reduced capacity, extra Teams traffic and the US morning peak triggered it, and Microsoft’s automatic rerouting spread the failure worldwide.

How long did the Outlook outage last? Close to 24 hours, from 11:20 a.m. Eastern on November 12 to about 11:10 a.m. Eastern on November 13. Delayed mail kept arriving after that.

Was the Microsoft 365 outage a hack? No. Microsoft’s final report says it found no evidence of malicious activity, and the faulty change was not made by AI tools.

Did I lose any emails? Microsoft says no business email was permanently lost. Some delayed messages to personal mailboxes that had been inactive for over 30 days bounced, and their senders got a non-delivery report.

Do I need to resend emails from November 12? Only the ones that came back as undeliverable. Messages that did not bounce were delivered, even if late.

Does the bug affect Windows on my PC? No. Microsoft says the defect and the update were specific to its Microsoft 365 gateway servers and do not apply to standard Windows installations.

Fakhrul Alam

Editor, Mobiles Tech Land

Fakhrul Alam is the founder and editor of Mobiles Tech Land, which he started in 2013. He is passionate about technology and loves everything from smartphones and laptops to smart TVs, streaming sticks and the AI features built into them. He loves sharing what he knows publicly, so others can solve their tech problems and get more out of their devices. Every guide links to the official source it is based on.

Keep reading