We Said 'Protocol Storm' and 'Turn On Storm Control.' Officials Now Say a Router Feature Broadcast Data More Widely Than Necessary, and the Maker Says Its Routers Worked as Intended
If you run routers, go turn on storm control today. That was our advice on Sunday, and the reporting since then says it was the right advice. Officials now describe the FAA's November 13 ground stop as a router feature that sent data further than it should have, and the router maker says its equipment did what it was told.
What we wrote, and when
Our post on the FAA math went up on the evening of Sunday, November 16 (Wix timestamp 00:28 UTC, November 17). On the cause, it said: "One device sending a flood of connection attempts until the network around it falls over looks like a change that went wrong on a live network: a bad filter, a loop, or a protocol storm, done without the change control and rollback plan that exist to stop exactly that." It called that "our reading of the public facts, not a finding."
For prevention, item two on the list: "Storm control and control-plane protection on every router, so one misbehaving device cannot flood its neighbors. These are configuration settings." And Patrick's LinkedIn joke from the same weekend asked whether the other $49.5 billion was "to click the spanning tree setting."
What has come out since
The feature. Per TechTimes, citing the Wall Street Journal, officials believe "a feature that broadcast data more widely than necessary" caused the overload. Transportation Secretary Duffy said officials "stopped the affected routers' ability to broadcast."
The FAA's own words. Its questions-and-answers page, dated November 15, says "the broadcasting function was also disabled on all the new routers as a precaution," then on "more than 60 other Juniper routers," and installations were paused. On November 17, CNBC reported the FAA confirmed the pause.
The maker. HPE, which owns Juniper, says its devices "did not fail," and a spokesperson told the Journal the routers "appeared to work as intended." A router that works as intended and still floods the network is a router configured to flood the network.
A second router. Duffy said a router installed about three weeks earlier in Amarillo, Texas "started to flood our system as well." Two sites, the same new equipment, the same behavior: that is a setting, not bad luck.
The honest scorecard
We got right: a storm, not an attack; a configuration and change-control failure, not a hardware fault; and the fix, which is a configuration setting.
We did not get first: the FAA said it disabled broadcasting on November 15, the day before our post. We read the shape correctly; the FAA had already shown its hand.
Still not confirmed: the root cause. FAA officials say they still cannot say "whether faulty hardware, a faulty installation or a faulty configuration set it off," per TechTimes. Nobody official has said "multicast" or "broadcast storm"; those are our words and TechTimes' words. When the root cause lands, we will update this post either way.
Call it 95 percent on the nuts, which is as high as we ever go.
Why it matters past the joke
Senate Commerce Democrats put it well, per CNBC: "Identifying the device that failed does not establish why it failed." The why, on the evidence so far, is a feature left on in new equipment that nobody tested against the old network before it went live, at two sites, three weeks apart. The DOT Inspector General described almost the same thing in 2010, about a Harris router configuration copied from a replaced box: our 2009 write-up.
What to check on your own network, today:
Storm control on every switch and router port that faces another device: cap broadcast and multicast as a percentage of the link, and alert when it trips.
New-equipment baselines: what does the box send, by default, when you plug it in? Find out in a lab, not in production.
Change windows for remote sites: the FAA says it "will reevaluate when we do replacement/maintenance work." Mid-afternoon on a Friday was never it.
And if you learned all this from Doom over IPX in 1993, we wrote that one up too.
Sources
FAA, "Nationwide Ground Stop: Questions and Answers," November 15, 2026. TechTimes, "FAA Ground Stop Traced to Two Routers Flooding Network: Agency Disables Broadcast Feature," November 16, 2026, citing the Wall Street Journal. CNBC, "FAA pauses installation of new routers after ground stop," November 17, 2026. Aviation Week, "FAA Says Router Malfunction Led To Ground Stop," November 14, 2026. Our original post: One Router in Arkansas Grounded 12,462 Flights.
How do AI models see YOUR brand?
AIPM has audited 250+ domains. 15 seconds. Free while still in beta.



Comments