Inside the Router Storm Behind the November 2026 FAA Ground Stop

We all knew that the infrastructure was ancient; the benefits of the ancient technology are decreasing over time with limited availabilty of parts and limited capacity.

  • Technology
  • FAA
  • Networking

On Friday afternoon, November 13, 2026—with disruptions spilling well into Saturday, November 14—the Federal Aviation Administration (FAA) ordered a nationwide ground stop that halted U.S. departures for nearly five hours. The stoppage, the longest since September 2001, stemmed from a localized telecommunications upgrade that cascaded into a system-wide network overload.

The Copper-to-Fiber Cutover

According to Transportation Secretary Sean Duffy and FAA technical briefings, the failure began during routine maintenance at a remote FAA facility. Contractors with L3Harris, the agency's telecommunications provider, were migrating legacy copper lines—built on aging Time-Division Multiplexing (TDM) architecture—over to modern optical fiber because the older copper circuits were being retired.

During that cutover, a router tied to the upgrade began malfunctioning. Instead of dropping offline cleanly, the device started firing more than 1,000 connection requests every four to five seconds into the FAA's private air traffic control network.

Packet Floods and Out-of-Sync Telemetry

Air route traffic control centers rely on deterministic, low-latency links to keep radar feeds and controller-to-pilot radio frequencies synchronized. When the misbehaving hardware flooded neighboring nodes—preliminarily linked by federal sources to legacy Cisco 600-series routers manufactured between 2001 and 2006—the older routing equipment could not process the sudden surge in session requests.

Overwhelmed routers began passing delayed and out-of-sync data packets across the backbone. In operational terms, that packet desynchronization introduced static onto air-to-ground voice channels and caused controller radar displays to flicker or blank out. Unable to guarantee clean telemetry across all 22 en-route centers, the FAA froze takeoffs at 3:30 p.m. ET while keeping airborne flights under active management until they landed.

Isolation and Network Containment

Officials with the FAA and the Department of Homeland Security ruled out a cyberattack or external intrusion, pointing instead to an internal hardware or configuration fault during the line transition.

To restore stability before lifting the ground stop at 8:15 p.m. ET, network engineers isolated the originating equipment and disabled the specific routing functionality responsible for the connection flood. Technicians then applied the same configuration disablement across roughly 60 comparable routers nationwide to prevent the packet storm from recurring while investigators review whether installer error or faulty hardware triggered the loop.


Sources

  • Federal Aviation Administration (FAA) – Nationwide Ground Stop: Questions and Answers (November 15, 2026)
  • U.S. Department of Transportation – Update on Restoration of Airspace Following Nationwide Ground Stop (November 15, 2026)
  • CBS News – FAA lifts nationwide ground stop that disrupted thousands of flights (November 14, 2026)
  • NPR – FAA blames Friday's ground stop on 'equipment issue' during telecoms network upgrade (November 14, 2026)
  • Flightradar24 – US nationwide ground stop operational timeline (November 14, 2026)