On Friday, November 13, 2026, the FAA ordered a ground stop for all US airports, citing "extraordinary circumstances". Transportation Secretary Sean Duffy attributed it to "a communication issue impacting all Air Route Traffic Control Centers". When this market opened, officials had given no root cause, and CNN cited two law enforcement officials saying preliminary reports indicated it was not a cyberattack.
Resolution
Resolves to the one answer that best describes the root cause of the communications failure behind the ground stop, as publicly established by December 31, 2026 (Pacific time).
What counts as established: statements or reports from the FAA, DOT, DHS or CISA, the FBI, the NTSB, the White House or the DOT inspector general, or reporting by a major outlet (Reuters, AP, New York Times, Wall Street Journal, Washington Post, Bloomberg or similar) that investigators reached a finding. Speculation, early anonymous impressions and claims of responsibility do not count on their own. If official statements and reporting on investigators' findings conflict, I will go with the better-supported account.
If several things went wrong, the answer is the initiating cause. A cyberattack that knocked out equipment resolves as a cyberattack. A bad software update at a telecom contractor resolves as a software bug.
Answers
Cyberattack in which AI materially enabled or carried out the attack. Malicious cyber activity where officials or investigators find that AI did substantial work in the attack, for example finding or exploiting the vulnerability, writing the malware, or running the intrusion autonomously.
Cyberattack with no AI role established. Any other malicious cyber activity, including by a malicious insider. This is also the answer when a cyberattack is established and AI involvement is only speculated.
Physical sabotage or physical attack. Deliberate damage or interference that is not cyber: cut cables, arson, radio jamming.
AI system malfunction or AI agent error (no attacker). For example an AI traffic-management tool misbehaving, or an AI agent making a bad change to production systems. This takes precedence over the software answer.
Software bug, failed update, configuration or operator error. Non-malicious, at the FAA or a contractor, with no AI system at fault.
Hardware, power or cable failure, or accidental physical damage. Failed equipment, power loss, an accidental fiber cut, a fire.
Natural event. Space weather, severe weather, an earthquake.
Other established cause. A cause that meets the evidence bar and fits none of the above.
No root cause publicly established by Dec 31, 2026. Nothing meets the evidence bar, including when officials say only "technical issue" or "communication issue" without saying what caused it.
If officials rule out an attack but do not say enough to choose between the non-attack answers, I will split the resolution evenly among the non-attack answers that fit their account.
I may resolve before the close date if a final official finding is published and nothing credible disputes it for two weeks.
Related markets: confirmed as an AI hack by Nov 16?, result of a cyberattack?, how long will it last?
People are also trading
@SpeaksForTrees if installing hardware that fails comes under that “software bug, failed update…”, and not “hardware failure..” or other “established cause”, then I think that’s a bad resolution.
@capybara i agree that resolution would be confusing but i interpret the commas as separate resolution criteria and without assuming the intention of the creator i can't say either way; i sold all positions because of uncertainty
@SpeaksForTrees even if you follow that interpretation, you don’t “update” an old copper wire with a new one, you replace it. “Update” is very software orientated.
@capybara good point, the more I think about it you're probably closer to right about this than me. I just started the conversation to try and get the market creators input as ultimately that matters most to traders.
@SpeaksForTrees For resolution I'll let Fable resolve it according to its best judgment in light of the market description and discussion here. I'll wait a few more days for the evidence to settle though.
@capybara if operator means “any human interacting with the system” then practically everything will come under that, as even installing faulty hardware or not maintaining hardware is due to the error of the person’s whose duty it is to do it. Given how extreme that is, I wonder if “user of the system” is a better interpretation of “operator”.
@capybara "communications disruption set off by a copper-to-fiber upgrade at a remote site, which they did not identify. A newly installed router began firing more than a thousand connection requests every few seconds, which disrupted voice communications and radar feeds."
This implies to me that the router was digital and misconfigured, which is "software configuration".
@CraigDemel I broadly agree with your reading. It would require the router to not be faulty and the flooding behaviour to not be correct behaviour. If the flooding is something like topology discover on first boot but the rest of the network can’t handle it, then I’d lean toward “other established”, as configuration is correct, just the rest of the network can’t handle it, which may not have been foreseen.
@capybara Sure - although even if the flooding results from a default config which is normally "correct", if some other behavior was desired, configurable, but not configured, then it would be "configuration".
I think I am mostly in agreement. I wasn’t trying to say default is “correct”. I was trying to rule out the edge case where you install an incompatible router and someone says it’s just a config issue, as the router could have been installed with power set to off (or disable some core feature).
Reading ft.com’s article, it sounds like the “update” is the progressive installation of new hardware which generates more network traffic, and that the actual failure was overload to switches and not some software update.
@capybara doesnt the hardware option mean actual physical damage? and the purple option includes but is not limited to software? so a hardware upgrade would resolve to purple option. and in any cases although they were installing new hardware, the issue happened in software
@calour I think that a router being overloaded will either count as hardware failure or as other established cause. We don’t actually know in what way the router failed: was it just a message queue overflow, or like a melted connection.
