A contractor’s router grounded SFO flights. Who was watching it is still unanswered
SAN FRANCISCO - The ground stop that froze SFO departures for hours on Nov. 13 started with a router swap at a remote federal site in Arkansas, the FAA says. Whether anyone from the agency was watching that work has not been confirmed by any official record.
How a router swap stopped flights
L3Harris, the FAA’s network contractor, had been working at a radio communications site in El Dorado, Ark., including deploying a new router, according to the FAA’s questions-and-answers page. The agency says its older equipment became unstable when data flooded its telecommunications network at “1,000 connection attempts every 4 to 5 seconds,” disrupting aircraft communications and radar feeds. Instability hit 17 of its 22 en route air traffic control centers.
The FAA first pointed to two possible sources: the El Dorado site and a radar site in Amarillo, Texas. L3Harris blocked both and the network stabilized. The agency says it then disabled the function at fault on the originating Juniper routers and on more than 60 others, and paused installing them.
Transportation Secretary Sean Duffy said Nov. 15 that the contractor had secured the two routers from the Texas and Arkansas sites, and on Nov. 16 that FAA staff were at L3Harris’ Florida lab analyzing the router “that was the likely cause.” The FAA says it has no indication of a cyberattack, and that it and L3Harris are still investigating the root cause.
The FAA calls the swap a “routine replacement at a remote facility,” work it says has regularly been done for decades, and says it will reevaluate when such work is scheduled. L3Harris said in a statement that it is supporting the investigation and takes the ground stop seriously.
Who was watching the contractor
The union for FAA equipment technicians, the Professional Aviation Safety Specialists, said in a Nov. 14 statement that the problem was isolated to “two contractor owned and maintained routers that were being updated mid-day.” It said its members “were not involved in the upgrades that led to the ground stop.”
PASS said contractors have historically followed a protocol in which FAA employees do a risk assessment and coordinate the maintenance. The union did not say in its statement whether that happened in El Dorado.
Some news reports, citing unnamed sources, say the contractor worked without anyone from the FAA watching. No FAA, Transportation Department, L3Harris or union record released so far confirms that, or says who, if anyone, supervised the installation. The FAA’s published account says only that it will reevaluate when it schedules this kind of work.
At SFO and around the city
The ground stop held SFO departures from about 12:30 p.m. Nov. 13, the FAA says. SFO said Pacific-bound flights were cleared as of 3 p.m. and the stop had ended as of 5:30 p.m. United warned Nov. 14 that some flights would stay delayed or canceled. SFO, the FAA and the airlines have published no count of SFO cancellations or delays.
Nationally, operators canceled about 12,462 flights that day, the FAA says, though not all because of the ground stop.
The same week, the Superior Court warned Nov. 12 that a Microsoft outage could delay staff emails, and Muni’s Central Subway signs, arrival predictions and live maps went dark for about an hour on Nov. 13 as trains ran normally before the SFMTA reported a fix. Neither agency tied its problem to the router failure.
What it means
Before heading to SFO, check your flight with your airline, as United advised during the stop, and the FAA’s national airport status page for ground stops and delays. The FAA says it has paused installing these routers. For city emergency alerts, text your ZIP code to 888-777 to join AlertSF.
Source: FAA ground stop Q&A; Transportation Secretary Sean Duffy on X (Nov. 15, Nov. 16); L3Harris statement on X, Nov. 14; PASS statement, Nov. 14; SFO on X, Nov. 13 (1, 2); United on X, Nov. 13–14 (1, 2); S.F. Superior Court on X, Nov. 12; SFMTA on X, Nov. 13 (1, 2, 3); FAA NAS status; SF.gov AlertSF
- Federal Aviation Administration: Nationwide Ground Stop: Questions and Answers, Nov. 15, 2026
- SFO on X: Pacific-bound flights cleared (posted 3:30 p.m., text headed 3:00pm), Nov. 13, 2026
- SFO on X: ground stop ended (posted 5:45 p.m., text headed 5:30pm), Nov. 13, 2026
- San Francisco Superior Court on X: Microsoft outage may delay court emails, Nov. 12, 2026
- SFMTA on X: Central Subway signage unavailable, Nov. 13, 2026, 9:49 a.m.
- SFMTA on X: predictions and live maps down, Nov. 13, 2026, 10:11 a.m.
- SFMTA on X: predictions restored, Nov. 13, 2026, 10:56 a.m.
- United Airlines on X: ground stop lifted, no change fees, Nov. 13, 2026, 6:56 p.m.
- United Airlines on X: some flights still delayed or canceled, Nov. 14, 2026, 8:44 a.m.
- SF.gov (Department of Emergency Management): Sign up for AlertSF
- Transportation Secretary Sean Duffy on X: contractor secured the two routers, Nov. 15, 2026
- Transportation Secretary Sean Duffy on X: FAA team at L3Harris lab analyzing the likely router, Nov. 16, 2026
- L3Harris on X: statement on the Nov. 13 ground stop, Nov. 14, 2026
- Professional Aviation Safety Specialists (PASS): PASS On the Nationwide Ground Stop, Nov. 14, 2026
- FAA National Airspace System Status