Skip to content

Another Day, Another Outage: Banks Join a Week of Technology Chaos

Banking disruptions follow Microsoft 365 failures, an FAA ground stop and other operational breakdowns. Different incidents, same warning: Organizations are dangerously dependent on systems they can't function without.

Another day, another outage. This time, it's the banks.

Customers of Chase, Bank of America, Wells Fargo, Truist and U.S. Bank reported trouble accessing online banking services Monday, November 16, as another wave of technical disruptions added to an already chaotic stretch for critical services.

According to The Associated Press, Chase acknowledged a technical problem that delayed some transactions, though customers retained access to their accounts and funds. U.S. Bank said its own systems weren't directly affected, but customers could experience delays involving Zelle payments with other institutions.

Chase said its issue was technical, not cyber-related. There's no established evidence that all the reported banking problems share a common cause.

First Microsoft. Then the FAA. Now the banks.

The banking problems follow a Microsoft 365 outage that disrupted essential business services, including Outlook and Teams. Then came an FAA ground stop that disrupted air travel and unleashed the predictable speculation about cyberattacks before investigators had established the facts.

Now we're watching banking customers struggle to access services and complete transactions.

None of these incidents needs to be connected for the collective lesson to be essentially the same.

We've built an extraordinary amount of operational complexity around systems that, when they fail, can leave organizations with surprisingly few alternatives.

The problem isn't the outage. It's what the outage reveals.

What should concern cybersecurity and business leaders is how quickly an ordinary technical problem can become an operational crisis.

A communications failure grounds a perfectly functional aircraft. A cloud service disruption interrupts business operations. A banking technology problem delays financial transactions.

The immediate technical issue matters. But so does the question of why the affected operation couldn't continue without that particular system.

As George V. Hulme wrote earlier today, organizations need to stop treating resilience as something that begins after systems go down. The work must happen long before that.

That means identifying critical dependencies, including the ones buried several layers deep in third-party services. It means testing alternative workflows rather than assuming they will work. And it means measuring recovery in terms of actual business operations, not simply whether a dashboard has returned to green.

For cybersecurity leaders, the practical priorities are straightforward:

  • Identify single points of operational failure. Look beyond infrastructure to the everyday workflows that depend on it.
  • Test what happens when dependencies disappear. Don't just simulate a server failure. Take away email, cloud authentication, payment processing or a critical third-party service and see what still works.
  • Build usable alternatives. Manual procedures, alternate communications and contingency processes must be practical, documented and rehearsed.
  • Measure whether the business can function. Restoring a system isn't the same as restoring the service customers and employees depend on.

Not every outage is a cyberattack. Every outage is a resilience test.

There's another lesson in this week's events: Stop assuming every major disruption must involve malicious actors.

Cyberattacks are one cause of outages. Software defects, configuration mistakes, infrastructure failures and broken dependencies are others.

The cause determines the investigation and remediation. It doesn't eliminate the need for business continuity.

Availability is a fundamental part of cybersecurity, and it deserves the same attention organizations devote to preventing unauthorized access and protecting sensitive information.

Microsoft will fix its services. Banks will resolve their transaction problems. Airplanes will get back in the air.

Then something else will break.

The question isn't whether your organization will experience an outage, but if you've built a business that can keep functioning when it does.

Latest