🔍 Read the full analysis: Is This A Cyberattack? A Week Of Outages And Breaches, And What Actually Caused Them on ThorstenMeyerAI.com
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
As of 09:40 UTC on Nov. 15, officials and companies had attributed a Microsoft 365 outage and a nationwide FAA ground stop to technical and maintenance problems, with no evidence of cyberattacks reported for either. Five other incidents involved confirmed attacks or data theft, including exploitation of a Microsoft Outlook flaw and breaches involving vendors. Investigations and post-incident reports are still pending.
Two major disruptions this week — a Microsoft 365 outage and a nationwide U.S. flight ground stop — have been attributed by the companies and officials involved to technical problems, with no evidence of an attack reported so far. Separately, five other incidents involved confirmed exploitation, unauthorized access or data theft, according to the accounts summarized by ThorstenMeyerAI.com on Nov. 15. Investigations into the outage causes are not complete.
Microsoft said its Microsoft 365 disruption, which affected access to Exchange Online mailboxes from Nov. 12 to 13, followed traffic shifts during network maintenance and upgrades. Those shifts exposed a latent bug that prevented systems from completing new connection requests, according to the company’s revised preliminary explanation. Microsoft changed both its explanation and the recorded start time as it investigated: the status record now gives a start time of 16:20 UTC on Nov. 12 and an end time of 16:10 UTC on Nov. 13.
The FAA ground stop on Nov. 13 lasted about four hours and 23 minutes, based on the event times in the agency’s advisories. Transportation Secretary Sean Duffy said a contractor was replacing telecommunications equipment as a remote site moved from copper lines to fiber. He said a router began flooding other routers in the air traffic control system, but added that officials had not determined whether the fault was contractor error or defective equipment. The FAA’s written statement continued to say technicians were investigating.
The week’s other five incidents were distinct from those outages. The source’s review says Microsoft and the U.S. Cybersecurity and Infrastructure Security Agency listed an Outlook flaw as exploited; attackers accessed unpatched Check Point gateways; Uber driver data was taken using a vendor’s stolen credentials; Osaka users’ email addresses were obtained through a vendor’s vendor; and three Trezor wallets bought from one reseller contained implants. The available material does not provide the full dates, scope or investigative records for each case, so those details cannot be independently compared here.
The week of November 9 to 15, 2026
Two outages, five attacks, one question
Each incident we covered this week, sorted by what the companies and officials responsible have said so far.
Day by day
- Nov 10Outlook flaw: Microsoft and CISA list it as exploited
Attack - Nov 10Uber notice: a vendor’s stolen credentials were used
Attack - Nov 12Check Point: unpatched gateways broken into
Attack - Nov 12Trezor: implants in wallets bought from one reseller
Attack - Nov 12 to 13Microsoft 365 outage: network maintenance exposed a bug, Microsoft says
Change / maintenance - Nov 13FAA ground stop: router swap during routine work, officials say
Change / maintenance - Nov 13Osaka: email addresses leaked through a vendor’s vendor
Attack - Nov 15Microsoft’s report and a written FAA account: still pending
Open
The tally
AttackConfirmed by the company or agency
Change / maintenanceNo evidence of an attack so far
OpenReports still to come
Sources: Microsoft service health records and status page (Nov 12 to 15); FAA statement and Command Center advisories (Nov 13); Transportation Secretary Sean Duffy and FAA Administrator Bryan Bedford, news conference of Nov 14, as reported by Fox Business, MS NOW and CNN; Microsoft Security Response Center and CISA (Nov 10); Uber notice dated Nov 10; Check Point (Nov 12); Trezor (Nov 12); City of Osaka (Nov 13). Tags are our summary of those statements, as of 09:40 UTC, Nov 15, 2026.
Graphic: Powered by Thorsten Meyer AI
Outages and Breaches Had Different Causes
The week’s events show why a cluster of disruptions is not, by itself, evidence of a single coordinated cyberattack. The two highest-profile outages were attributed to network changes and maintenance work; the separate security incidents involved routes such as exploited software flaws, compromised vendor credentials and a compromised supply chain. The causes matter because they point to different ways organizations may reduce risk.
For users and businesses, the distinction affects what to watch for and what questions to ask. A technical outage can interrupt essential services without an attacker being involved, while an incident at a supplier can expose data even when the affected organization’s own systems were not the entry point. The reported cases also underline that routine operational work and third-party relationships can carry security and reliability risks. These are lessons from the reported incidents, not evidence that the events shared a cause.
Products Worth Considering

LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1, Black

Ledger Stax Crypto Wallet with Touchscreen

Ledger Flex + Folio Crypto Hardware Wallet
As an affiliate, we earn on qualifying purchases.
How the Explanations Changed
Microsoft’s first public updates did not identify a recent change correlated with the start of its outage. The company later said it was reverting a network configuration change, then stated that it had no indication of malicious activity. Its Nov. 15 status record offered a more detailed preliminary explanation involving traffic shifts, maintenance and an exposed latent bug. Microsoft said it would publish a preliminary post-incident report within two business days and a final report within five business days.
The FAA account also became more specific over time. Duffy initially cited old, overloaded telecommunications equipment, then described the contractor’s copper-to-fiber work and the router failure. FAA Administrator Bryan Bedford said the agency had found no evidence of anything nefarious or AI-related, according to CNN. The FAA’s written statement remained limited to saying technicians were investigating when checked on Sunday. L3Harris said it was supporting that investigation, according to the source report.
Those shifting accounts are why this report distinguishes current explanations from final findings. The information is based on official statements, company status updates and media reports identified by ThorstenMeyerAI.com, checked at 09:40 UTC on Nov. 15. It does not establish that all seven incidents were connected.
“We’re still looking, so we’re not going to rule that out.”
— Homeland Security Secretary Markwayne Mullin, at a Friday White House briefing
Investigations Have Not Closed
Neither outage has a final public root-cause report in the material reviewed. Microsoft’s account remains preliminary, with two post-incident reports still expected. The FAA has not published a detailed written account, and officials have not said whether the router problem resulted from a faulty device, human error or another cause.
Officials and Microsoft reported no evidence of a cyberattack behind the two outages at the time of the Sunday check. That is not the same as a final determination that an attack was impossible: Mullin said the possibility had not been ruled out, and the investigations remained open. The source also does not provide enough detail to independently verify the scope or attribution of each of the five other incidents.
Reports and FAA Findings Ahead
Microsoft said it expected to issue a preliminary post-incident report within two business days and a final report within five business days. Those reports may clarify the outage timeline, the role of maintenance and network changes, and the steps the company plans to take.
The FAA and L3Harris were still investigating the ground stop as of Sunday morning. A fuller written account is needed to identify the failure mechanism and explain how the router affected the wider air traffic control network. Until those findings are released, the causes described by Duffy and Microsoft should be treated as the latest available explanations, not final conclusions.
Key Questions
Were the Microsoft 365 outage and FAA ground stop cyberattacks?
No evidence of an attack had been reported for either incident as of 09:40 UTC on Nov. 15. Microsoft attributed its outage to a network bug exposed during maintenance and upgrades. FAA officials described a router problem during telecommunications work, while the investigation remained open.
What caused the Microsoft 365 outage?
Microsoft’s revised preliminary account says traffic shifts during standard network maintenance and upgrades exposed a latent bug that prevented new connection requests. The company said it planned to issue post-incident reports, so the explanation was not yet final.
Why were U.S. flights grounded on Nov. 13?
Transportation Secretary Sean Duffy said a router began flooding other routers during a contractor’s work to replace telecommunications lines as a site moved from copper to fiber. He said officials had not determined whether contractor error or faulty equipment caused the problem.
Were there confirmed cyber incidents during the same week?
Yes. The source report describes five separate incidents involving exploitation of an Outlook flaw, access to unpatched Check Point gateways, stolen vendor credentials, a vendor’s vendor and implanted hardware in three Trezor wallets. They were separate events from the two outages; the report does not establish a common cause.
What information is still expected?
Microsoft said preliminary and final post-incident reports were due within two and five business days, respectively. A detailed FAA account was also pending, including a determination of what caused the router failure.
Source: ThorstenMeyerAI.com
