If it looks like a DDoS attack
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.

TL;DR
- Microsoft Outlook, the FAA's communication network, and several major online banking services experienced major outages within a five-day span.
- Affected companies, including Microsoft and Chase, attributed the failures to technical issues or network overloads, explicitly denying cyberattacks.
- The described issues, such as overloaded routers and saturated systems, closely match the definition of a Distributed Denial of Service (DDoS) attack.
- The timing and nature of these failures suggest a pattern that warrants investigation beyond initial denials.
- A survey revealed that 86% of CISOs test their DDoS defenses annually or less, and only 5% are confident in their effectiveness.
- On average, 37% of attack vectors bypassed existing protection in initial validations of enterprise production environments.
- Organizations need to proactively map vulnerabilities and strive for continuous resilience testing to ensure services remain operational.
- Boards should demand evidence of DDoS resilience certainty gathered continuously in production, rather than just owning DDoS protection.