
Hi there, argmin readers. Welcome to p(doom) week as we celebrate the Anthropic IPO. Today’s post is some gonzo journalism on Friday’s nationwide ground stop and how it relates to AI fearmongering.
Picking up my phone from the X-ray scanner at the sleepy TSA PreCheck line at the John Wayne Airport, I saw a text from a friend:
“i will blame Openai :p. i am sure that shit would happen eventually (i dont know if this is cyber related)”
He linked to an NBC News story declaring that the FAA had ordered a nationwide ground stop for all departing flights for safety reasons. There was no further explanation. I’d spend the next 6 hours trapped in a linear hallway of frustrated Disneyland tourists trying to figure out what was going on.
People almost immediately took to Twitter, claiming this was the dreaded AI gone rogue. It was too convenient that the FAA had rolled out a new SI tool just the day before.1 But from the get-go, the Trump administration downplayed fears of a cyberattack. By 2 PM Pacific Time, Homeland Security said it looked like a run-of-the-mill telecommunications outage. It just happened to be an outage on critical infrastructure. Whoopsies.
By 4 PM, CBS was reporting that some sort of update by the defense contractor L3Harris had crashed the system. I wrote to my group chat, “Does that mean they were trying to do an update in the middle of the day on a Friday? That can’t be right,” and immediately received the reply, “Your logic is sound, but we shouldn’t underestimate the stupidity of defense contractors.”
Still, it was really weird that there was no official update and we had to scour the internet for anonymous sources. There was no press conference, no briefing. Just chaos from coast to coast. I guess that sort of thing is to be expected, as we have a bunch of crony morons running our government. Even with my extremely low expectations of them, I was surprised the entire air transportation system shut down, and no one said anything. That only made the speculation worse.
The Departures board lit up with cancellations, but my flight back to Oakland stayed “delayed.” For about a half hour, it was listed as “departed,” even though I could see the plane parked at Gate 17. The airport slowly thinned out as people figured out alternative plans.
Bored out of my mind, I started up some conversations with the dwindling crowd. I talked to a guy who had been in the air during the September 11 attacks. He remembered flight attendants running up and down the aisles, and stories of planes flying into buildings all over the country. It would be too weird if we were in the same sort of sea of confusion over a preventable network error.
Eventually the stop was lifted, though it wasn’t at all clear I was getting home. I broke down and went to an authentic Orange County burger place with an airport outpost: Carl’s Jr. Have you heard of it? After 5 hours of sitting in impossibly uncomfortable gate chairs, the Western Bacon Cheeseburger was the most delicious burger I’ve ever eaten. And it was magical too. As soon as I had inhaled it, they called for us to get on the plane.
The flight had been full at 2 PM, but when we pushed off the gate around 7:30, only 29 people were on board. It was then a 30-second taxi, a completely uneventful 75-minute flight, and a short Uber ride, and I was home. I got off easy in the end.
Lots of travelers weren’t as lucky as I was, and I hope everyone has finally made it where they needed to be. This shouldn’t happen. There is absolutely no reason for our national transportation system to be completely crippled for a weekend without explanation. I watched the whole Saturday press conference with Transportation Secretary Duffman (from the Real World Boston) and his FAA subordinates. Duffy stuck to the story from the previous day:
L3Harris was doing “routine maintenance” at a “remote location” on the FAA IT network. They were in the process of modernizing the network, switching from copper to fiber. The contractor installed a router that started sending 200 pings a second. While this number is actually quite small in the grand scheme of things, this caused control-plane congestion in the other routers on the network, overloading their processors. Air traffic control observed this as “network instabilities,” like the ones I regularly get on my Zoom calls, but now at most major FAA communications centers across the country. Since they didn’t know at the time what was causing the instabilities, they grounded everyone out of “an abundance of caution.” No system ever went down, but they couldn’t triangulate the faulty hardware in Arkansas because their maintenance is logged on paper records (!!!). Once they took the faulty router offline, everything stabilized.
Duffy said we do these sorts of updates all the time, and no one had any idea a router in this location could cause this sort of problem. What brought the whole country’s transit to its knees was solved by “hello IT, have you tried turning it off and on again?”2
Now, we wanted to believe it was AI, because that would have been much more exciting than the truth. The truth is, our transportation system depends on an antiquated network. FAA head Bryan Bedford, who was previously famous for his stint on Undercover Boss, took a harder line: the FAA telecom system has been a known critical infrastructure weakness for two decades.
A private defense contractor owns, maintains, and runs this network. Exorbitant pricing and bureaucratic contracting run through opaque federal processes. It is impossible for citizens to hold these systems and actors accountable. The accountability instead depends on a federal workforce that has been reportedly slashed by the Trump administration and his moronic Musk-led efficiency goons. I’m not going to write out their idiotic, unfunny acronym.
It is odd that my left-leaning friends were so ready to blame AI run amok, as this conveys more techno-optimism than blaming the sad, crippled, crumbling infrastructure managed by a moron from The Real World Boston. But, as Kevin Baker notes, it’s easier to fear futuristic doomsday scenarios than to grapple with our real inability to stabilize the world in the present.
If you think I’m being a chud for using the “SI” abbreviation, know that I think the term “AI” is just as stupid.
You can actually get a lot of good insights on what can go wrong in a network and potential explanations for this particular outage on subreddit r/it!

I use Ai. I would use Si if the s stood for shit.
As a first year undergrad / intern, I once plugged a too-long coax ethernet cable into a vampire tap ('twas early 1990s) and took down most of the company network (a few hundred people or more). IT found me very quickly, and the sysadmin unplugged it with what I can only describe as extreme vehemence.
Given how far FAA IT infra seems to lag, it seems like this is still the sort of risk they are still dealing with.