Airports & Aviation · United States / global digital services
FAA and Outlook outages put infrastructure reliability at the center of the AI debate
Separate disruptions to U.S. aviation and Microsoft 365 show why network renewal, failure isolation and recovery planning matter alongside new AI capacity.

A nationwide aviation ground stop and a widespread Microsoft 365 disruption last week put the reliability of everyday infrastructure under scrutiny. The incidents affected different systems, but both raised a practical question for operators investing in new technology: how do you change a network while keeping essential services available?
The FAA is still investigating the November 13 disruption. Microsoft has published a preliminary incident review following the November 12–13 outage that interrupted Outlook access and other functions dependent on Exchange Online. The available accounts describe separate failures, not a shared cause.
What the investigations establish
In its November 15 update, the FAA said excessive connection attempts destabilized communications and radar feeds. Its initial investigation identified sites in Amarillo, Texas, and El Dorado, Arkansas. L3Harris had been deploying a router at the Arkansas location; blocking the two sites stabilized the network.
The agency reported instability at 17 of its 22 Air Route Traffic Control Centers. Air traffic resumed at 8:15 p.m. Eastern on November 13. The FAA said it had no indication of a cyberattack and would reconsider when remote-site replacement and maintenance work is performed.
L3Harris said November 14 that more than 70% of the planned communications conversion from copper to fiber had been completed with its telecommunications partners and the FAA. It said it was supporting the investigation.
Microsoft’s incident notices, reproduced by the University of Pennsylvania from its Microsoft 365 administrative console, give a preliminary explanation for the Exchange disruption: traffic shifts during maintenance and upgrades exposed a latent software defect. Requests accumulated until affected servers exhausted their processing capacity and could no longer accept connections.
Microsoft classified the incident as a technical issue unrelated to cyber activity or AI agents. Its final service-restoration notice records an end time of November 13, and the feed subsequently records publication of a post-incident report. That distinction matters: interrupted access to AI tools is not evidence that AI caused the outage.
The investment question
Infraday perspective: These incidents illustrate why modernization budgets need to cover the transition as well as the replacement equipment. A new connection, router or application can depend on older components and shared services whose limitations become visible only when traffic changes.
For infrastructure owners, the useful questions are concrete. Can a failed component be isolated before it disrupts neighboring systems? Has the upgrade been tested under realistic demand? Can operators reverse a change, and do they have an alternative way to communicate while recovery is underway?
AI investment adds another reason to answer those questions. New applications remain dependent on the networks and services underneath them. Capacity plans should therefore account for service continuity, maintenance and recovery, alongside the equipment needed to support additional workloads.
The next evidence to watch is the FAA’s completed root-cause investigation and Microsoft’s detailed corrective actions. Those findings will be more useful for procurement and operating decisions than treating every outage as proof of the same underlying problem.
Related Infraday reporting: the FAA router investigation. Topic reference: Fortune’s November 16 infrastructure commentary.
Photo: JFK during the November 13, 2026 ground stop. Sashimi-b / Wikimedia Commons, CC BY-SA 4.0. Original photograph displayed at web resolution.
Status and next steps
FAA root-cause investigation and Microsoft post-incident corrective actions.
Review the official next step →Project contacts and next steps
A direct project contact has not been verified for this article. Consult the linked source organization for the appropriate office.
Primary sources
- FAA: ground-stop questions and answers · 2026-11-15
- Microsoft incident notices reproduced by University of Pennsylvania · 2026-11-16
- L3Harris statement · 2026-11-14