🔍 Read the full analysis: This Week’s AI Outages And Breaches: What Actually Went Wrong? on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
As of 09:40 UTC on Nov. 15, Microsoft attributed its Microsoft 365 outage to a latent bug exposed during network maintenance, while U.S. officials linked a nationwide FAA ground stop to a router problem during a contractor’s routine work. Officials said they had found no evidence of attacks behind either outage; five other incidents involved exploited software flaws, stolen vendor credentials or compromised devices. Final reports on the two outages are still pending.
Microsoft’s Microsoft 365 outage and a nationwide FAA ground stop were attributed to technical problems, not identified attacks, in explanations available by Sunday, Nov. 15. The same week also brought five separate confirmed security incidents involving exploited software, stolen credentials, a vendor breach and tampered hardware, making it important to distinguish service failures from cyberattacks.
Microsoft said its Nov. 12–13 outage, which prevented many users from accessing Exchange Online mailboxes and affected services that rely on them, resulted when traffic shifts during network maintenance and upgrades exposed a latent bug. Its explanation changed as the company investigated. On Thursday, it said it had not identified a recent change linked to the impact; later, it said it was reverting a network configuration change. By Friday, Microsoft said the problem was technical and unrelated to cyber activity or AI agents. A revised status post available Sunday gave the more detailed preliminary cause.
The FAA ground stop on Nov. 13 lasted about four hours and 23 minutes, based on the times in the agency’s advisories. Transportation Secretary Sean Duffy said a contractor was switching telecommunications lines from copper to fiber at a remote FAA site when a router began flooding other routers in the air traffic control system. He said officials had not determined whether the cause was contractor error or faulty equipment. The FAA’s written statement still said technicians were investigating.
The five other incidents were distinct from those outages: Microsoft and the U.S. Cybersecurity and Infrastructure Security Agency listed an Outlook flaw as exploited; attackers breached unpatched Check Point gateways; Uber driver data was accessed using a vendor’s stolen credentials; Osaka users’ email addresses were exposed through a vendor’s vendor; and three Trezor wallets bought from one reseller contained implants. The source account’s summary describes these as attacks or compromises, but does not provide enough detail to independently assess each incident’s scope.
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
Why Outages and Breaches Differ
The incidents show why a disruption and a breach should not be treated as interchangeable. The Microsoft and FAA explanations available Sunday point to maintenance, network changes and equipment problems; the other five cases involved security failures, including known software flaws and weaknesses in supplier relationships. Conflating them can confuse customers and the public about what happened and what response is needed.
For organizations, the pattern also highlights risks around ordinary operational work and outside providers. Network changes can have broad effects when systems depend on shared infrastructure, while vendor access and supply chains can create routes into customer or employee data. These are takeaways from the reported cases, not proof that every incident had the same cause or impact.
Public explanations matter as well. Microsoft’s account evolved over several updates, and the FAA had not yet published a detailed written explanation when checked. Initial assessments can change as investigators obtain more evidence. The current lack of evidence of an attack in either outage is not a final ruling that an attack was impossible.
Popular right now

iRobot Roomba 105 Robot Vacuum with LiDAR Navigation

De'Longhi La Specialista Touch Semi-Automatic Espresso Machine with Grinder

De'Longhi Classic Signature Espresso Machine with Adjustable Milk Frother
As an affiliate, we earn on qualifying purchases.
Seven Incidents, Separate Causes
The account published by ThorstenMeyerAI.com groups seven incidents reported during the week: two service disruptions and five security incidents. Its status check was at 09:40 UTC on Sunday, Nov. 15, 2026. It relies on statements and status pages from the named companies and agencies, along with attributed media reports; the account does not present a single shared investigation linking the events.
Microsoft’s explanation developed between Thursday and Sunday. The company first said it had not found a recent change correlated with the outage, then described reverting a network change, and later identified traffic shifts during standard maintenance as exposing a latent bug. Microsoft said a preliminary post-incident report was due within two business days and a final report within five business days.
In the FAA case, officials first referred to old, overloaded telecommunications equipment before Duffy described the copper-to-fiber work and router issue. The FAA’s public written statement remained limited to saying technicians were investigating. The source says L3Harris was supporting that investigation. These accounts are preliminary and should not be read as completed findings.
“Traffic shifts during standard network maintenance and upgrades exposed a latent bug in which our systems were unable to complete new connection requests.”
— Microsoft, in its revised service status
Investigations Still Open
Neither major outage has a final published cause in the information available as of Sunday morning. Microsoft’s account is preliminary, with post-incident reports still expected. The FAA had not released a detailed written account, and Duffy said investigators had not determined what fault occurred during the contractor’s work.
Officials’ statements that they had found no evidence of malicious activity describe the evidence available at that time; they do not establish that an attack was conclusively ruled out. Mullin explicitly said the possibility was still being examined. The source material also does not specify the full number of users affected by the Microsoft outage, the full operational effects of the FAA stop, or the amount of data involved in each of the five security incidents.
The five incidents are summarized as confirmed attacks or compromises, but the available account gives limited information about discovery dates, affected populations, remediation and whether data was misused. No shared connection among the seven events is established by the cited material.
Reports and Findings to Come
Microsoft said it expected to issue a preliminary post-incident report within two business days and a final report within five business days. Those documents may clarify the outage timeline, the latent bug and the network changes involved.
The FAA and its contractor, L3Harris, are supporting an investigation into the router failure. A detailed written FAA account and a determination of whether the problem involved human error, equipment failure or another cause had not been published in the information checked Sunday. Until those findings arrive, the current explanation remains provisional.
For the five security incidents, the next useful updates would establish how many people or systems were affected, how access was gained, what remediation has been completed and whether any exposed information was used. The available source material did not give a timeline for those disclosures.
Key Questions
Were the Microsoft and FAA outages confirmed cyberattacks?
No attack was identified in the explanations available as of 09:40 UTC on Nov. 15. Microsoft attributed its outage to a network issue, and FAA officials said they had seen no evidence of malicious activity. Both investigations were still open, so those assessments were not final determinations.
What did Microsoft say caused its outage?
Microsoft’s revised preliminary explanation said traffic shifts during routine network maintenance and upgrades exposed a latent bug that prevented new connection requests. The company said its post-incident reports were still to come.
What caused the FAA ground stop?
Transportation Secretary Sean Duffy said a router began flooding other routers during contractor work to switch telecommunications lines from copper to fiber. He said officials had not determined whether the fault was human error or faulty equipment.
What were the five other security incidents?
The source account lists an exploited Outlook flaw, attacks on unpatched Check Point gateways, Uber driver data accessed through a vendor’s stolen credentials, Osaka users’ email addresses exposed through a vendor’s vendor, and three Trezor wallets bought from one reseller that contained implants.
When will more information be available?
Microsoft said its preliminary report was due within two business days and its final report within five business days. The FAA had not given a publication date for a detailed account, and the timing of further disclosures about the other incidents was not specified.
Source: ThorstenMeyerAI.com
