Don Willoughby retweeted
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, 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. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. 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. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
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. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. 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.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
Don Willoughby retweeted
I'll be on @CNN around 7PM ET today talking about the FAA outage.
First - no-one knows what happened, not even the FAA, the FBI, or anyone else. These things take time - so anything is speculation and not conjecture.
Second - the FAA systems are super old dating back to the 1980s with STARS deployed in the 2000s to 2015.
The new AI systems being deployed
The GAO has every year stated the FAA is in a dire straight for reliability (and security). FAA’s 2023 assessment classified 105 of 138 systems, about 76%, as unsustainable or potentially unsustainable.
As of September 1, 2026, FAA said it had replaced over 64% of its copper-based TDM telecommunications infrastructure, leaving roughly a third awaiting replacement.
The modernization plan also illustrates how much equipment needs work. It covers 450 legacy voice switches, digital radio conversion at 1,581 sites, 612 radar replacements, and 53 surface movement radar replacements. Those are program totals, not counts of what remains today. Most of that work targets completion in 2028.
A new system called SMART (AI-based) has been used in limited capacity. SMART began limited operations around Washington, D.C., in September. On November 10, FAA announced its expansion to airspace managed by all 22 air route traffic control centers.
If cyber-related (which again no-one knows) - more modern systems require substantially more interconnected systems that if not properly introduced, can increase attack surface by allowing multiple communications in through third parties, other networks, and less network segmentation versus the older system which was highly segmented from public Internet.
My predictions (purely speculation) - if not cyber related, flights resume tomorrow. Will cause massive flight disruptions for a week or so.
If cyber related - flights probably resume on Monday or later.
Don Willoughby retweeted
LeBron chalk toss in his first return to Cleveland as a Sixer.
He got an ovation from the crowd during starting lineup announcements.
Don Willoughby retweeted
Charles Barkley gets emotional addressing Ernie Johnson:
“It’s been an honor and privilege to work with you all this time.”
Johnson announced today that he will be leaving Inside the NBA after this season.
Don Willoughby retweeted
This Victory Monday on a Friday is brought to you by the Thursday Night Cleveland Browns.
Don Willoughby retweeted
Nick Chubb will sign a 1-day contract tomorrow to retire as a Cleveland Brown, per @JDubsIII on @Browns_Daily.
A Cleveland Browns legend.
Don Willoughby retweeted
Josh Allen has 9 total touchdowns in 5 days.
Deshaun Watson has 8 total touchdowns in 1,041 days
Don Willoughby retweeted
Todd Monken watching Sunday’s film and concluding it’s not all on Watson
#Browns






















