- India's horticulture output estimated to rise 4.36 pc to record 3,869 lakh tonnes in 2025-26
- Suriya’s Scene Crosses ₹260 Crores Worldwide In Just 10 Days
- INS Sahyadri and Japan's JS Ise participate in maritime exercise
- OpenAI Rolls Out New AI Tools to Detect CSAM on ChatGPT
- Chennai corporation plans upgrade of 753 roads, seeks consultants for quality checks
- 184 women incorrectly declared dead in govt records denied Gruha Lakshmi benefits, claims Karnataka BJP
- JPMorgan Chase Software Bug Disrupts Banking Services Across US
- Gold and Silver rates today, 17 Nov, 2026 in Hyderabad, Visakhapatnam, check gold prices of 18K, 22K, 24K
Microsoft reveals cause of massive Outlook outage, traces bug back to July
In Short
Microsoft has identified a dormant software bug, increased Teams traffic and server maintenance as key factors behind its 36-hour global outage.

Microsoft reveals cause of massive Outlook outage
Microsoft has finally shared what caused Outlook and several other Microsoft 365 services to stop working this week. The company said the issue came from a software bug that had been hiding since July 2026. This bug was not caught until the problem showed up. At the time there was a sudden spike, in network traffic. On top of that server capacity had dropped. All of these factors together brought the services to a standstill.
The outage affected millions of users all over the world keeping Outlook, Exchange Online, Teams and other Microsoft 365 applications from working for more, than 36 hours. Many businesses, schools and government offices were. Those users could not open emails or use the essential tools that help them work.
On November 15 Microsoft shared a report about an incident. The report described what happened that caused problems. Charles Lamanna, who is an Executive Vice President at Microsoft talked about the issue on X. Microsoft said sorry, to customers who were affected.
A software bug that went unnoticed for months
Microsoft said the problem was not because of a cyberattack. Instead, it came from an update they sent out for their networking gateway servers in July. The update caused the issue. They are looking into it to fix things.
The update first looked good. Microsoft testing did not catch a problem that surfaced when the same software ran on newer servers, with more processor cores. The update was then found to fail under those conditions.
Under workloads the software had a technical problem called lock contention. This created a struggle, for system resources making the CPU and memory usage go up. The servers that were affected stopped working.
How three issues triggered a global outage
The dormant bug stayed hidden for months. Then on November 12 two more problems came along. Put extra strain on Microsoft’s network.
Fifteen hours before the outage Microsoft Teams traffic was sent to the primary network gateway that also handles Exchange Online. This put pressure on the servers.
At the time almost 14 percent of the gateway’s capacity could not be used because of maintenance work that happened the day before.
Although neither situation was supposed to cause an outage, on its own putting them together made the servers go past their limits. This made a hidden software bug appear.
Why the disruption spread so quickly
As servers started to crash Microsoft’s automated traffic management system tried to send users to machines that were still working. The extra load pushed those servers past their limit. More failures followed.
The problem spread beyond where it started because the systems meant to stop it from spreading didn’t work. In two hours, over 80 percent of Microsoft’s gateway servers stopped working. It was a wide impact.
Why Outlook took longer to recover
Microsoft was able to bring Teams, OneDrive, SharePoint and Office up fairly fast by sending traffic to backup systems. I saw how Microsoft could not fix Outlook quickly because Exchange Online was too large to shift to a network.
The recovery was further complicated by recurring server failures, triggered by a surge in traffic each time engineers restarted the affected machines.
Ultimately Microsoft created a fix to undo the bad July update. Engineers sent it to groups of servers in steps. Then slowly brought everything back, to normal.
The company confirmed that, by November 14, services were functioning normally. Microsoft is expected to publish its final report on the incident on November 20.

