Innovation & Tech

Three service outages in five days test the DDoS narrative

Three outages in five days disrupted Outlook, U.S. flights and online banking. As attack questions remain open, a MazeBolt survey exposes executives’ limited confidence in DDoS defenses.

By Nathan Brooks

5 min read

If it looks like a DDoS attack
If it looks like a DDoS attackBru-nO / pixabay

What's News

  • Nov. 12, 2026: Microsoft Outlook’s worldwide outage ran past 12 hours and drew more than 43,000 reports from 72 countries.
  • Nov. 13, 2026: The FAA halted every U.S. departure for more than four hours, canceling nearly 12,000 flights.
  • Nov. 16, 2026: Chase, Bank of America, Wells Fargo, U.S. Bank and Truist customers reported online-banking lockouts; Chase drew more than 5,000 reports.
  • MazeBolt’s survey of 300 CISOs found 86% tested DDoS defenses annually or less, while only 5% were fully confident in them.
  • MazeBolt said an average 37% of attack vectors got through existing protections in its first enterprise production validations.

By Nathan Brooks

Nearly 12,000 U.S. flights were canceled after the FAA halted every departure for more than four hours on Friday, Nov. 13, 2026, according to NBC News. The disruption followed a worldwide Microsoft Outlook outage and preceded online-banking lockouts at five named U.S. banks.

In a commentary, Matthew Andriani, writing from MazeBolt, a provider of DDoS resilience services, grouped the failures as a five-day pattern across three pillars of American life.

The five-day outage sequence

  • Al Jazeera reported that on Thursday, Nov. 12, Microsoft Outlook went down worldwide. By the next morning, the outage had drawn more than 43,000 problem reports from 72 countries and had run past 12 hours.
  • On Friday, Nov. 13, the FAA halted every departure in the country for more than four hours. Nearly 12,000 flights were canceled, and the resulting backlog remained days later.
  • On Monday, Nov. 16, customers of Chase, Bank of America, Wells Fargo, U.S. Bank and Truist reported being locked out of online banking. Chase alone had drawn more than 5,000 outage reports by early afternoon.

The overload evidence

Microsoft said: “There is no indication this is the result of malicious or cyber activity.” Chase said: “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.

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. Andriani said the resulting flood overwhelmed network equipment until legitimate traffic could not get through.

Andriani argued that this mechanism fits the textbook definition of a distributed denial-of-service attack. His case rested on the overload mechanism, not an identified attacker. FAA Administrator Bryan Bedford said Duffy’s explanation did not fully account for the root cause.

Microsoft blamed a network upgrade but had not published a full post-incident report, Andriani wrote. Chase had not explained its “technical issue.” Andriani described the common symptoms as unreachable services, saturated systems and recovery measured in hours.

Why attribution remains unresolved

According to Andriani, officials initially declined to rule out a cyberattack on the day of the FAA failure. He called that the right instinct and said “no indication” on day one differs from “ruled out” after forensics. Days later, with the FBI involved, a cyberattack had not been ruled out.

Andriani said three failures across cloud software, aviation and banking in five days form a pattern that would trigger an investigation in another security context, not merely a press release. He argued that the language carries disclosure consequences. Calling an event a “technical issue” frames it as maintenance, while calling it an “attack” makes it a disclosure event for regulators, investors and customers.

Those incentives favor the maintenance label even if nobody acts on it, Andriani said. He defined DDoS, or distributed denial of service, as a leading threat to the availability of any publicly accessible online service. He said banks, airlines and cloud providers run hundreds or thousands of services, making each one a potential target.

Would your systems hold if someone tried?

For a bank, the impact goes beyond an inaccessible website. Andriani said an outage can freeze payments, trigger regulatory notifications and leave customers asking where else to keep their money. He also argued that an hour offline costs the same whether a router misfired or a botnet fired. In his view, DDoS is the cheapest, most repeatable way for an adversary to buy that hour.

Andriani said most executives could not answer the readiness test. His practical question was whether a system would hold if someone tried, and he said organizations often could not substantiate the answer.

MazeBolt commissioned a survey of 300 chief information security officers at banks, insurers and payment providers. The company found that 86% test their DDoS defenses once a year or less, while only 5% are fully confident those defenses would stop an attack.

In its first validations of enterprise production environments, MazeBolt found an average of 37% of attack vectors got through protections already in place and believed sound. That is nearly two in five vectors. For Andriani, an enterprise unable to vouch for purchased protection carries risk it has never measured.

Evidence boards should demand before the next outage

Andriani said the accountability chain leaves gaps at every layer. A mitigation vendor reports what its system sees, not what it misses. A cloud provider’s contract covers its infrastructure, not the customer’s configuration. An auditor confirms that a control exists, not that it works on the day it is needed.

Andriani said he was seeing DDoS attacks grow longer with AI orchestration and expected further shifts on the attackers’ side. He urged organizations to map vulnerabilities proactively and build greater resilience.

He said nearly every large enterprise already owns DDoS protection. His board-level prescription was to demand continuous evidence of resilience in production across the entire attack surface, rather than merely confirm that protection has been purchased. He said that certainty is what keeps payments flowing, planes moving and customers logged in.

The next bad week will separate companies that can prove their systems withstand sustained traffic floods from those still relying on annual tests, contractual assurances and a technical explanation. For boards, that evidence is the difference between reading the outage headlines and appearing in them.

Source: fortune.com

Share this article:

More from Nathan Brooks

Nathan Brooks

Show full bio

News editor covering regulation, policy and their impact on entrepreneurship, startups and venture funding at Business Bearings.

2,352 articles

Related articles

« Previous articleNext article »