Outlook outage lasted nearly 24 hours and hit 70-plus countries
A July bug, failed containment walls and 'thundering herds' took down Outlook for 70-plus countries. Microsoft's final repair report is due Nov. 20.

Nathan Brooks
· 4 min read
By Nathan Brooks
Email stopped for organizations in more than 70 countries last week, and Microsoft now says a software bug that had been running in production since July caused it. More than 80% of the servers in the company's Microsoft 365 networking gateway stopped responding at the height of the failure, according to Microsoft's preliminary report, released overnight.
Active disruptions lasted nearly 24 hours. Delayed email kept arriving after service returned Friday morning, and Microsoft posted its public all-clear on X late Friday night, nearly 38 hours after the outage began.
For employers, the episode is a reminder of how much people-process continuity now rests on a single vendor's infrastructure. Recruitment pipelines, payroll approvals, benefits enrollment and everyday manager communication all move through email. When the gateway in front of Outlook froze, those processes froze with it.
What actually went wrong?
The root flaw dates to July, when Microsoft began rolling out a fix to the software that handles incoming connections on its networking gateway, the layer of servers that sits in front of Outlook and many other Microsoft 365 services. Microsoft has not said what that fix was meant to address. It ran worldwide for more than three months without problems.
Under heavy load, parts of the software could get stuck waiting on one another, consuming servers' processing power and memory until they froze. About 15 hours before the outage, Microsoft's systems automatically moved Teams traffic onto the same servers that handle Outlook email, adding to their load. Microsoft called the switch part of normal operations but did not say what prompted it. Nearly 14% of the gateway's server capacity was already out of service because of an unrelated, unexplained problem. When traffic peaked during the U.S. workday, that combination was enough to trigger the outage.
Microsoft's own safety systems then made things worse. Automated systems shifted traffic from unresponsive servers onto healthy ones, where the extra load triggered the same bug. That is the cascading failure the report describes. Recovery hit a second wall: restarted servers were immediately overwhelmed by waiting traffic, a phenomenon engineers call a "thundering herd." About 10 hours in, engineers turned off some of the automatic rerouting.
Why didn't testing or safeguards catch it?
Microsoft's labs mostly ran on less powerful machines with fewer processing cores and a different traffic mix, while the problem was worst on newer servers handling real customer load. The fix also passed through Microsoft's standard staged rollout, spreading worldwide over several weeks without any sign of trouble. The company spent $45.2 billion on capital expenditures in its most recent quarter, much of it on AI infrastructure, so the means to test on production-grade hardware exist.
The containment walls did not hold either. The gateway consists of thousands of "capacity units" grouped into regions, with barriers meant to keep a failure in one place, and Microsoft runs a second, independent gateway so services can switch over during a disruption. Teams, OneDrive, SharePoint and Office apps made that switch, which is why Teams chats and meetings mostly kept working. Exchange could not, "for scale reasons," as the company put it, so email stayed down. The walls between regions failed because of what the report calls "a separate issue," which it does not explain, so the outage went global.
Microsoft's automated recovery "was not designed" for a fleet that was almost entirely unresponsive, according to the report, and its usual rollback procedures could not quickly undo a change that was months old.
What has Microsoft promised next?
Charles Lamanna, Microsoft's executive vice president of Copilot, Agents and Platform, posted an abridged version of the report on X late Sunday. "We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations," he wrote. He had previewed the findings Friday afternoon, blaming "cascading failures + thundering herds at our network perimeter" for the slow recovery.
Microsoft says it has rolled back the defective code, added server capacity and monitoring, and placed new limits on how traffic is redistributed to avoid another cascade. A final report with a full list of repairs is due Nov. 20. It may also answer the biggest open question: why the walls between regions failed to stop a regional problem from becoming a global one. Until then, HR teams that lost a working day to the outage have a case for dusting off their own continuity plans.
Source: geekwire.com
More from Nathan Brooks
Show full bio
News editor covering people, launches and day-to-day practice in Recruiting and talent acquisition, learning and development at HR Briefing.
257 articles