JupiteX Get the app
Science & Technology17 Nov 2026 · about 6 min

Microsoft says months-old bug caused global Microsoft 365 outage

The brief

More than 80% of Microsoft’s networking gateway servers became unresponsive at the outage’s worst point, disrupting Microsoft 365 around the world. The incident affected Outlook, Exchange Online, Teams, and Copilot, and lasted nearly 24 hours. Users could not access email, and message delivery was significantly delayed. The outage began at 11:20 AM ET on November 12. Microsoft said a software bug, more traffic after a Teams failover, and reduced server capacity combined to overwhelm the gateways. The report describes Teams moving to infrastructure used by Exchange Online about 15 hours before the outage. Other services could switch to alternative infrastructure and recover earlier, but Exchange Online could not make the same switch. Microsoft confirmed that active customer impact ended at 11:10 AM ET the following day. Engineers fixed the bug and deployed the fix across affected servers. Microsoft has since increased capacity, improved monitoring, and added safeguards against similar cascading failures. Its investigation is continuing, with a final report expected later that week.

01

Which Microsoft 365 services were disrupted, and how long did the outage last?

More than 80% of Microsoft’s networking gateway servers became unresponsive at the outage’s worst point, disrupting Microsoft 365 around the world. The incident affected Outlook, Exchange Online, Teams, and Copilot, and lasted nearly 24 hours. Users could not access email, and message delivery was significantly delayed.

The outage began at 11:20 AM ET on November 12. Microsoft said a software bug, more traffic after a Teams failover, and reduced server capacity combined to overwhelm the gateways. The report describes Teams moving to infrastructure used by Exchange Online about 15 hours before the outage. Other services could switch to alternative infrastructure and recover earlier, but Exchange Online could not make the same switch.

Microsoft confirmed that active customer impact ended at 11:10 AM ET the following day. Engineers fixed the bug and deployed the fix across affected servers. Microsoft has since increased capacity, improved monitoring, and added safeguards against similar cascading failures. Its investigation is continuing, with a final report expected later that week.

02

What combination of the software bug, increased traffic, and reduced capacity triggered the failure?

The failure needed three conditions to collide: a latent software bug, increased traffic, and reduced server capacity. Microsoft said the bug, introduced in a July update, could overwhelm gateway servers under certain traffic conditions. It had gone undetected for more than three months because testing did not expose it.

About 15 hours before the outage, Teams automatically switched to networking infrastructure used by Exchange Online, increasing traffic there. At the same time, nearly 14% of gateway capacity was offline for an unrelated reason. Microsoft said the infrastructure could handle that capacity reduction by itself, but the combination of extra traffic and reduced capacity triggered the bug. Servers stopped responding, and redirected traffic burdened others.

The failure spread rapidly: at its lowest point, more than 80% of servers were unresponsive. Microsoft deployed a fix across affected servers, then increased capacity, improved monitoring, and added safeguards. Its investigation is continuing, and the final post-incident report was expected later that week. The report also said regional safeguards failed to contain the cascade.

03

How widespread was the failure at its worst?

The failure became widespread quickly. Microsoft said the previously unknown software defect was encountered across its fleet in less than two hours. At the outage’s lowest point, more than 80% of the networking gateway servers were unresponsive. The disruption affected Microsoft 365 services worldwide and continued for nearly 24 hours.

The bug was triggered when increased traffic followed a Teams failover to infrastructure used by Exchange Online, while nearly 14% of gateway capacity was already offline. As servers stopped responding, Microsoft redirected users to available servers. Those servers became overwhelmed by the added traffic and failed as well. Safeguards intended to keep problems from spreading between regions did not contain the cascade.

The impact was not identical across services. Teams, OneDrive, and SharePoint could switch to alternative infrastructure and recover earlier, while Exchange Online could not make the same switch. Microsoft’s engineers developed and deployed a fix, and the company said active customer impact ended at 11:10 AM ET on November 13. It has since added capacity and safeguards.

04

What happened to customers when the gateway servers stopped responding?

Gateway servers failing meant customers could not reliably reach Microsoft 365 services. The outage affected Outlook, Exchange Online, Teams, and Copilot worldwide. Users were unable to access their email, and messages were delivered with significant delays. The disruption lasted nearly 24 hours, with active customer impact ending on November 13.

Microsoft said its systems redirected users from unresponsive servers to other available ones. But those servers then faced extra traffic and also became overwhelmed. The failure spread across the fleet, leaving more than 80% of gateway servers unresponsive at the worst point. Exchange Online could not switch to alternative infrastructure in the way that Teams, OneDrive, and SharePoint could.

Recovery was also difficult because restarting affected servers caused them to be quickly overwhelmed again by backed-up traffic. After identifying the software bug, Microsoft engineers developed a fix and deployed it across affected servers. Microsoft confirmed that services were fully restored at 11:10 AM ET on November 13. It has since increased capacity, improved monitoring, and added safeguards.

05

What is a networking gateway server, and how does it help connect users to online services?

In general, a networking gateway server acts as an entry point that helps route network requests between users and online services. It can connect incoming requests with the infrastructure that provides the requested service. The article calls the affected machines Microsoft 365 networking gateway servers, but does not provide a detailed technical description of their design.

The report does explain what happened when these gateways failed. As servers stopped responding, Microsoft’s systems redirected users to other available servers. Those servers received additional traffic and became overwhelmed as well. At the worst point, more than 80% of the gateway servers were unresponsive, disrupting Microsoft 365 services worldwide.

The gateways mattered because their failure affected access to services such as Outlook, Exchange Online, Teams, and Copilot. Microsoft said Exchange Online could not switch to alternative infrastructure, while other services could and recovered earlier. After the incident, Microsoft said it increased capacity, improved monitoring, and added safeguards to reduce the risk of traffic redirection triggering another cascading failure.

06

How can redirecting users from failed servers overload the servers that are still working?

Redirecting users helps keep a service available when some servers stop responding. But it also concentrates requests on the servers that remain online. If those servers have little spare capacity, extra traffic can overwhelm them, causing more failures and further redirection. That creates a cascade rather than containing the original problem.

Microsoft described that exact pattern during the outage. As gateway servers stopped responding, its systems sent users to other available servers. Those servers were also overwhelmed by the additional traffic and failed. In less than two hours, the defect had affected the fleet, and more than 80% of servers were unresponsive at the lowest point. Safeguards designed to prevent problems spreading between regions did not contain the cascade.

Recovery was difficult because restarting affected servers quickly exposed them to backed-up traffic and overwhelmed them again. Microsoft eventually deployed a software fix across affected servers. It says it has since increased capacity, improved monitoring, and added safeguards so traffic redirection is less likely to trigger similar failures.

07

Why can software load tests miss bugs that appear on real-world servers under different traffic conditions?

Load tests try to reveal problems by putting software under simulated traffic before it reaches production. But a test can miss a bug if its hardware or traffic does not match real-world conditions. Microsoft said its testing did not expose the defect in a July update for its networking gateway servers, even though the update had been deployed for more than three months.

The company said the issue was worsened on machines with more cores and newer hardware. Its lab testing tended to use weaker machines with fewer cores, and the traffic mix and server configurations, or SKUs, differed from production. Under certain traffic conditions, the bug could overwhelm servers and make them stop responding. The failure was triggered after Teams traffic shifted to infrastructure used by Exchange Online.

Microsoft said it identified the bug during its investigation, developed a fix, and deployed it across affected servers. It has also improved monitoring and added safeguards. The company’s investigation is continuing, with a final post-incident report expected later that week.

This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.

Read more in the JupiteX app

Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.

Or read more news on the web