It has been a rough week for the systems we all depend on. On Thursday, Microsoft 365 went down around the world. On Friday, the Federal Aviation Administration ordered a nationwide ground stop. On Monday, JPMorgan Chase stumbled and took pieces of the rest of the banking system with it, while United Airlines held its planes at the gate. And on Tuesday, Apple services failed for millions of people — on the same day the National Security Agency’s classified internal network went dark.
When that many big systems fail in six days, the first question everyone asks is the obvious one: are we under a coordinated cyberattack? I went through what each organization has actually said about its own failure. So far, the answer is no — and the real explanation is less dramatic but, in its own way, more unsettling.
The week, day by day
Thursday, November 12 — Microsoft. Microsoft 365 — Outlook, Teams, SharePoint, Copilot — was disrupted across dozens of countries for the better part of a day, with problems lingering into the weekend. Microsoft later traced it to a faulty software update: a defective gateway fix it had shipped back in July, exposed when the company ran a network capacity upgrade.
Friday, November 13 — the FAA. The FAA ordered a rare nationwide ground stop — only the second since 9/11 — after trouble on the telecommunications network that supports air traffic control. The cause, by the reporting so far: a contractor’s upgrade for L3Harris, the FAA’s telecom provider, switching a remote site from copper to fiber, overloaded the legacy routers the system still runs on. Thousands of flights were delayed or canceled over the weekend. (Workday, the HR platform, was also down Friday into Saturday — its cause was a backup-test fault.)
Monday, November 16 — the banks and United. A software bug in JPMorgan Chase’s on-premise hardware slowed transactions online and in branches. Because banks constantly transact with each other, customers of Bank of America, Wells Fargo, U.S. Bank and Capital One also reported problems, as did users of Zelle — which said its own platform was operating fine. Chase said plainly there was no evidence the problem was cyber-related. The same day, United Airlines held departing flights for more than 90 minutes because pilots could not pull electronic weight-and-balance figures onto their cockpit tablets. United said there was no indication of a cybersecurity incident.
Tuesday, November 17 — Apple and the NSA. Apple’s outage began late in the morning, Eastern time: iCloud sign-in, the App Store, Apple Pay, Apple Music and AppleCare were disrupted, new iPhones and iPads could not be activated, and Apple retail stores reportedly could not complete sales — while Apple’s own status page initially showed green. By late afternoon Apple said the cause was an internal update and that it was not the result of a cyberattack. The same morning, the NSA’s classified internal network, NSANet, went down at Fort Meade, with staff arrivals staggered. The agency called it a “temporary degradation during scheduled routine maintenance” — patching — and said mission-critical capabilities remained fully operational.
So: attack, or accident?
The officials whose job is to know have been unusually direct. CISA has told the White House the outages are “all individually unrelated.” National Cyber Director Sean Cairncross said the FAA stop and Monday’s failures were “not any sort of coordinated, nefarious cyberattack.” Homeland Security Secretary Markwayne Mullin put it at “98 percent certainty” that there was no hack — although he also mused that rapidly advancing AI could be triggering a domino effect, a theory the security experts quoted this week have not endorsed.
Consider the NSA case on its own. NSANet is a closed, classified network, walled off from the public internet. Whatever went wrong at Apple or Chase could not have reached it. It broke during its own scheduled patching. That is hard to square with a coordinated external attack — and easy to square with the explanation every one of these organizations has given: they broke their own systems, mostly while trying to improve them.
Real cyberattacks do happen, and this week had those too — four separate incidents were disclosed by Optimizely, Ipsos, Infoblox and the energy company Equinor, all distinct from the outages. After this summer’s attacks on Minnesota water utilities, it is no wonder people are jumpy. But intrusions leave evidence — ransom demands, stolen data, forensic traces. None of that has surfaced in any of these six failures. What has surfaced, every time, is a change: an update, a patch, an upgrade, a maintenance window.
The pattern underneath
That is the common thread, and it is the part worth worrying about. Every stated cause so far is a software or network fault introduced by the operator itself: a bad fix shipped in July, a fiber upgrade that overwhelmed routers old enough to still have copper wiring in the plan, a bug in a bank’s own hardware, a backup test, routine maintenance at the NSA, an internal update at Apple. Security specialists quoted this week keep landing on the same point: there is no credible public evidence of coordination — the culprit is aging, underfunded, enormously complex infrastructure, where one organization’s glitch (Chase’s) instantly becomes everyone else’s problem because everything is connected to everything else.
The scary version of this story is a foreign attack that takes down banks, airlines and the NSA in a single week. The real version may be worse, because there is no adversary to deter: these systems are now so complex, and so dependent on constant updates, that they can do this to themselves on an ordinary Tuesday. The question worth asking the FAA, the banks and the rest is not whether they can stop a hacker. It is whether they can survive their own upgrades.
Sources: reporting by The Register, the Associated Press, and a running tally of each incident and its stated cause at MLQ.ai, November 12–17, 2026.
Photo: server racks at the National Energy Research Scientific Computing Center (NERSC). CC0, via Wikimedia Commons.