Amtrak's booking site failed during the FAA's four-hour national ground stop

Two transport systems failed the same way on Friday evening, and only one made the national wire. As we reported on November 14, upgrade work on the Federal Aviation Administration's aging telecom network overloaded its equipment, and the agency stopped every US departure for more than four hours↗ ¹. Travelers who turned to Amtrak, the national passenger railroad, met a booking site returning "We've experienced an unknown error", and Amtrak blamed a "systemwide update" ²³. Both failures had the same trigger: an update pushed into a system that is never allowed to stop.

A maintenance window grounded the country

A contractor crew switching a remote site from copper to fiber left a router flooding the network with more than 1,000 connection attempts every four to five seconds↗ ⁴. The FAA still runs what Transportation Secretary Sean Duffy called "1980s little copper lines"; the old switches overloaded, radar and communications feeds turned inconsistent, and the agency stopped departures rather than fly on bad data ⁵. "Our new IP switches did not go down," Duffy said. "It's the old hardware that went down" ⁵. The order was lifted at 8:15 p.m ⁶. Eastern ⁶.

The AI theory was cleared within a day

FAA Administrator Bryan Bedford said officials saw "zero evidence of anything nefarious, and zero evidence of anything AI-related" ⁴. Duffy said there was "no possible way" SMART, the agency's new AI traffic-planning tool, could have touched the systems controllers use; its developer, Boston-based Air Space Intelligence, which holds a 12-year FAA contract, denied any role ⁵. Microsoft▼−0.28% — Microsoft, down 0.28 percent today, whose Outlook outage primed the speculation, called its own disruption "not related to cyber or AI / agents" ⁷.

The trains ran; the sales channel did not

Amtrak's site and app began failing shortly before 5 p.m ³. Eastern, while the ground stop was still in force ³. Callers waited longer than usual, and when FOX 5 DC rang the support line around 8 p.m., an automated message said Amtrak could not take calls↗ because of "unusually high call volume" ³. Systems were returning to normal by 9 p.m. ²³.

A spokesman said "Amtrak service is operating normally, and we are seeing increased demand for travel across our network" ². About 1.5 million air passengers were affected that evening ⁸, and the country's one national rail alternative had no working way to sell them a seat. The booking failure was written up by the rail trade press↗, in Trains Magazine; the Associated Press's nationwide wire story on the ground stop never mentions Amtrak ²¹.

Taxpayers buy the fix; vendors sell the discipline

The repair bill lands on the public. Congress approved $12.5 billion for the air-traffic overhaul last year ¹. The White House wants $30 billion more ¹, and Duffy now puts the need at $50 billion ⁹. L3Harris▼−3.91% — L3Harris, down 3.91 percent today, the defense contractor whose crew was on the network, fell more than 4 percent after hours↗ and says it is supporting the investigation ⁹. Duffy's words, "They own this network... I can't go somewhere else," are vendor lock-in said plainly ⁴.

Neither failure had a staged rollout or a fallback

Every institution adopting AI pushes more changes, not fewer, through systems that cannot stop, and every agent rollout is a maintenance window. Neither Amtrak nor the FAA has described a staged rollout or a tested fallback, and that is the layer both failures point to. The watchables are concrete: whether Congress writes staged-rollout and failover requirements into the new money, and how AT&T▼−0.13% — AT&T, down 0.13 percent today, hired in August on an initial $74.3 million award to lead the FAA's replacement network, scopes its first cutovers ⁵.