

If your organization runs on Microsoft Outlook, you probably spent last Thursday fielding the same question: “Is email down for everyone, or just us?” It was down across much of the world. Within an hour, outage reports had come in from 74 countries and territories. Microsoft has since published a preliminary account of what went wrong, and it’s a useful case study in how large failures come together.
On Thursday, November 12, the networking gateway that handles traffic for many Microsoft 365 services began to fail. Exchange Online, the cloud email service behind Outlook, took the hardest hit, though other services were disrupted too. Microsoft’s monitoring flagged rising connectivity problems at 11:03 a.m. ET, and the first customer support case arrived 30 minutes later.
Microsoft’s preliminary post-incident report, released November 15 and summarized publicly by executive Charles Lamanna, attributes the outage to three factors:
As U.S. traffic peaked on November 12, the three factors came together. Requests piled up until servers stopped responding, so traffic was rerouted to the healthy ones. Those servers then hit the same defect and failed too. The mechanism meant to route around failure ended up spreading it. In less than two hours, the failure had moved across Microsoft’s gateway fleet, and at its worst, more than 80% of the gateway servers were unresponsive.

Any organization that relies on Microsoft 365 could have been affected, no matter how healthy its own network was. But the impact varied by service. Services that could fail out of the gateway did, which is why Teams, OneDrive, SharePoint, and Office apps recovered sooner. Exchange Online couldn’t. According to Microsoft’s report, it can’t fail out of that gateway “for scale reasons.” As a result, Outlook stayed down long after other services came back.
The public sector felt it too. Governments around the world put contingency measures in place, and US city governments reported services returning on Friday after a day of disruption.
Yes, but recovery was slow. Servers brought back online were immediately overwhelmed by waiting traffic and went unresponsive again. Microsoft’s report says its automated recovery processes weren’t designed to handle a failure that broad. Engineers ultimately built an update that returned the affected code to its previous known-good state, then applied it to groups of servers.
Microsoft reported healthy service at 11:10 a.m. ET on November 13, roughly 24 hours after its monitoring first flagged the problem. It issued its final customer update that night. A final post-incident report is due November 20.
When something breaks, the first question is usually “what changed?” Microsoft asked it too, pausing all ongoing and planned deployments and configuration changes while it investigated.
According to the preliminary report, though, the defect shipped in July. The triggers that week weren’t deployments. They were conditions: a failover that added load, and capacity that was already partly out of service. Neither caused problems alone. Together, they exposed a defect that had run without impact for months.
So “what changed?” was still the right question. The answer just wasn’t a recent deployment. It was a shift in where traffic flowed, onto infrastructure already short on capacity. A review of recent deployments wouldn’t have surfaced that.
Microsoft’s own explanation evolved as the picture came together. Early on, it pointed to a traffic surge and a problem with a component that processes server health. By Friday, it had linked the incident to an earlier upgrade and a more recent network change. The preliminary report then laid out all three factors.
That’s not a knock on Microsoft’s engineers. Symptoms surface first and causes later. When the cause is months old, the obvious places to look can point the wrong way.
For network teams, the more useful set of questions are about how your network behaves when conditions shift. What happens when one service fails over onto infrastructure another service depends on? Which services can’t fail over at all? How much headroom remains when part of your capacity is already out?
Yes, including twice since late 2025 at hyperscale.
These incidents involved different companies and different systems, but they share a shape. A routine change or event met a weakness no one had tested for, and the effects spread well beyond where it started.
Change is a common thread in major outages more broadly. In Uptime Institute’s 2026 annual outage analysis, configuration and change management failure was the most commonly cited root cause of major network-related outages, cited by 41% of survey respondents.
None of this was yours to cause or fix. If your users told you before Microsoft did, you likely spent the first stretch ruling out your own network. At points, Microsoft pointed admins to its public status page in case the admin center itself was unavailable.
Now that service is restored, consider these steps:
Leadership may also be asking, “Could this happen to us?” It’s a fair question. Start by defining the minimum service your organization needs if a major provider goes down for a day. Then look at your own network:
No one outside Microsoft can verify Microsoft’s network. But the way this failure spread has direct parallels in enterprise networks. A failover pushed traffic onto shared infrastructure, and one service was left with nowhere to go. Three practices help:
A network digital twin is built to answer these questions. Forward Enterprise uses a mathematically accurate digital twin of your hybrid network to trace paths end to end, compare network behavior between any two points in time, whether days, weeks, or months apart, and verify that failover paths exist and behave as designed. The answers come from the network’s real configuration and state, not from diagrams or memory.
Uptime Institute’s research notes that outages are increasingly caused by interactions between systems rather than single faults, which makes root causes harder to pin down. This outage is close to a textbook case. A months-old defect, a failover that added load, and capacity already out of service each caused no impact on their own. Together, they disrupted email for organizations around the world.
Networks will keep changing, and failovers and maintenance windows are part of running them well. The goal isn’t to avoid them. It’s knowing, before the next one, what shares a path, what can’t fail over, and how traffic actually moves when conditions shift. For network teams, that’s a visibility problem first: seeing how your network actually behaves, not just how it was designed.
For a closer look at what that visibility requires, read The Network Digital Twin Guide.