Microsoft 365 outage and FAA ground stop caused by separate network configuration errors

A major Microsoft 365 outage on November 12, 2026, was caused by a latent fault in the company's cloud infrastructure that was triggered by a routine network capacity upgrade. This fault caused automated health checks to fail, leading to a cascade of server failures as the load balancer removed unresponsive servers from rotation, overwhelming the remaining infrastructure. The outage lasted approximately 36 hours and affected Exchange Online, Teams, and other Microsoft 365 services globally. Separately, on November 13, 2026, the Federal Aviation Administration (FAA) issued a nationwide ground stop for all departing flights in the United States. This incident was attributed to a contractor error during a routine router upgrade at a remote FAA site, which flooded other routers with login attempts and caused widespread network instability. While both incidents involved network configuration errors that overwhelmed critical infrastructure, officials from both Microsoft and the FAA have confirmed that the two events were not related. The Microsoft outage resulted in an estimated $7 billion in lost productivity, while the FAA ground stop led to over 9,000 flight cancellations.

A major Microsoft 365 outage on November 12, 2026, was caused by a latent fault in the company's cloud infrastructure that was triggered by a routine network capacity upgrade. This fault caused automated health checks to fail, leading to a cascade of server failures as the load balancer removed unresponsive servers from rotation, overwhelming the remaining infrastructure. The outage lasted approximately 36 hours and affected Exchange Online, Teams, and other Microsoft 365 services globally. Separately, on November 13, 2026, the Federal Aviation Administration (FAA) issued a nationwide ground stop for all departing flights in the United States. This incident was attributed to a contractor error during a routine router upgrade at a remote FAA site, which flooded other routers with login attempts and caused widespread network instability. While both incidents involved network configuration errors that overwhelmed critical infrastructure, officials from both Microsoft and the FAA have confirmed that the two events were not related. The Microsoft outage resulted in an estimated $7 billion in lost productivity, while the FAA ground stop led to over 9,000 flight cancellations.

Microsoft 365 services experienced a 36-hour global outage due to a latent fault triggered by a network capacity upgrade. The Microsoft outage was caused by failing automated health checks that led to a cascading failure of the load balancer.

A separate nationwide FAA ground stop was caused by a contractor error during a routine router upgrade at a remote site. The FAA router error flooded other network devices with login attempts, causing widespread instability and over 9,000 flight cancellations.

Microsoft and the FAA have both confirmed that the two major infrastructure incidents were not related to each other. The Microsoft outage resulted in an estimated $7 billion in lost productivity for businesses and organizations worldwide.

Chapter guide

Worth noting

  • The video contains a sponsored segment for OpenRouter, which may influence the presentation of its routing algorithm.
  • The exact cause of the FAA router failure remains under investigation, with reports citing potential human error or equipment issues.
  • The $7 billion figure for lost productivity is an estimate and not an official financial report.

Watch the original video ↗