Chase software bug knocked out banking for thousands, rippled through Zelle and rival banks
A software bug in JPMorgan Chase's own hardware systems disrupted online and in-branch banking for much of Monday, briefly dragging Zelle payments and transactions at other major banks along with it.
JPMorgan Chase's online and in-branch banking ground to a crawl on Monday after a software bug in the company's on-premise hardware systems slowed transactions across the board — peaking at nearly 5,000 customer complaints on Downdetector by 2 p.m. ET and temporarily holding up Zelle payments and transfers at Bank of America, Wells Fargo, U.S. Bank and other institutions. By around 6:30 p.m. ET, Chase said transactions were posting normally again, and by early Tuesday Downdetector showed service levels back to normal across the affected institutions.
JPMorganChase has experienced a temporary issue related to a software bug. It is taking longer than usual to service some customers.— Chase spokesperson
Chase was careful to frame the scope of the problem on two fronts: it was not a cyberattack, and it was not systemic. The bank said in a social media post that other institutions were affected only where Chase was a party to a shared transaction — meaning a customer trying to send money from a U.S. Bank account to a Chase account, for example, could see a delay even though U.S. Bank's own systems were working fine.
Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds. We are working to resolve this as quickly as possible.— Chase spokesperson
The outage was not caused by a cloud-related issue or a cyberattack, according to a source familiar with the matter. A software update applied to the bank's own physical computer infrastructure triggered the problems, CNN reported. A Justice Department official separately said there was 'no evidence of any attack,' and the Federal Reserve confirmed that all Fed-operated financial systems were functioning normally.
Customers felt the disruption in tangible ways. Chase app users in some cases encountered a message reading 'Some services aren't available. We're working on them. Please try back later.' One Chase customer in Texas, speaking to CBS News, said he went to a Dallas branch early Monday to deposit a check but was unable to finish the transaction after a teller told the person ahead of him that the 'system was down,' offering no further details. Social media users also reported issues with transactions at physical branches.
The ripple effects across other banks were real but limited in origin. U.S. Bank said its own systems were not directly impacted, but that customers trying to send or receive Zelle payments with another financial institution might see delays. Bank of America said its systems had been operating normally all day, and Capital One said it had not been affected. Zelle itself said its service was 'operating as it should' — but acknowledged that a problem at a financial institution could delay payments for that institution's customers.
Consumers use Zelle through participating banks and credit unions, which manage their accounts and hold their funds. Consumers do not have a separate Zelle account, and Zelle does not hold consumer funds.— Zelle spokesperson
Zelle's network operator, Early Warning Services, is owned by a consortium that includes Bank of America, Capital One, JPMorgan Chase, PNC Bank, Truist, U.S. Bank and Wells Fargo. Because Zelle moves money between bank accounts rather than holding funds itself, a payment requires both the sending and receiving bank to be functioning — which is why Zelle being 'up' offered little comfort to customers trying to send money to or from a Chase account on Monday.
Monday's outage was the third straight weekday with a large-scale technology failure in the United States. A Microsoft outage on Thursday left millions of people across 74 countries without access to email. A Federal Aviation Administration systems failure on Friday brought about a nationwide ground stop. On Monday afternoon, United Airlines also reported a systemwide computer problem that delayed flights before being resolved that evening. Investigators and company officials have said there is no evidence the incidents are connected — each had a distinct stated cause.
Our country has seen three very serious technology incidents over the past week. When we dig into the details, each one has an explanation that makes sense on its own, but they all point to a common theme: the complexity and fragility of the systems that we depend on every day.— Mike Chapple, professor of IT, Analytics, and Operations, University of Notre Dame
The larger companies have global reach that affords their customers flexibility and seamless integration with other businesses. Unfortunately, when one of these backbone providers has disruptions, the downstream effects are magnified. The multiple entities that rely on those services are also affected.— Karen Panetta, dean of graduate engineering, Tufts University
The question for leaders is not whether one system will fail but how many other things fail with it, and how fast you can contain it.— Madhu Shashanka, founder of Concentric AI
Chase has not published a detailed technical account of what went wrong or said how many of its roughly 94 million U.S. customer relationships were affected. Rep. Maxine Waters, the top Democrat on the House Financial Services Committee, called on Monday for banks to give the public a prompt explanation of what occurred. Chase's public statements have not mentioned automatic fee refunds or compensation for customers whose payments were delayed.
Why it matters — When the largest U.S. bank's payment systems slow down, the effects don't stay inside Chase — they ripple through shared networks like Zelle and touch customers at banks that had no technical problem of their own, illustrating how deeply interconnected the financial system's infrastructure has become.
⚠ Not yet confirmed
- First outage reports appeared around 9:30 a.m. ET Monday.
- A Justice Department official said there was 'no evidence of any attack.'
Sources differ on Time the first outage reports appeared: Around 9:30 a.m. ET (WIRED, via stablecoininsider.org) (stablecoininsider.org) vs As early as 11:30 a.m. ET (CNBC, via stablecoininsider.org) (stablecoininsider.org) vs Around noon (BBC, via stablecoininsider.org) (stablecoininsider.org)
Reported by cbsnews.com, cnn.com, forbes.com, stablecoininsider.org
- Maxine WatersUnited States Representative from California since 1991