There exist several conflicting sources, but I will use the summary from CBS:
The FAA's preliminary investigation has led the agency to believe the issue was limited to Cisco 600 series routers that were manufactured between 2001 and 2006, senior government sources told CBS News.
The sources said the routers essentially got overwhelmed, and started feeding out-of-sync data packets into the larger air traffic control system. That causes static over voice communication lines and can cause screens to flash or go to black.
However, we have a secondary explanation, which may or may not conflict with the former.
Sources told CBS News they are receiving conflicting information about the cause of the issue. Multiple sources said Friday that an update to the the private communications network that connects the U.S. air traffic control system caused the system to reboot, leading to a crash and a communications outage.
Nonetheless we can analyze both cases.
In the first case, we can note that an AI tool was rolled out nationwide, a few days ago. This tool has nothing to do with communications, but rather "advising air traffic controllers to assist in managing air traffic across the entire national airspace system." If the network bandwidth is the problem, then we necessarily know that it's due to the introduction of new burdens on the network. And it isn't something that can be fixed within 4 hours or a software patch. So that leaves the main suspect, the newly rolled out poorly coded AI tool. Potential causes are:
Instantiating too many connections without being aware of old hardware limitations.
A loopback issue with the code, causing some sort of network storm.
In the second case, where the private communications network was down, we know that the hardware in question is the L3Harris routers and switches.
As an aside, we note that these routers should be somewhat different than the modern ones, in that they may be using legacy TDM (Time Division Multiplexing), originally used for telephone era, or have TDM to standard packet conversion hardware for interoperation with legacy and modern hardware.
There was a recent snippet with the CTO of L3Harris posted on LinkedIn about him being vibe coder. I will post the relevant transcription of the associated clip (parentheticals and emphasis mine):
Andrew (CTO of L3Harris Technologies), are you a vibe coder at all? Are you using Cursor or anything like that?
Yeah, and I love the trend of vibe coding because it really does help accelerate workflows, right? And I actually tell every engineer at L3Harris that they should be looking for how to use AI enabled tools such as CodeMetal (another automated code generation tool, which claims to be provably correct, which is impossible under all circumstances) to be more productive as engineers...
And so, we can conclude that it's also highly likely that the relevant firmware update which caused issues in the realm of potentially boot loops, changed configs, etc. is caused by vibe coding.
In other words, no matter what the source of the issue which is contested, it's likely the vibe-coding culture and AI push is the cause in some way. It is expected, for many those here in tech, and this will certainly not be the last incident.
Edit: As an addendum, we have further explanation from Sean Duffy. Take it's veracity with what you will, from the following article
Duffy said the outage occurred during routine FAA telecommunications maintenance at a remote facility, where aging copper communications lines were being replaced with fiber-optic service. The work was being performed by L3Harris, the FAA's longtime telecommunications contractor, as part of a broader modernization effort.
During the upgrade, Duffy said, a router began flooding the FAA network with traffic, generating more than 1,000 connection attempts every four to five seconds.
"We see zero evidence of anything nefarious and zero evidence of anything AI-related," FAA administration Bryan Bedford told reporters.
With this in mind, it corroborates both reports from CBS, where it causes both effects. During an upgrade of a router, it flooded the network with traffic, which would have causes issue one of network bandwidth, and is an apt description of the second.
Of course, details about the actual router installation are not available, as well as the specific router are not available. You are free to take Bryan Bedford's comment with what you will.