FAA Ruled Out Cyberattack on Nov. 13 Before Naming the Router Fault, and the Trigger Is Still Unknown
Security / news
FAA Ruled Out Cyberattack on Nov. 13 Before Naming the Router Fault, and the Trigger Is Still Unknown
A router flooded the FAA's FTI network with 1,000-plus connection attempts every four to five seconds; the public record has no forensic basis for the cyber ruling.

Officials ruled out a cyberattack on the 13 November 2026 FAA ground stop within hours, but the public record contains a router that "started flooding other routers" and no published forensic basis for the "not cyber" finding. The trigger has not been determined, and as of 15 November no CISA statement and no NTSB, DOT Inspector General or GAO investigation had been announced, according to GovInfoSecurity's reconstruction.
What the FAA says happened
At 3:54 p.m. ET on Friday 13 November the FAA ordered a nationwide ground stop, citing "communication issues". It lifted the stop at 8:15 p.m., the only end time given on the record. The Department of Transportation says more than 3,500 flights were grounded; FlightAware counted about 9,159 cancellations on Friday alone, per GovInfoSecurity.
The official explanation: a router being replaced during a TDM-to-IP conversion at a remote site "started flooding other routers" with "over 1,000 connection attempts every four to five seconds". The network is FTI, the contractor-owned FAA Telecommunications Infrastructure, which carries voice, radar and data links. Harris won that contract in 2002 and L3Harris now operates it. Fortune reports that an L3Harris contractor was moving lines from copper to fiber, and that the company says it has finished more than 70% of that conversion.
Two days of shifting explanations
The account changed each day, which matters because the cyber ruling came first and the mechanism came after.
| When | Who | Statement |
|---|---|---|
| Friday afternoon | FAA | "communication issues" |
| Friday night | Sean Duffy, Transportation Secretary | Overloaded legacy routers and data inconsistency |
| Friday night | Markwayne Mullin, Homeland Security Secretary | "just a telecommunications outage" |
| Saturday | Duffy | Contractor doing routine work triggered the flood; "We haven't determined what the fault was" |
On Saturday 14 November, Bryan Bedford, FAA Administrator, said "I think we've all concluded that it's not a cyber issue" and described "zero evidence of anything nefarious". Duffy said "we don't believe this was cyber at all" and "It wasn't a foreign actor". Fortune reports that the White House Situation Room was activated, the FBI went to FAA facilities, and officials found no evidence of hacking chatter.
What the "not cyber" ruling rests on
The on-record basis is absence of evidence plus a benign mechanism. A flooding router is consistent with a hardware fault, a bad configuration or improper installation, and it is also consistent with a malformed packet or a rogue device on the network. The public record does not separate them. GovInfoSecurity lists what is still unexplained:
- Whether the fault was defective hardware, misconfiguration or improper installation
- Whether the FAA shut overloaded routers down deliberately or they failed on their own
- The router's make, model and firmware, and whether the outgoing or the incoming unit was flooding
- Whether the change was tested, who performed it and whether rollback criteria existed
Bedford separately described routine replacement of about 2,000 Cisco 600 routers with Juniper units, which he did not link to the failure. A CBS report cited by GovInfoSecurity names Cisco 600-series routers as the failed model, from unnamed sources, and GovInfoSecurity marks that unverified. Bedford also said the work was not part of the $12.5 billion Peraton-FAA modernization effort, while GovInfoSecurity notes that GAO lists copper-to-fiber replacement within that program's first phase, so the claim is disputed.
Why the mitigation tells you more than the label
The FAA disabled an unnamed function on about 60 routers of the same type nationwide, pending tests with L3Harris. Disabling it on every router of that type points toward the model and its configuration rather than one bad install, though the FAA has not said so. Tracing the source took about 45 minutes, partly because maintenance records were on paper. Bedford's description of the redundancy was "no backup to the backup", and Nick Daniels, president of NATCA, put the effect plainly: "we know we didn't have communications with airplanes".
Dependence on a single contractor network is itself an exposure that a cyber ruling does not remove. The CISA KEV analysis shows how the government triages known exploited flaws within days. Here the router model is unnamed and no CVE exists to triage. The Java4Shell dispute shows how much a single number can hide; this outage so far has no number at all.
Senators Maria Cantwell (D-Wash.) and Tammy Duckworth (D-Ill.) have called for reviews. The next concrete milestone is the FAA and L3Harris test of the disabled function on the roughly 60 routers, and whether either names the router model and the change that preceded the flood.
Sources
More in Security
- 01Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still OpenHundreds of settings are on from first boot, Microsoft warns Server 2025 workloads may break, and the 33 percent of servers still on 2019 are untouched.
- 02VicOne's 28 Robotics Zero-Days Come From a Sponsored Article With No CVE IDs and No Named ProjectsThe Tokyo security firm's count ran as paid content on IEEE Spectrum and The Robot Report. An independent March paper counted 38 flaws in three named consumer robots.
- 03Synology's Third Critical DSM Advisory in 62 Days Hits OAuth, and the Last Patch Does Not Cover ItCVE-2026-120382 scores 9.8 and needs no login. DSM 7.4 and 7.3 builds ending -2 and -6 fix it; 7.2 and 7.1 have none yet.
- 04Codex's Sandbox Uses Seatbelt, bubblewrap and MXC, and Lets Commands Read Broadly by DefaultOpenAI's Nov. 18 engineering post says writes are confined to the workspace and the network is off, while reads stay wide open.