The case
On Thursday, 12 November 2026, Microsoft 365 stopped working for users around the world. Lawrence Abrams of BleepingComputer reported that the incident "began at 11:20 AM ET on Thursday, November 12, and continued until 11:10 AM ET the following day," which is 8:20 AM PT to 8:10 AM PT. He wrote that it "disrupted Microsoft 365 services worldwide, including Outlook, Exchange Online, Teams, and Copilot."
The effects reached far past email. Johana Bhuiyan of The Guardian reported: "Jails could not release prisoners, hospitals turned to paper records, schools lost contact with parents, and police departments could not receive crime reports."
The adherents' reading
For those who see a pattern, the timing matters most. The next afternoon, the FAA halted departures nationwide. PolitiFact's Maria Briceño reported that a Spanish language post "said the blackout already started, pointing to the Nov. 12 to 14 Microsoft outage" and to the FAA ground stop. At a news conference that evening, the Homeland Security secretary acknowledged the link people were drawing: "I know a lot of people are making that jump," GeekWire's Todd Bishop reported.
Posters on Reddit add a claim of their own. They claim that code written with AI tools, combined with the loss of experienced engineers in layoffs, explains why the outage happened and why it lasted so long.
The official view
Microsoft's preliminary report gives a technical cause. Nick Indge of Ars Technica reported that the report "lists the incident's final status as 'a technical issue not related to cyber or AI/agents.'" Ars described "the latent bug, changes in traffic, and reduced server capacity" combining, with the defect "dormant since July," and added that Microsoft "expects to publish its full final incident report on November 20."
BleepingComputer quoted the report on how fast it spread: "In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive."
On the FAA link, GeekWire reported that "Microsoft confirmed in a statement that it had no indication the FAA ground stop was related to its service disruption." During the outage itself, Jenni Reid and Sara Salinas of CNBC reported that "Microsoft says it has not detected any malicious activity causing the outage."
The adherents' answer
Adherents answer that a technical cause does not explain the timing. A defect that sat quietly for months surfaced in the same week as a nationwide ground stop, a bank failure and an airline failure. The safeguards meant to contain it did not hold. The final report is still days away. Until it is published, they say, the question of why it broke now, and why so much else broke with it, stays open.
