LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Developing stories › The November 2026 outages

Developing story

Was it a hack? The week of outages, 12-16 November 2026

Published 17 Nov 2026 · last updated 17 Nov 2026. Each fact below links to its source.

The short answer

As of 17 November, nobody investigating the FAA ground stop, the Microsoft 365 outage, the Chase disruption or United’s delays had found a cyberattack behind them. The FAA says it has no indication of one, Microsoft says its outage was a technical issue, Chase says its problem was not cyber-related, and United says there was no indication of a cybersecurity issue. — FAA, 15 Nov; SecurityWeek, 16 Nov; WAFF, 17 Nov; TIME, 16 Nov

Two questions were open on that date: the FAA had not named a root cause, and Microsoft had published only a preliminary post-incident report, with the final one due by 20 November according to Office Watch. What is confirmed is a phishing campaign that used the Microsoft outage as bait. — CNBC, 14 Nov; Office Watch, 16 Nov; SecurityWeek, 16 Nov

If an email offers to restore mail held during the Microsoft outage, do not click: that is the phishing campaign Microsoft found, and it quotes a real incident number. — SecurityWeek, 16 Nov

What to do ↓ · What it means for you, and the scams to ignore, on GalaxyWarden →

Timeline

  1. Exchange Online (Outlook mail) fails worldwide. Teams, SharePoint, OneDrive, Copilot and Defender are affected in the parts that rely on it, though most of those services largely stay online. The preliminary report puts the end of the incident at 16:10 UTC on 13 November. — Office Watch, 16 Nov
  2. The FAA has a technical problem that leads to a nationwide ground stop. Air traffic resumes at 8:15 p.m. ET. CNBC reports it as the longest pause on departures in 25 years and only the second nationwide ground stop since 9/11. — FAA, 15 Nov; CNBC, 14 Nov
  3. Homeland Security Secretary Markwayne Mullin says it did not appear to be a cyberattack but officials were not ruling one out, and that NSA, DoD, CISA, FEMA and other agencies worked the issue. He says there is no connection to the Microsoft outage. — Nextgov/FCW, updated 14 Nov; CBS News, updated 14 Nov
  4. Microsoft Threat Intelligence first detects phishing emails that use the outage as a lure. — SecurityWeek, 16 Nov
  5. FAA Administrator Bryan Bedford says: “We couldn’t explain the instability.” CNBC reports that a definitive cause had not been established as of that afternoon. At a briefing Bedford says the White House Situation Room and national security agencies were activated, the FBI was at facilities, and officials concluded it was not a cyber issue. — CNBC, 14 Nov; Fortune via Yahoo News, 14 Nov
  6. L3Harris says it is supporting the FAA investigation and that, with its telecom partners, it has completed more than 70% of the planned copper-to-fiber conversion. — L3Harris, 14 Nov
  7. The FAA’s question-and-answer page on the ground stop sets out its initial findings (below). — FAA, 15 Nov
  8. Microsoft releases a preliminary post-incident report, dated 15 November, in the Microsoft 365 admin center under incident IDs MO1550821 and EX1550543. Its status account announces it early on 16 November, UTC. — Microsoft 365 Status on X, 16 Nov; Office Watch, 16 Nov
  9. Chase customers report online-banking problems: by 2 p.m. ET nearly 4,800 users had reported problems with Chase on Downdetector, and user complaints also spiked at Bank of America, Wells Fargo, U.S. Bank and Zelle. — CBS News, 17 Nov
  10. Chase says transactions are posting normally again by about 6:30 p.m. ET. Separately, United Airlines resolves a technology issue that delayed departures, with almost 600 flights delayed per FlightAware. — Al Jazeera, 17 Nov; TIME, 16 Nov
  11. Downdetector shows service back to normal at the banks and Zelle early on Tuesday. — CBS News, 17 Nov

What officials and the companies have established

  • FAA: its legacy equipment became unstable when data flooded the FAA Telecommunications Infrastructure network at 1,000 connection attempts every 4 to 5 seconds, disrupting communications and radar feeds at 17 of its 22 Air Route Traffic Control Centers and spreading into several approach-control facilities. — FAA, 15 Nov
  • FAA: its initial investigation points to two potential sources, a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas. L3Harris, its network service provider, had been working at the El Dorado site, including deploying a new router. Blocking the two sites stabilised the network; the FAA then disabled the problem function on those routers and on about 60 similar ones. — FAA, 15 Nov
  • FAA: asked directly, it says that on all available evidence it has no indication of a cyberattack or an outside nefarious actor. It also says its SMART system and wider modernisation work did not cause the disruption, which it attributes to the legacy TDM system. — FAA, 15 Nov
  • FAA: about 3,500 aircraft landed safely and some radio frequencies and radar feeds stayed up, so it was not a full outage. It counts about 12,462 cancellations on 13 November, 9,082 of them by major airlines, and notes not all were caused directly by the ground stop. — FAA, 15 Nov
  • Microsoft: a technical issue, not related to cyberattacks or to AI agents, traced to an earlier network capacity upgrade whose problem surfaced after a later network change. — SecurityWeek, 16 Nov
  • Microsoft’s preliminary report, as summarised by Office Watch: a latent defect in a Windows fix on networking gateway servers, Teams traffic moved onto the gateway shared with Exchange Online about 15 hours earlier, and roughly 14% of gateway capacity already offline. At the worst point more than 80% of servers were unresponsive. — Office Watch, 16 Nov
  • Chase: a temporary issue caused by a software bug in on-premise hardware systems, “not cyber related”. Customers kept access to their accounts and funds while some transactions took longer than usual. — WAFF, 17 Nov
  • Chase: the bug affected other institutions “when we were party to a transaction involving other banks”, and the issue was not systemic. Bank of America told CBS its systems were operating normally, U.S. Bank said it was not directly affected though Zelle payments to or from other banks might be delayed, Capital One said it was not affected, and Zelle said its service was operating as it should. — CBS News, 17 Nov
  • United Airlines: a technology issue, resolved the same evening, with flights in the air and the regional network unaffected and no indication it was cybersecurity-related. — TIME, 16 Nov

What has not been established

As of 17 November 2026.

  • The FAA’s root cause. On 14 November Transportation Secretary Sean Duffy said officials had not yet determined whether it was user error, an installation error by L3Harris, or a faulty router. — Nextgov/FCW, updated 14 Nov
  • Which site was the trigger. The FAA names both Amarillo and El Dorado as potential sources. — FAA, 15 Nov
  • Any fault finding against L3Harris or any equipment maker. L3Harris has made no admission, and officials had not determined fault as of 14 November. — L3Harris, 14 Nov; Nextgov/FCW, updated 14 Nov; CNBC, 14 Nov
  • Microsoft’s final root cause. As of 17 November only the preliminary report, dated 15 November, was out, and the details above come from it as summarised by a third party. Office Watch said the final report was due by 20 November. — Office Watch, 16 Nov
  • Whether Wells Fargo had an outage, and why. It has given no detailed public explanation, and it is unclear whether its problems and Chase’s shared a cause. — Fortune, 16 Nov
  • That Capital One had an outage. Some coverage lists it; Capital One said it was not affected. — CBS News, 17 Nov
  • Whether every problem reported at other banks came from Chase’s bug. Chase says the bug affected other institutions when it was party to a transaction with them; it has not said that this explains every report, and no other bank has said its own reports came from it. — CBS News, 17 Nov; Fortune, 16 Nov
  • Any common cause or coordination. No official has linked the outages, and the Homeland Security Secretary said the FAA and Microsoft events were unconnected. — CBS News, updated 14 Nov
  • Any statement from a bank regulator (OCC, Federal Reserve, CFPB). None found as of 17 November.
  • Any link to ARTEX, the AI intrusion framework in the news the same week. No source connects them.

The scam that did follow

Outage or breach: how the statements differ

Separate security incidents that week

These were security incidents. No source links any of them to the outages above.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Breaches linked to these outages

None. As of 17 November no data breach is linked to these outages: every organisation involved puts its disruption down to a technical cause, and we do not list their older, unrelated breach records here. — FAA, 15 Nov; SecurityWeek, 16 Nov; WAFF, 17 Nov; TIME, 16 Nov

What to do

Separate from the outages: check your exposure
Free: the scan checks your email against known breach records and look-up sites. It cannot tell you anything about these outages, and we can’t confirm any single incident against the sources we search.
Check if you’re exposed →

What it means for you, and the scams to ignore, on GalaxyWarden →

Sources

  1. FAA — the FAA’s account of the ground stop · Nationwide Ground Stop: Questions and Answers · 15 Nov 2026 · Official statement
  2. SecurityWeek — Microsoft’s cause and the outage phishing campaign · 16 Nov 2026 · Reporting
  3. WAFF — a Chase spokesperson’s explanation · 17 Nov 2026 · Reporting
  4. TIME — on the United Airlines outage · 16 Nov 2026 · Reporting
  5. CNBC — on the root cause being unknown · 14 Nov 2026 · Reporting
  6. Office Watch — a summary of Microsoft’s preliminary post-incident report (dated 15 Nov) · 16 Nov 2026 · Reporting
  7. CNBC — on flights resuming after the ground stop · 14 Nov 2026 · Reporting
  8. Nextgov/FCW — on officials’ statements, first published 13 Nov · updated 14 Nov 2026 · Reporting
  9. CBS News — on the ground stop and the DHS Secretary’s remarks · updated 14 Nov 2026 · Reporting
  10. Fortune via Yahoo News — on the 14 November FAA briefing · 14 Nov 2026 · Reporting
  11. L3Harris — L3Harris’s statement · 14 Nov 2026 · Official statement
  12. Microsoft 365 Status on X — Microsoft’s official status account, on the preliminary report · 16 Nov 2026 · Official statement
  13. CBS News — on the bank disruptions · 17 Nov 2026 · Reporting
  14. Al Jazeera — on Chase transactions resuming · 17 Nov 2026 · Reporting
  15. Fortune — on the bank outages and Wells Fargo · 16 Nov 2026 · Reporting
  16. Microsoft Threat Intelligence on X — Microsoft Threat Intelligence’s own post on the outage phishing campaign · 14 Nov 2026 · Official statement
  17. KPTV — on scam warnings after the bank outage · 17 Nov 2026 · Reporting
  18. ABC11 — on why not every outage is an attack, and scam warnings · 17 Nov 2026 · Reporting
  19. A.P. Moller-Maersk — Maersk’s incident notice · 11 Nov 2026 · Official statement
  20. Microsoft Security Response Center — Microsoft’s CVE entry · CVE-2026-124194, Microsoft Outlook Spoofing Vulnerability · 10 Nov 2026 · Official statement
  21. CISA — the KEV listing · Known Exploited Vulnerabilities catalog · 10 Nov 2026 · Official statement
  22. BleepingComputer — reporting the WhiteArmor group’s claims about Maersk · 11 Nov 2026 · Attacker claim, unverified
  23. ConnectWise Trust Center — ConnectWise’s ScreenConnect advisory, first published 11 Nov · ScreenConnect security advisory: Precautionary extension disabling and partner guidance · updated 16 Nov 2026 · Official statement
  24. BleepingComputer — on the ScreenConnect partner-account abuse · 11 Nov 2026 · Reporting
  25. FTC consumer advice on scam texts — recognising and reporting scam texts · Official statement
  26. eCFR — the federal refund rule · 14 CFR 260.6 · Official statement
  27. Chase Security Center — Chase’s standing security guidance · Official statement
  28. FBI Internet Crime Complaint Center — where to report cybercrime · ic3.gov · Official statement
  29. FTC consumer advice on identity theft — what to do about identity theft · Official statement

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

AICompiled with AI assistance from public sources and published under our editorial standards.

ShareXLinkedInFacebookRedditWhatsAppTelegram