A software bug inside JPMorgan Chase's in-house systems slowed or blocked transactions for thousands of Americans on Monday, and the failure rippled straight through to Bank of America, Wells Fargo, and the Zelle payment network — exposing just how fragile a financial system built around a handful of too-big-to-fail institutions really is.
When the nation's largest bank trips over its own code, it doesn't just inconvenience Chase customers. It gums up transactions at rival banks, stalls peer-to-peer payments, and leaves working people standing at the teller window with no answers. That's not a glitch. That's a design flaw — the natural result of concentrating the nation's financial plumbing in fewer and fewer hands.
Chase confirmed the issue was a technical bug in its own software, not a cyberattack. "Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds," a Chase spokesperson said in a statement. "We are working to resolve this as quickly as possible." Some Chase customers received a blunter message: "Some services aren't available. We're working on them. Please try back later."
Try back later doesn't cut it when you're trying to deposit a paycheck. A Chase customer in Texas told CBS News he tried to deposit a check at a Dallas branch Monday morning, but the transaction could not be completed. A bank teller told the customer the "system was down" — with no further explanation. Nearly 4,800 users reported problems with Chase by 2 p.m. ET, according to Downdetector, the most of any institution.
The damage didn't stay at Chase. Because Chase sits at the center of so many interbank transactions, customers at Bank of America, Wells Fargo, US Bank, Capital One, and Truist all reported spikes in outages. Wells Fargo posted a message on its own website: "Online banking is temporarily unavailable." Zelle, the peer-to-peer payment system owned jointly by those same big banks, felt the drag too. A Zelle spokesperson said its network was "operating as it should" but acknowledged that "an issue at the financial institutions may be delaying Zelle payments for some of their customers." In plain English: the banks broke the pipe, and Zelle can't flow through a broken pipe.
Chase insisted this "is not a systemic issue." The other banks, contacted by Reuters, said they were not experiencing significant direct problems. But that's the point — they didn't have to have their own problems for Chase's failure to become theirs. When one bank is party to so many transactions across the system, its private software bug is everybody's problem.
This is the second major infrastructure disruption in less than a week. A Microsoft outage on Thursday crippled Outlook, Teams, and government operations worldwide. On Friday, a faulty router grounded every commercial flight in the United States for four hours. The Guardian connected all three failures; most American outlets treated them as isolated hiccups. They aren't. They're symptoms of the same disease: critical systems stacked on single points of failure, run by institutions too big to be held accountable when they break.
After 2008, these banks were bailed out and told to get stronger. Instead, they got bigger. Chase alone holds over $3 trillion in assets. When it stumbles, the whole country feels it. No regulator has broken them up. No politician has forced real competition. And when the software crashes, the same people who can't access their own money are the ones who bore the cost of the last rescue.
Chase says customers "still have access to their accounts and funds." For thousands of Americans on Monday, that was a technicality, not a reality. The question isn't whether this bug gets fixed. It's whether anyone in Washington will treat this as what it is — a warning that a system this concentrated is a system one failure away from crisis.







