Research

In 1993 We Found Our First Broadcast Storm Playing Doom Over IPX. Carmack Fixed It the Day After Release. On Friday the FAA Fixed Its Outage by Turning Off Broadcasting

In 1993 We Found Our First Broadcast Storm Playing Doom Over IPX. Carmack Fixed It the Day After Release. On Friday the FAA Fixed Its Outage by Turning Off Broadcasting

If you run a network, the lesson is 33 years old: anything that shouts to every device on the segment will eventually take the segment down, so allow broadcast for discovery and nothing else. The FAA learned it again on Friday. A generation of network admins learned it in December 1993, from a video game.

How a lot of us learned networking

Doom shipped in December 1993, and its multiplayer ran over IPX, the Novell networking protocol that ran most office and campus LANs of the day. I worked in the computer lab at Nassau Community College, and we found Doom lag on IPX before most of us knew the words "broadcast domain." All we wanted to do was shoot each other in peace.

The problem was how the game talked. John Carmack, quoted in a review of Fabien Sanglard's Game Engine Black Book: Doom: "Doom used IPX broadcast packets to communicate between the players." Every move, sent to every machine on the network, whether it was playing or not. His own summary of the result: "A few dozen Doom players could cripple a network with a few thousand endpoints." On campuses built from bridged IPX networks, that meant the whole campus.

His fix, from the same account: "I quickly changed the network protocol to only use broadcast packets for game discovery," with directed packets between players during the game. He made the change the day after release. Admins still added Doom-specific rules to their bridges, along with stern notes that nobody should play the game. Nobody listened to the notes.

Three years later the problem moved to the internet. Doom and the first Quake assumed a fast local network, and most players were on modems. Carmack's .plan update from August 1996 estimated "300+ ms latencies, minimum," and he rewrote Quake's network code so the game would guess at your movement until the server answered. QuakeWorld shipped in December 1996, and client-side prediction is in nearly every online game since. Lag was not a nuisance to us. It was the first performance engineering problem many of us ever solved.

Friday, November 13, 2026

The FAA's own questions-and-answers page describes data flooding its telecom network "at a rate of 1,000 connection attempts every 4 to 5 seconds," from two remote sites, one of them in the middle of a router replacement. Then the fix: "The broadcasting function was also disabled on all the new routers as a precaution," followed by "more than 60 other Juniper routers." (Our post, with the 2009 precedent.)

The FAA has not published a root cause, and we are not claiming the two failures are identical. But the fix rhymes: when the network started to drown, the people running it turned off broadcast on the new equipment. Carmack did the same thing in December 1993, in a day, for a video game.

What the LAN party taught that the change window forgot

  1. Broadcast is for discovery, not for traffic. Find your neighbors by shouting, then talk to them directly.
  2. Storm control is a configuration setting. Every managed switch and router has a way to cap broadcast and multicast before they eat the link. Turn it on and set it low.
  3. Test the new box against the old ones before it touches production. Our Doom test lab was the college computer lab after hours. Most of us now have budgets for a real one.
  4. Latency is a design input, not an excuse. QuakeWorld worked because Carmack designed for the network people actually had, not the one he wished they had.

The Gen-X note

We grew up debugging networks so we could play games on them, then spent our careers keeping them up for everyone else. Five outages in six days this week, and not one of them was an attack (the full week). It wasn't the hackers. It was the change window, which anyone who ever brought down a lab with a Doom deathmatch learned to respect.

So, from the generation that learned broadcast storms from Doom: turn on storm control, test before you plug in, and please don't make us come out of retirement to fix it. We'd like the retirement first.

What is not known

  • The FAA's root cause. The broadcast fix is the FAA's own description; why the flood started is still under investigation by the FAA and L3Harris.
  • Whether Friday's flood was a broadcast storm in the technical sense, a routing problem, or something else. "Rhymes" is our word, not the FAA's.

Sources

Adam Halbert's review of Fabien Sanglard's "Game Engine Black Book: Doom" (ahalbert.com, April 20, 2026), for the John Carmack account of IPX broadcast and the fix. John Carmack's .plan update of August 2, 1996, as archived and quoted by QuakeWorld history pages, for the modem latency estimate. QuakeWorld.nu, "The History of QuakeWorld," for the December 1996 release. FAA, "Nationwide Ground Stop: Questions and Answers," November 15, 2026.


How do AI models see YOUR brand?

AIPM has audited 250+ domains. 15 seconds. Free while still in beta.

Audit your site now → aipmsec.com