1. DHS rules out a coordinated attack
Homeland Security Secretary Markwayne Mullin said on November 16, 2026, that a run of failures at Microsoft, Chase and United Airlines was caused by new technology overloading outdated systems, not by hackers. Asked whether the Microsoft outage was a cyber attack tied to the other incidents, he put his confidence that they were unrelated at 98%.
Mullin made the remarks in a television interview, as public unease grew over a cluster of disruptions that hit office software, air travel and retail banking within days of one another. His message had two parts: the events were separate, and none of them showed signs of sabotage.
The assessment carries weight because of where it comes from. The Department of Homeland Security is the federal body charged with protecting critical infrastructure in the United States, including the networks that underpin aviation, finance and communications. When its secretary says investigators see no hostile hand behind a series of failures, that is the government's working position, even if it stops short of absolute certainty.
2. Was the Microsoft outage a cyber attack?
No, according to both the stated cause and the Homeland Security secretary. The Microsoft disruption was attributed to a software defect combined with difficulty handling demand on its servers, and Mullin said he saw no indication of sabotage in it or in the incidents that followed.
The failure struck Microsoft's 365 suite the week before Mullin spoke, interrupting services including the Outlook email client and the Teams collaboration platform for users around the world. Those products sit at the center of daily work for a vast number of companies, schools and public agencies, so an interruption is felt immediately and widely: messages stop arriving, meetings cannot be joined and shared documents become unreachable.
Cloud-based productivity software concentrates risk in a way that older, locally installed programs did not. When email and messaging ran on servers inside each organization, a failure affected one employer at a time. Now that the same functions are delivered from a provider's data centers to customers everywhere, a single fault can interrupt all of them simultaneously. The efficiency of the model and its fragility come from the same source.
That breadth is part of why suspicion of an attack arose so quickly. An outage that reaches users on several continents at once resembles, from the outside, what a successful intrusion into a major cloud provider might look like. The explanation offered was more mundane. A flaw in software, coinciding with trouble absorbing the load placed on servers, is the kind of internal fault that large computing platforms encounter from time to time, and it requires no outside actor.
3. A ground stop, a banking glitch and an airline failure
Air travel was the next system to seize up. On November 13, the Federal Aviation Administration ordered a nationwide ground stop after aging telecommunications hardware became overloaded, and thousands of flights were cancelled or delayed as a result.
A ground stop is among the bluntest tools available to aviation authorities: departures are held on the ground until controllers are satisfied that the system guiding aircraft is working safely. Applying it across the entire country is rare, and the knock-on effects last well beyond the order itself, because aircraft and crews end up in the wrong places and schedules take time to rebuild.
Banking followed on November 16. A software bug caused problems with transactions at Chase and at other banks, producing a series of temporary disruptions for customers. The issue was fixed the same day, and there was no indication of cyber activity behind it.
United Airlines reported an outage of its own on the same date, one that affected its departures for a short period before operations resumed. Unlike the other incidents, no specific technical cause was given for the airline's trouble.
Each event, in other words, came with its own trigger. Microsoft's was a software defect and server demand. The aviation shutdown traced back to overloaded legacy telecommunications equipment. The banking disruption came from a software bug. It is the absence of a shared mechanism, as much as the absence of evidence of intrusion, that supports the conclusion that the incidents were not a single coordinated campaign.
4. Why would new technology break old systems?
Mullin's diagnosis is that modern tools are being stacked on top of infrastructure that was never designed to carry them. He tied the strain to emerging technologies, a category that likely includes artificial intelligence, being layered onto systems built for a far lighter load.
The underlying problem is familiar to engineers under the name legacy infrastructure. Large organizations rarely replace their core systems outright, because doing so is expensive, risky and disruptive. Instead, they keep decades-old hardware and software running at the base and attach newer applications to it over time. The arrangement works until the newer layers ask more of the foundation than it can deliver.
Demand is the variable that changes fastest. Older equipment was sized for the volume of traffic, the number of connections and the pace of requests that were typical when it was installed. Newer software, and automated tools in particular, can generate requests at a rate and scale that those assumptions never contemplated. When capacity is exceeded, the result is not a graceful slowdown but an abrupt failure, and because so many services depend on the same underlying components, one overloaded element can halt everything built above it.
The aviation incident illustrates the pattern most plainly, since it was obsolete telecommunications hardware that gave way. But the same logic runs through the secretary's account of the corporate outages: systems that functioned for years began failing once they were asked to support something new.
5. What Mullin said about security
Reassurance was the central purpose of the secretary's appearance. Mullin said the homeland and the banking system remain secure, and he stressed that the failures showed no sign of having been engineered by an adversary.
His choice of a figure, 98%, is notable for what it leaves open. It signals strong confidence without claiming that every possibility has been excluded, which is consistent with how officials tend to speak while technical reviews are still under way. The remaining margin is an acknowledgment that conclusions about complex system failures are usually refined as more data comes in.
Public anxiety in moments like this tends to run ahead of the evidence. When unrelated services fail in quick succession, the natural instinct is to look for a single cause, and a hostile government or criminal group is the most dramatic candidate. Officials face a delicate task in response: speaking too soon risks being contradicted by later findings, while staying silent allows speculation to harden into assumption. By addressing the incidents together and stating a level of confidence, the secretary chose to confront the theory directly.
The distinction between an attack and an accident is more than semantic. If hostile actors were responsible, the appropriate response would involve law enforcement, intelligence agencies and possibly diplomatic or military channels. If the cause is worn-out infrastructure, the remedy is investment, engineering and better management of how new tools are introduced. Mullin's account places the recent incidents firmly in the second category.
6. Why the episode matters for finance and digital assets
For anyone who moves money, the sequence of events is a reminder that availability is itself a form of security. A bank account that cannot process a transaction for several hours, or an airline that cannot dispatch flights, imposes real costs on customers even when no data is stolen and no funds are lost.
The banking disruption on November 16 is the piece most relevant to financial markets. Payment systems are tightly interconnected, so a fault at one large institution can delay transfers that other firms, including brokerages and digital asset platforms, rely on to fund customer accounts and settle withdrawals. That the bug was corrected within the day limited the damage, but the incident showed how a single software error can ripple across institutions.
The episode also feeds a long-running debate about resilience. Advocates of decentralized networks often argue that systems without a single operator are harder to knock offline, while critics point out that most people still reach those networks through centralized companies, cloud providers and bank connections that share the vulnerabilities on display this month. The outages do not settle that argument, but they show why uptime has become a competitive and regulatory concern across the financial sector.
Artificial intelligence adds a further dimension. Banks, exchanges and payment firms are deploying automated tools at speed, and the secretary's explanation suggests that the infrastructure beneath those tools deserves as much attention as the tools themselves. Adding capability at the top of the stack without reinforcing the base is, on his account, precisely what has been going wrong.
7. The open questions
Several details remain unresolved. No technical cause has been set out for United Airlines' outage, and the individual explanations offered for the other incidents describe what failed more fully than why it failed at that particular moment.
The broader issue is whether the pressures Mullin described will ease or intensify. Organizations are continuing to introduce new technology, and the older systems underneath are not being replaced at the same pace. Until that gap narrows, the conditions that produced a week of failures across software, aviation and banking will remain in place, whatever the eventual findings on each individual event.
