What do we actually know about the global Microsoft outage?

Millions locked out, 74 countries, and a cause that boils down to "a lot of servers went missing".

Let's get the facts straight first, because the internet is already writing its own chapters. Thursday 12 November, around 16:00 GMT, people start reporting they can't open Outlook. Within about an hour, the outage tracker Downdetector has reports from 74 countries and territories. Not a region. Seventy-four.

And it wasn't only email. Teams, SharePoint and Copilot all went wobbly, and so did Defender XDR, Microsoft's own security system. At the peak, more than 120,000 people in the US alone were reporting Outlook problems. For scale, Microsoft 365 apps have around 430 million users worldwide, though the company hasn't said how many were hit. Germany's national railway reported severe sluggishness with its email, and the US House of Representatives said its users were affected too.

So what's the explanation?

First Microsoft talked about "elevated load". Then it corrected itself: not a surge in traffic, but a large number of servers that unexpectedly became unavailable after failing automated health checks, which put strain on everything left standing. The company redistributed traffic, tested configuration changes, and at one point admitted its actions so far hadn't given the relief it expected. Early Friday, more than 12 hours in, it was reporting "marginal success".

And here is the question that practically asks itself: servers don't just decide to vanish. Why did a big chunk of them fail those checks at the same moment, across multiple regions?

Honestly? Nobody has said. We know the symptoms, we don't know the cause. That answer usually arrives in a post-incident report, sometimes weeks later. Until then, the cleanest summary is also the least satisfying one: huge outage, no root cause yet.