When the Financial System Goes Offline

The hidden systemic risk behind banking technology, third-party dependencies and the concentration of digital infrastructure

By Arturo Duran | November 2026

When access to money becomes a technology problem

On November 16, 2026, customers across the United States encountered difficulties accessing online banking and financial services at several major institutions.

JPMorgan Chase acknowledged a software bug affecting its internal hardware systems. Customers reported problems with online banking, account access and transaction processing. Reports of difficulties also emerged involving Wells Fargo, Bank of America, U.S. Bank, Capital One, Truist and the Zelle payment network.

The situation was particularly revealing because the disruption extended beyond the institution where the original technical problem was identified.

Chase said that transactions involving its systems could be delayed at other financial institutions, while Zelle maintained that its own network was functioning normally.

The immediate incident was eventually resolved. But the questions it raises will remain relevant long after the systems have been restored.

What happens when the financial system becomes so digitally interconnected that a technical failure at one institution can affect the ability of customers at other institutions to access or move their money?

And perhaps more importantly, how independent are our financial institutions when they increasingly depend on common technology providers, interconnected payment networks and similar operating architectures?

This is no longer simply a banking technology question. It is a question of economic resilience.

The financial system: A pillar of the free-world economy

The modern financial system is one of the fundamental pillars of the free-world economy.

It enables commerce, investment, savings, international trade, capital formation and the movement of money between individuals, businesses and governments.

Its credibility depends on more than the financial strength of individual institutions.

It depends on continuity, accessibility, confidence and the ability to execute transactions when required.

A bank can be solvent, adequately capitalized and fully compliant with regulatory requirements, yet still become operationally incapacitated.

That distinction deserves much greater attention.

Financial stability and operational resilience are not the same thing.

A financial institution may have the money, but if its customers cannot access their accounts, transfer funds, settle transactions or conduct business, its economic function is impaired.

In a highly digital economy, availability is becoming as important as solvency.

1. The new systemic risk: Operational contagion

Traditionally, systemic financial risk has been associated with bank failures, excessive leverage, liquidity crises, credit defaults and the collapse of confidence.

The 2008 financial crisis demonstrated how interconnected financial obligations can transmit distress throughout the global economy.

Today, another form of interconnectedness is emerging.

Operational contagion.

A technical failure does not need to destroy an institution’s balance sheet to create disruption across the financial ecosystem.

Consider the November 16 incident.

Chase reported an internal technical problem. Other institutions reported customer difficulties, and transactions involving Chase experienced delays.

This distinction matters.

Not every bank reporting problems necessarily suffered an independent outage. Some customers may have experienced downstream effects from transactions involving another institution.

Nevertheless, the result was a disruption that crossed institutional boundaries.

The financial system is becoming interconnected not only through capital and credit, but through technology and operational dependencies.

2. The concentration problem: Different banks, common vulnerabilities

Competition between financial institutions is essential to a free-market economy.

However, competition at the customer level does not necessarily mean independence at the infrastructure level.

Banks may compete aggressively while relying on overlapping ecosystems of:

  • Cloud computing and data-center providers.
  • Core banking software and transaction-processing platforms.
  • Cybersecurity and identity-management services.
  • Telecommunications and network infrastructure.
  • Payment processors and financial messaging systems.
  • External software developers and technology contractors.
  • Automated software updates and common technology components.

This creates a potential concentration problem.

If several institutions rely on the same critical provider, architecture or operational component, a failure can have consequences beyond the original customer or institution.

We should be careful not to assume that all banks use identical systems. They do not.

The more relevant question is whether apparently independent institutions share enough critical dependencies to create common-mode failure.

A failure in one common component can defeat multiple layers of otherwise independent protection.

The Financial Stability Board has already identified this broader challenge, emphasizing the need to monitor systemic third-party dependencies and the concentration of critical services.

The issue is not whether technology providers are good or bad. They have enabled extraordinary improvements in efficiency, security and scale.

The issue is what happens when the financial system becomes dependent on a limited number of them.

3. Efficiency versus resilience: A dangerous trade-off

For decades, financial institutions have pursued operational efficiency.

They have consolidated infrastructure, automated processes, outsourced technology functions and migrated services to increasingly integrated platforms.

These decisions have compelling economic logic.

They reduce operating costs, increase scalability, accelerate product development and improve the customer experience.

But efficiency and resilience are not interchangeable.

A highly optimized system can also become highly dependent on a small number of critical components.

The problem is not automation or cloud computing. It is the assumption that centralized, interconnected systems will always be available.

The same logic applies to redundancy.

Maintaining independent backup systems, alternative transaction channels, separate network connections and recovery capabilities costs money.

When these capabilities are viewed exclusively as operating expenses, organizations may gradually eliminate the very resources that protect them during a crisis.

We have seen this pattern in other critical infrastructure sectors.

The lesson is consistent: efficiency without sufficient redundancy can create fragility.

4. Third-party risk: Who actually controls the financial infrastructure?

One of the most important developments in modern banking is the growing reliance on external technology providers.

A bank may outsource part of its technology infrastructure, cybersecurity, data processing or payment operations.

But outsourcing does not outsource responsibility.

The Federal Reserve, FDIC and Office of the Comptroller of the Currency have explicitly addressed this issue in their joint guidance on third-party relationships.

The guidance recognizes that third-party relationships can introduce operational, technological and strategic risks, particularly when providers support critical activities.

It also highlights the importance of understanding dependencies, monitoring providers and maintaining contingency plans.

This raises an important question for boards and regulators:

Does the institution truly understand the full chain of dependencies required to keep its services operational?

It is not enough to know the name of the primary contractor.

One must understand the subcontractors, software components, infrastructure providers, network dependencies and recovery arrangements supporting that contractor.

The weakest link may be several layers removed from the bank’s own technology department.

5. The common-mode failure problem

Perhaps the most uncomfortable question is whether the financial industry is building a technology architecture that creates similar vulnerabilities across otherwise independent institutions.

Consider the following scenario.

A software component is widely deployed across multiple financial institutions. A faulty update, configuration error or infrastructure defect causes unexpected behavior.

Each bank has its own IT department, security controls and disaster recovery plan.

Yet all may be exposed to the same underlying defect.

This is a common-mode failure.

The July 2024 CrowdStrike incident demonstrated how a problem involving a widely deployed software component could disrupt organizations across multiple sectors.

It was not a banking-specific event, but it illustrated how technology concentration can produce consequences far beyond the original provider.

The lesson is particularly relevant to financial institutions.

Independence cannot be measured only by corporate ownership or the number of data centers.

It must also be measured by the independence of critical operating components and the ability to continue functioning when shared components fail.

6. The implications for the free-world economy

The financial system is not an isolated industry.

Its disruption affects virtually every economic activity.

Consider the consequences of a prolonged financial technology failure:

  • Businesses may be unable to receive payments or pay suppliers.
  • Employees may experience delays in receiving salaries.
  • Consumers may lose access to digital payment methods.
  • International trade and settlement operations may be delayed.
  • Small businesses with limited cash reserves may face immediate liquidity pressure.
  • Financial markets may experience operational uncertainty.
  • Confidence in institutions and digital financial services may deteriorate.

A disruption lasting a few hours is inconvenient.

A disruption lasting several days could become an economic event.

And a disruption affecting multiple institutions simultaneously could become a national resilience issue.

The critical distinction is between a temporary service interruption and the inability of the financial system to continue performing its essential functions.

That is the scenario boards, regulators and policymakers should be testing.

7. What should financial institutions do differently?

The answer is not to abandon digital banking or return to an entirely manual operating model.

Technology is indispensable.

The objective should be to build systems that can fail without bringing the institution to a standstill.

Several priorities deserve attention:

Independent redundancy

Critical banking functions should have recovery capabilities that do not depend entirely on the same infrastructure, software or network as the primary system.

Dependency mapping

Institutions should identify their critical third-party providers, subcontractors, common software dependencies and potential single points of failure.

Alternative transaction capabilities

Banks should test whether essential services can continue through alternative channels when primary digital platforms become unavailable.

Operational stress testing

Testing should extend beyond financial liquidity and capital adequacy. It should include prolonged technology outages, simultaneous provider failures, payment-network disruptions and telecommunications failures.

Board-level accountability

Operational resilience should be a board-level concern, not simply an IT department responsibility.

Cross-institution coordination

Regulators and financial institutions should develop better visibility into common dependencies and systemic technology risks across the financial ecosystem.

8. An opportunity to rethink financial infrastructure

Every structural vulnerability creates an opportunity for innovation.

Financial technology companies, cybersecurity providers, infrastructure developers and specialized service firms have an opportunity to address a growing need: operational independence and resilience.

Potential areas include:

  • Distributed and geographically independent recovery infrastructure.
  • Independent payment and settlement capabilities.
  • Real-time monitoring of third-party dependencies.
  • Automated disaster recovery and continuity systems.
  • Secure alternative identity and transaction verification.
  • Resilient communications infrastructure.
  • Better tools for mapping and testing common technology dependencies.

The objective should not be decentralization for its own sake.

It should be the ability to maintain essential financial operations when individual components fail.

The question is no longer whether technology will fail

Technology will fail. Software will contain defects. Hardware will malfunction. Networks will experience disruptions. Third-party providers will occasionally experience outages.

These are unavoidable realities.

The question is whether our institutions are designed to withstand those failures.

The modern financial system has become extraordinarily efficient, interconnected and technologically sophisticated.

But sophistication does not automatically translate into resilience.

We must recognize that a financial institution’s operational independence is increasingly determined by the infrastructure it shares with others.

A bank’s balance sheet may be independent. Its technology architecture may not be.

And if the institutions supporting the free-world economy become dependent on the same critical systems, the failure of one component may have consequences far beyond the organization where it originated.

The next financial crisis does not necessarily have to begin with bad loans, excessive leverage or a collapse in asset values.

It could begin with a failure of the infrastructure that allows money to move.

That possibility deserves the attention of every bank board, regulator, investor and policymaker.

Financial resilience must become as important as financial stability.

Because confidence in money ultimately depends on the ability to access it, transfer it and use it when it matters most.


Sources and further reading

  1. Associated Press, November 16, 2026 — Reporting on the Chase technical incident and delays involving other financial institutions.
  2. Reuters, November 16, 2026 — JPMorgan Chase software bug and transaction delays.
  3. Financial Stability Board, December 4, 2023 — Enhancing Third-Party Risk Management and Oversight: A Toolkit for Financial Institutions and Financial Authorities.
  4. Federal Reserve, FDIC and OCC, June 6, 2023 — Interagency Guidance on Third-Party Relationships: Risk Management.
  5. Federal Reserve, July 2024 — Cybersecurity and Financial System Resilience Report.

Leave a Reply