Thousands of Chase customers could not use their online accounts on Monday. By 2pm Eastern, more than 4,700 had reported problems to Downdetector.
"JPMorganChase has experienced a temporary issue related to a software bug," a spokesperson said. "It is taking longer than usual to service some customers."
What it was, and what it was not
Chase was explicit that this was a bug, not a cyberattack. A source familiar with the matter told CNN it was not cloud-related either: an update to the company's own physical computer systems caused the problem.
Customers kept access to their accounts and funds, Chase said, though social media users reported trouble at physical branches too, and some local branches told customers their internal systems were affected.

How it spread to banks that were working fine
This is the part worth understanding, because it explains why an outage at one bank looked like an outage at four.
Customers reported problems at Bank of America, Wells Fargo and U.S. Bank — but on a smaller scale, and the reports traced back to Zelle transfers being sent to Chase accounts.
U.S. Bank said its systems were "not directly impacted" but that clients sending or receiving Zelle payments with another institution might see delays. Bank of America said it was operating normally. Zelle said its own service was "operating as it should" and that an issue at the financial institutions may be affecting broader services.
Chase put it plainly: other banks were affected "only to the extent that they were a party to a transaction with us".
So three banks with healthy systems looked broken because the fourth one they were transacting with was not. Nothing failed at their end. The failure arrived through the connection.
The run of three
Monday was the third straight weekday with a major technical failure, and readers who followed our coverage will know the first two.
- Thursday: the Microsoft outage cut email for millions across 74 countries. Microsoft blamed a Windows defect, a traffic overload and capacity limits.
- Friday: an FAA systems failure forced a nationwide ground stop. The cause was a router deployment and data flooding the system.
- Monday: Chase, plus a separate systemwide computer problem at United Airlines that delayed flights.
The causes are genuinely different. That is the point — this is not one bug propagating.
What the pattern actually shows
Mike Chapple, a professor of IT at the University of Notre Dame, named the common thread: "the complexity and fragility of the systems that we depend on every day". In each case, he said, an issue in one small part of a larger system spread quickly into nationwide disruption.
Rebecca Krauthamer of QuSecure made the more careful point. Complexity and interdependence are not flaws in themselves — they usually make systems more resilient. The danger arrives "when dependencies on systems aren't sufficiently understood".
Her comparison is the Titanic: watertight bulkheads that could not withstand a failure beyond what the designers imagined.
Madhu Shashanka of Concentric AI reduced it to the question an operator should actually be asking: "not whether one system will fail but how many other things fail with it, and how fast you can contain it".
For any bank, telecom or payment operator here, that is the audit worth running this week — not "can this break", but "who else breaks when it does".




