86 million customers affected. Over 4,800 user reports. A single software bug at JPMorgan Chase rippled through the U.S. banking system, exposing a hidden vulnerability in its interconnected infrastructure.
The Root Cause: A Local Glitch, Not a Global Attack
JPMorgan Chase confirmed Monday’s outage was caused by a “software bug in on-premise hardware systems.” The bank stated there is no evidence of a cyberattack. The bug impacted Chase’s core systems, slowing transactions for its customers. The bank emphasized this was “not a systemic issue,” but acknowledged that other banks may have been affected “to the extent they were a party to a transaction with us.” Customers retained access to their funds but faced delays in account access and transactions.
The Ripple Effect: How One Bank’s Failure Spread
The outage peaked around 2 PM ET, with issues beginning as early as 9:30 AM ET. Downdetector recorded over 4,800 user reports for Chase alone. Spikes were also reported for Wells Fargo, Bank of America, and Zelle. While only Chase was officially confirmed as the source, the cascading effect was clear. Zelle denied its systems were down but acknowledged “an issue at the financial institutions may be impacting broader services.” U.S. Bank confirmed its systems were not directly impacted, but noted clients using Zelle with other institutions might experience delays.
The Numbers: The Scale of the Disruption
The figure that matters is 86 million. That’s the number of U.S. customers Chase reported were affected. The scale of the outage is put in perspective by similar past events. In 2024, a CrowdStrike software update caused 8.5 million Windows systems to crash globally, with financial damage estimated in the tens of billions. CrowdStrike’s Falcon Sensor operates at the OS kernel level, meaning a single faulty update can paralyze entire networks.
A Mirror of 2024: The Fragility of Shared Systems
This outage mirrors the CrowdStrike disaster and highlights a growing pattern of systemic fragility. Last Thursday, Microsoft experienced a two-day downtime for Outlook and Teams. Just days before that, the FAA grounded all U.S. aircraft due to a telecom and data issue. These cross-sector failures reveal a shared reliance on complex, interconnected infrastructure. The Chase outage showed how a localized failure in banking can amplify through shared transaction networks.
What Comes Next: The Bottom Line for Regulators
Some users reported being locked out of accounts entirely, while others could view balances but not initiate transactions. Credit and debit card transactions continued to process, but digital services were disrupted. Chase projected resolution by end-of-day, but manual fixes in past outages prolonged disruptions for days. The ripple effect across major banks will likely draw regulatory scrutiny, given the outage’s scale and the financial sector’s shared reliance on third-party networks.
Sources
- 2024 CrowdStrike-related IT outages
- The Bank Outage May Have Nothing to Do With Your Bank
- Chase Bank outage: Customers report problems at major U.S. banks
- What to Know About the Banking Service Outages
- It's not just you, several bank apps are down
Photo: Jfendi (CC BY-SA 4.0)





