Guides / Dispatches
Dispatch3 min read

Why the Microsoft Outlook outage took 24 hours to fix

Servers that came back were knocked over again by the backlog. Grid operators know this problem well.

The Blackstart Supply power mark on a dark background
The short version
  • Microsoft’s Outlook outage lasted about 24 hours, from 11:17 a.m. Eastern on November 12, 2026 to 11:10 a.m. on November 13, by the company’s own times.
  • Microsoft blamed an earlier network capacity upgrade and ruled out an attack. Its promised full report had not appeared by November 16.
  • Servers brought back online failed again under the backlog, so service had to be restored in stages, the way a power grid is.

Microsoft’s Outlook email was down for almost exactly a day. By the company’s own clock the outage ran from 11:17 a.m. Eastern on Thursday, November 12 to 11:10 a.m. on Friday, and Microsoft didn’t declare the incident closed until late Friday night.

The failure took minutes. What I want to look at is why the fix took 24 hours, because the reason is the same one that keeps a dead power grid from being switched straight back on.

What Microsoft says went wrong

Microsoft’s statement on Friday blamed “an issue during an earlier network capacity upgrade that surfaced following a recent network change.” It said the problem was technical and “not related to cyber or AI / agents.” It also said it was “deeply sorry.”

That’s all the company has said about the cause. It promised a full report, and as I write this on November 16 I can’t find one on its own pages. One trade site says a preliminary report points to a Windows bug on gateway servers. I couldn’t confirm that, so I’m not treating it as fact.

Why it took a day

The more useful record is the string of status updates Microsoft posted while it was happening. An admin-focused site kept a log of them, and they read like a restart that kept failing. (I’ve converted its times to Eastern.)

At 1:19 p.m. on Thursday, Microsoft reported that its servers were under elevated load, and an hour later it said the load wasn’t coming from extra traffic. At 2:43 p.m. the overloaded servers failed their own health checks and were pulled out of service. By 5 p.m. the company said its fixes hadn’t brought the relief it expected.

Then came the part I keep coming back to. Engineers put servers back, and around 7 p.m. those servers went unresponsive again as soon as traffic reached them. Every one that returned met hours of waiting connections and fell over.

So Microsoft changed its approach. It began limiting traffic in some locations and restarting equipment in stages, and by 8:50 p.m. it reported “positive results.” Recovery reached parts of Asia Pacific at 6:04 a.m. Friday. Europe and North America improved over the next few hours.

Grid operators would recognize all of this. After a blackout they add customers back a block at a time, because a generator handed too much load at once shuts itself off again. I went through that in what a black start is. Microsoft ended up doing the same thing with email: limit the load, bring back a piece, let it settle, bring back the next.

Big systems are built to run. Very few are built to start.

What it looked like outside Microsoft

More than 7.4 million problem reports were logged worldwide, according to ABC News in Australia, which drew on Reuters and AFP. In Britain, a GMB union official said NHS staff taking emergency calls were “unable to refer patient details in the normal way.” Immigration New Zealand stopped processing visa applications. Some companies couldn’t publish their earnings.

None of those organizations made a mistake on Thursday. Each had put one supplier underneath a job that couldn’t wait.

What I’d take from it

Ask one question of anything you depend on: if this went down for a day, what’s my other way? For email the answer can be as small as a second account with a different provider and a printed list of the ten phone numbers you’d need.

For a household it’s the same question asked about maps, medical references and how you’d reach each other. That’s why the kit we sell keeps all of it on the device, and why the setup guide is free. Restarting is the hardest thing a big system does, so plan for it to be slow.

Questions people ask

How long was Microsoft Outlook down in November 2026?

About 24 hours. Microsoft put the start at 11:17 a.m. Eastern on November 12, 2026 and the end at 11:10 a.m. on November 13. It declared the incident fully remediated late that night.

What caused the Microsoft 365 outage?

Microsoft said it was caused by an issue during an earlier network capacity upgrade that surfaced after a more recent network change. It said the outage was not related to a cyberattack or to AI agents. A full report was promised.

Was any email lost in the Outlook outage?

Microsoft’s updates describe delayed mail held in queues, which it said were significantly reduced by the morning of November 13. Check with your own administrator if a message you expected never arrived.

Sources

  1. ABC News (Australia), with AFP and Reuters, Microsoft ‘deeply sorry’ for outage as it restores its service, November 14, 2026.
  2. azureblog.co.uk, Microsoft 365 outage, 12 November 2026: what happened and what admins can do, November 14, 2026.
  3. NBC News, Microsoft outage: Outlook and Teams updates, November 13, 2026.

This post was drafted with AI assistance from the sources listed above and checked against them. If you spot an error, tell us.

Keep reading /

More from the guides

All guides
Be ready

Get your household ready before the next headline.