Is it true that the November 12–13 outages are the start of a November 17 "digital apocalypse" and bank shutdowns?

True. The FAA halted departures at every airport in the country after a communications failure at air traffic control centers. The FAA itself called it a "temporary telecommunications issue". Details are in our separate fact check.^[1][3]

Partly. Reuters reported that the weather service announced nationwide internet and communications problems. But that same evening the weather service posted on X that its radars were working normally and that "outdated material from individual pages" was circulating online. A local service representative called the problems regional and the rumors of a nationwide outage untrue.^[4][5]

There was an outage, but the numbers are inflated. The Microsoft 365 outage began on November 12 at 18:26 UTC and lasted about 21 hours; it disrupted companies, government agencies and banks that use Outlook and Teams. Microsoft blamed part of its servers being unavailable and found no signs of a cyberattack. We did not find the "7.4 million reports" figure in any source.^[8][17]

Not supported. US Secretary of Homeland Security Markwayne Mullin: "I see no reason to link them… these are separate issues." Microsoft on X: there are no signs the FAA ground stop is related to its services. According to Bloomberg, the FBI is looking into a software update at the FAA itself. Verizon says its network is working. No one has named a common source for the outages.^{[6][14][7][9]}

No. The November 17 rumor appeared on October 31 in an anonymous post with no evidence — long before these outages. The only real event on November 17 is a test of the US emergency alert system at around 2:20 p.m. New York time: a one-minute signal on radio and TV that does not affect the internet or banks.^[2][10][11]

No. No accounts were frozen or wiped on November 12 or 13: because of the Microsoft outage, some banks lost email and internal chats, not customers' money. Wiping all accounts at once is technically impossible: balance data is stored in several copies. No bank or regulator has warned of anything like this.^[18][17][11]

An anonymous post: a global cyberattack will start on November 17, accounts will be wiped, the internet will be shut down for three months. This rumor is fact-checked in a separate article.^[11]

At 18:26 UTC a Microsoft 365 outage begins: Outlook, Teams, Copilot. It lasts about 21 hours; Microsoft finds no signs of a cyberattack.^[8]

At around 20:54 UTC the FAA halts departures at all US airports due to a communications failure at air traffic control centers.^[3][1]

Around 22:13 UTC: the National Weather Service reports internet and communications problems across the country.^[4]

Around 23:14 UTC: radars are working normally, outdated material is circulating online; a local representative says the problems are regional.^[5]

Homeland Security Secretary Mullin calls the FAA and Microsoft outages "separate issues"; Microsoft posts on X that there are no signs of a link to its services.^[6][14]

A Bloomberg source: the FBI is checking whether a software update caused the FAA outage and does not consider it a cyberattack or a crime.^[7][15]

Russian-language channels retell Reuters and list the FAA, weather service and Microsoft outages side by side, noting that a link is "not yet known".

A nationwide test of the US emergency alert system on radio and TV is scheduled for around 2:20 p.m. New York time.^[2][10]

Homeland Security Secretary Markwayne Mullin: the FAA ground stop and the Microsoft outage are "separate issues".^[6]

Microsoft on X: "No indication that the nationwide FAA ground stop is related to any Microsoft services."^[14]

The FBI is checking whether a software update caused the FAA outage; it does not suspect a cyberattack or a crime.^[7][15]

Weather service: radars are working, rumors of a nationwide outage are untrue, the problems are regional.^[5]

Looks at whether the FAA and Microsoft outages are linked: officials call them separate, and the FAA outage was a telecommunications issue.^[16]

The Microsoft 365 outage began on November 12 at 18:26 UTC; the cause was part of the servers being unavailable, with no signs of a cyberattack.^[8]

A survival website: "Three major outages in two days" — but it admits there is no confirmed link between them.^[19]

A retelling of Reuters on the FAA, with an add-on about the weather service and Microsoft and the phrase "not yet known whether they are linked": no direct claim of a link, but a nudge toward one.

2026-11-13

Microsoft: no signs that the FAA ground stop is linked to its services.^[14]

2026-11-13

Outcome: A faulty CrowdStrike security software update; there was no cyberattack.^[12]

Outcome: An internal technical failure in one AWS region; outages like this happen regularly.^[13]