In five days, three pillars of American life stopped working. On Thursday, Nov. 12, Microsoft Outlook went down worldwide, drawing more than 43,000 problem reports from 72 countries by the next morning in an outage that ran past 12 hours. On Friday, the FAA halted every departure in the country for more than four hours after its communications network failed; nearly 12,000 flights were canceled and the backlog was still felt days later. On Monday, customers of Chase, Bank of America, Wells Fargo, U.S. Bank and Truist found themselves locked out of online banking, with Chase alone drawing more than 5,000 outage reports by early afternoon.
Each organization was quick to say what it was not: an attack.
Microsoft: “There is no indication this is the result of malicious or cyber activity.” Chase: “This is a technical issue, not cyber related.” Homeland Security Secretary Markwayne Mullin said there was no indication of a “nefarious attack” on the FAA.
But look at what each one describes. Transportation Secretary Sean Duffy said, “Our switches, our routers, actually got overloaded with data,” after a newly installed router fired roughly 1,000 connection attempts every four to five seconds. A flood of requests overwhelming network equipment until legitimate traffic cannot get through is not merely similar to a denial-of-service attack. It is the textbook definition of one. FAA Administrator Bryan Bedford has said that explanation does not fully account for the root cause. Microsoft has blamed a network upgrade but has not published a full post-incident report. Chase has not said what its “technical issue” was.
Services unreachable. Systems saturated. Recovery measured in hours. No root cause disclosed. No cyberattack here. Easy to say, but in reality it looks like a duck, walks like a duck and quacks like a duck…
Then there is the timing. Any one of these failures, on its own, could be bad luck. Three across cloud software, aviation and banking in five days is a pattern, and in any other security context a pattern triggers an investigation, not a press release. “No indication” on day one is not the same as “ruled out” after forensics. On the day of the FAA failure, officials initially declined to rule out a cyberattack. That was the right instinct. Days later, with the FBI involved, it has not been ruled out.
There is a reason the word DDoS rarely appears in early statements. A “technical issue” is a maintenance problem. An “attack” is a disclosure event: regulators, investors and customers all ask how it got through. Every incentive points to the first label, whether or not anyone acts on it.
DDoS, distributed denial of service, is a leading threat to the availability of any publicly accessible online service. Every bank, airline and cloud provider runs hundreds or thousands of services, and each is a potential target.
For everyone else, the cause matters less than the impact. An hour offline costs the same whether a router misfired or a botnet fired. A DDoS attack is the cheapest, most repeatable way for an adversary to buy that hour. For a bank, it means frozen payments, regulatory notifications and customers wondering where else to keep their money. Every executive should be asking one question this week: if someone tried, would ours hold?
Most cannot answer it. My company, MazeBolt, provides DDoS resilience certainty to our customers. We commissioned a survey of 300 chief information security officers at banks, insurers and payment providers, and 86% test their DDoS defenses once a year or less. Only 5% are fully confident those defenses would stop an attack. In my experience, reality tends to shock those who think a few tests a year are enough. In our first validations of enterprise production environments, an average of 37% of attack vectors got through protection already in place and believed sound. An enterprise that cannot vouch for what it has bought is carrying risk it has never measured.
No one in the value chain will tell you that. The mitigation vendor reports what its system sees, not what it misses. The cloud provider’s contract covers its infrastructure, not your configuration. The auditor confirms a control exists, not that it works on the day it is needed. Each answers its own question honestly. None answers yours.
In the era of AI-orchestrated attacks, we’re seeing the length of DDoS attacks increase, and we’re certain to see additional shifts from the attackers’ side. What about those putting security measures in place? To deal with the new reality, organizations will need to proactively map out their vulnerabilities and strive towards proper resilience.
Boards should stop asking whether they own DDoS protection. Nearly every large enterprise does. They should demand evidence of DDoS resilience certainty, gathered continuously in production, across the entire attack surface. That certainty is what will keep payments flowing, planes moving and customers logged in. Organizations that hold it will spend the next bad week reading the headlines instead of appearing in them.
The opinions expressed in Fortune.com commentary pieces are solely the views of their authors and do not necessarily reflect the opinions and beliefs of Fortune.

