The case
The run began on Thursday, 12 November 2026. Nick Indge of Ars Technica reported that Microsoft's preliminary report "places the outage between November 12 at 16:20 UTC and November 13 at 16:10 UTC, just under 24 hours total." That is 8:20 AM PT on 12 November to 8:10 AM PT on 13 November. Ars wrote that it knocked "much of Microsoft 365 and Exchange infrastructure offline."
On Friday, 13 November, the FAA halted departures across the country. Todd Bishop of GeekWire reported that the agency began seeing unstable radar and communications data "at 12:36 p.m. Pacific," halted departures "shortly before 1 p.m. Pacific," and reopened US airspace "at 5:15 p.m. Pacific."
On Monday, 16 November, two more failures followed. NBC News reported that Chase customers had "trouble accessing their accounts and withdrawing funds," and that the problems also delayed some Zelle payments. A Chase spokesperson said around 6:30 p.m. ET (3:30 PM PT): "Transactions are now posting normally." The same afternoon, CNBC reported that United Airlines "resolved a widespread system outage that briefly affected departing flights."
Next on the calendar is a scheduled event. A Federal Communications Commission public notice says that FEMA "will transmit the nationwide test of the EAS at 2:20 p.m. Eastern Time (ET), on November 17, 2026, using the Integrated Public Alert and Warning System (IPAWS)." That is 11:20 AM PT on Tuesday, 17 November.
The shared thread
Official accounts of the week name no vendor shared by the five events, and no single cause. Microsoft, the FAA, Chase and United each described a separate internal failure. The alert test is a scheduled exercise announced in September, not an outage. On any link between Microsoft and the FAA stop, the Homeland Security secretary said: "I want to make sure everybody understands that there is no connection between this and Microsoft." GeekWire added that "Microsoft confirmed in a statement that it had no indication the FAA ground stop was related to its service disruption."
What the failures do share, analysts and reporting say, is a structural pattern. USA Today, in a 16 November account of the week's crashes, quoted analysts who said a routine change set each failure off. In tightly linked older systems, they said, a small change or a hidden bug can spread far beyond where it started. That reading matches the two fullest official accounts. Ars Technica reported that Microsoft's report lists the incident's final status as "a technical issue not related to cyber or AI/agents." Ars summarized the cause as "the latent bug, changes in traffic, and reduced server capacity" combining, with the defect "dormant since July." Its subtitle sums it up: "A hidden bug, shifting traffic, and reduced capacity led to cascading failures." Ars added that Microsoft "expects to publish its full final incident report on November 20." GeekWire reported that officials blamed "aging FAA telecom equipment that was overloaded with data." As new equipment and technology were added, the Homeland Security secretary said, it "was overwhelming the older system." He said "it appears that this was mechanically driven." Chase, as quoted by NBC News, cited "a temporary issue related to a software bug in on-premise hardware system." United gave no cause.
The claims
For those who see a pattern, five events in six days is too many to be chance. Four failures hit four different kinds of system: a global cloud platform, the national airspace, a major US bank, and a major airline. Then comes a national alert test. Several claims now circulate. Each is set out below as a claim, next to what the companies and agencies have officially said.
First claim: a staged sequence of stress tests, rolling through supply chains, then transport, then banking, with utilities and phone networks said to be next. The claim is a poster's reading of the week, not a finding in the official accounts. Each operator has given its own cause. None describes a planned sequence, and no official statement says utilities or phone networks are next. NBC News reported that Chase said the issue did not impact the entire banking system.
Second claim: an AI failure. Some posters say many firms run the same AI model, and that the model failed in all of them at once. Some, aimed at Microsoft, say AI written code, combined with the loss of experienced engineers in layoffs, explains the outage. Others say an AI system now manages FAA flight paths. Microsoft's report, as quoted by Ars Technica, lists the incident's final status as "a technical issue not related to cyber or AI/agents." On the FAA side, the Transportation secretary said: "There was no possible way SMART would have impacted what happened today." GeekWire reported that SMART only recommends schedules and routes: "FAA specialists review its recommendations, and local facilities decide whether to act on them."
Third claim: a "3 more days" warning about 17 November. The phrase circulated online as a countdown to that date, in the same cluster of posts France 24 reported around the alert test. France 24 reported that "a conspiracy theory claiming a worldwide 'blackout' will hit on November 17 has spread across social media," and that over recent weeks "some posts warn of an impending cyberattack that will plunge the world into darkness, urging people to prepare for days without electricity, internet or access to their money." It reported that some posts encouraged people to withdraw their savings, and that the claim grew up around the already scheduled alert test. When Microsoft and the FAA failed, France 24 reported, those events "helped the story gain traction." On this reading, the outages are warning shots and the test is the signal. Officials say otherwise. The FCC public notice was released on 16 September 2026, two months before the test and before any of the failures. France 24 reported that "television and radio broadcasts will be interrupted for approximately one minute by a test message," and that "there is no planned power cut or internet shutdown. The test will not send messages to mobile phones and does not require any action from the public." The notice names 3 December 2026 as the backup date.
Fourth claim: a coordinated cyberattack, also pointed at 17 November. At the evening news conference on 13 November, GeekWire reported, reporters asked officials whether "a cyberattack or 'rogue AI'" could be ruled out. Each organization has said it saw no sign of an attack. Ars Technica reported that Microsoft called its outage a technical issue "not related to cyber or AI/agents." The Homeland Security secretary said there was "zero evidence" of a cyberattack so far, though there was "nothing completely certain right now." NBC News reported that Chase said the issue was not "cyber-related." CNBC reported that "a United spokesperson said there was no indication that the outage was a cyberattack."
Fifth claim: about 60 air traffic controllers dispute the official explanation for the ground stop. Washington Examiner homeland security reporter Anna Giaritelli said on CNN (Laura Coates Live, Friday 13 November) that she had spoken with 60 air traffic controllers who did not accept the official explanation, mainly because such equipment work is normally done overnight, not on a busy Friday afternoon. That is her report of unnamed sources, not a published investigation, and the account is unconfirmed. Officials, as reported by GeekWire, blamed "aging FAA telecom equipment that was overloaded with data." As new equipment and technology were added, the Homeland Security secretary said, it "was overwhelming the older system." He said "it appears that this was mechanically driven."
The adherents' answer
Adherents answer that each explanation may hold on its own, and still not settle the whole week. Every failure was traced to something routine: a months old bug, a router swap, a hardware glitch, an airline application. They ask why routine faults struck so many critical systems in so few days. They point out that the investigations are still open, and that Microsoft's final report has not yet been published. They accept that the alert test was scheduled in September. Their question is what the week reveals about how fragile, and how connected, these systems already are, and who might be watching.
