ZDNet AI ↗ · 2026-11-14 05:43 · UTC+8
微软将重大故障归咎于7月的更新缺陷及其他两个因素
媒体报道 ZDNet AI 原文语言:英文
微软将近期导致全球大面积中断的故障归因于7月更新中的潜在缺陷,并叠加了流量激增和服务器容量不足等因素。此次故障影响了Outlook、Copilot和Teams等服务,估计造成至少7亿美元损失。
全文
Microsoft blames major outage on a July update defect – and two other factors
A surprise defect took more than 80% of Microsoft's servers out at the outage's peak. Here's what happened.
Radhika Rajkumar
Senior Editor
Radhika Rajkumar is a senior editor at ZDNET based in New York City.… Read full bio
Radhika Rajkumar
Senior Editor
Read full bio
November 16, 2026, 11:57 am ET
4 min read
In this illustration photo a Microsoft Outlook and Teams logo are seen on a cellphone in Tokyo on November 13, 2026. Microsoft said on November 12, 2026 that efforts to repair a major outage of Outlook were not going as expected and the firm was seeking alternative solutions as users around the world were left without its crucial services. (Photo by ANDREW CABALLERO-REYNOLDS / AFP via Getty Images) ANDREW CABALLERO-REYNOLDS / AFP via Getty Images
ZDNET’s key takeaways
Microsoft has an explanation for last week’s outage affecting Outlook, Copilot, and Teams.
Peak traffic and low capacity revealed a dormant defect from a July update.
The outage is estimated to have cost at least $7 billion.
Microsoft has released new information explaining the massive outage that started Thursday morning and affected Microsoft 365, Copilot, and Outlook access in 74 countries, according to Downdetector.
What caused the outage
“A latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable,” Lamanna said, noting that the update was deployed safely worldwide without any issues for over three months.
More from ZDNET
He said Microsoft didn’t find the issue in testing due to “the different traffic and SKU mix used in our test labs,” because “our load testing tended to focus on our weaker hardware SKUs with fewer cores.”
Also: Microsoft fixes over 1,000 Windows flaws – and one is being exploited
Two other factors made matters worse, and left servers useless in less than two hours.
“A surge in load increased the likelihood for the networking gateways to encounter the contention,” Lamanna said, explaining that Microsoft 365 maintains two gateway systems. Before the outage started, Teams failed from one to the other, which “changed its traffic patterns.” Simultaneously, he added, “nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day.”
Those two conditions collided and “caused the network gateway to encounter the latent bug from July,” Lamanna concluded. Requests eventually overloaded servers, at which point they stopped responding. At the outage’s low point, over 80% of its servers weren’t responding.
“When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints,” Lamanna said. “However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers.”
Also: AI finds zero-day flaws for just $4 now – even mediocre hackers can cash in
Before Microsoft issued an explanation, some suspected the outage may have been the result of a cyberattack, which both Lamanna and Microsoft’s status account denied.
Where this leaves Microsoft
It’s unclear how many people the outage affected, though Microsoft’s own numbers from January say Microsoft 365 “exceeds 450 million commercial paid seats,” illustrating the scale of the issue. Microsoft deployed an update to fix the outage and gradually applied it to groups of servers. Lamanna said Microsoft would publish a full post-incident review with more details later this week.
Service might be restored, but customers aren’t happy about having lost nearly two full workdays. One think tank told CNN it estimated the outage — which lasted through close of business on Friday for some — resulted in $7 billion in losses, due to many businesses and organizations being unable to access their everyday systems.
Also: If the November Windows update fails to install on your PC, here’s what to do
The fact that Microsoft’s testing couldn’t find the July issue ahead of time may leave customers wondering when the next dormant defect will strike, and whether the company is prepared.
Organizations across Europe have been leaving Microsoft in recent years, opting instead for locally-controlled, open-source alternatives. The former CEO of Github launched a decentralized alternative called Entire earlier this year, citing developers’ need for something more reliable, as Github has similarly been plagued with outages.
Why was Teams least affected?
For many, Teams was barely offline over the two-day period, or was the first service to come back online.
“Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage,” Lamanna explained. Other services like Exchange Online can’t fail out.
He added that fixing the outage was slow because waiting traffic hit servers as soon as they came back, rendering them unresponsive just as quickly.
“Our normally automated recovery processes were not designed to restore service from this broad unresponsive state,” Lamanna said. “Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.”
When the outage started
On Thursday morning, people began reporting issues with Outlook, Teams, and Copilot, according to Downdetector. By 1 p.m. ET, the number of reported Outlook outages was nearly 83,000 but had fallen to just under 75,000 by 2:38 p.m. ET. Teams and Copilot reports started dropping significantly by Thursday evening, but many individuals were still reporting issues accessing systems well into Friday morning on X and Reddit. Even Microsoft’s status page was down until around 3 p.m. ET Thursday.
Also: If the November Windows update fails to install on your PC, here’s what to do
As late as Friday afternoon, the company didn’t yet have an ETA of when the outage would be fully solved.
Community Guidelines
Please accept cookies to view the comments powered by Disqus.
Radhika Rajkumar
Senior Editor
Radhika Rajkumar is a senior editor at ZDNET based in New York City. She covers AI, specializing in safety, privacy and security, policy, education, and synthetic media. She also leads ZDNET's newsletter strategy. Radhika holds a Masters in Creative Publishing and Critical Journalism from The New School. See full bio
The Latest from Radhika
You can use Google’s Spark AI agent, renamed Tasks, for free now – with limits
Microsoft’s new Licensed Weights lets businesses customize AI models with their own data
Microsoft unveiled Copilot Workspaces at Ignite 2026, plus more AI workplace updates
/ latest
Best early Black Friday Apple deals: MacBooks, AirPods, and more
Google Wallet comes to your iPhone – but without this feature
5 new AI features in iOS 27.3’s Health app – which iPhones can try them
Free Pixel Watch 5 and Buds 2A with Pixel 11 Pro XL for Verizon’s Black Friday sale – how to qualify
正文以来源语言显示。