Chase Software Bug Slows Payments at Major US Banks
Customers at several of America’s biggest banks struggled to reach their money on Monday after a software bug at JPMorgan Chase slowed transactions and rippled across the financial system.
Chase, the largest bank in the United States, said the fault lay in its own systems and was not a cyberattack. But because so many payments pass through Chase, customers at other banks felt the effects too, with online banking log-ins failing, balances slow to update and transfers delayed.
The bank said it was working to fix the problem by the end of the day, and by Monday evening it told NBC News that transactions were posting normally again. Wells Fargo, the other bank to confirm problems of its own, had not said by then that its service was fully restored.
What happened on Monday
Reports of trouble began on Monday morning, 16 November. Downdetector, the outage-tracking site, logged its first Chase reports shortly before 10 a.m. ET, and complaints climbed through the day. By 2 p.m. ET, nearly 4,800 people had reported problems with Chase, the most of any bank, according to CBS News. Fast Company, also citing Downdetector, reported that Chase was the hardest hit, with Bank of America and Wells Fargo also seeing spikes in complaints.
Some customers saw a message reading: “Some services aren’t available. We’re working on them. Please try back later.” One customer told CBS News he could not deposit a cheque at a Chase branch in Dallas, and NBC News reported that the fault reached online and in-person branch transactions.
Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One also saw spikes in customer reports on Downdetector, and users reported delays on the Zelle payment network. By early evening the numbers were falling: Chase reports were down to about 1,450 by 6:05 p.m. ET, Bank of America to about 650 and Wells Fargo to about 370.
Why other banks felt it
Chase was quick to say the problem was its own — and only its own. “This is not a systemic issue,” a Chase spokesperson said. “Other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us.”
That distinction matters, because the reports made it look at first as if several banks had gone down at once. U.S. Bank said its systems were “not directly impacted”, although Zelle payments to or from another bank could be delayed. Zelle’s operator, Early Warning Services, said Zelle itself was not down. The Associated Press reported that Bank of America and Citigroup had no problems with their own banking services, and Capital One told CBS News it was not affected.
Wells Fargo was the exception. Its website said online banking was temporarily unavailable, and it did not say whether the cause was connected to Chase.
Small businesses felt the disruption too. Chase says it banks 7.4 million small businesses, and the slowdown hit payroll, rent, vendor wires and card deposits at the same time — payments that cannot easily wait a day.
No sign of a cyberattack
With several banks apparently affected at once, speculation about a cyberattack spread quickly online. Chase rejected that outright. “JPMorgan Chase has experienced a temporary issue related to a software bug in on-premise hardware systems — it is not cyber-related,” spokesman Joe Evangelisti said.
The bank added that customers still had access to their accounts and funds, and no bank reported that any money had been lost. Plaid, the service many finance apps use to connect to bank accounts, opened an incident for Chase at 10:11 a.m. ET and had none for the other banks — another sign that the fault sat with Chase alone.
Online rumours claiming that bank balances would be wiped and the internet shut down on 17 November have no basis in what happened on Monday. The confirmed facts point to a single software fault at one bank, not a collapse of the banking system.
The latest in a run of technology failures
The bank disruption is the latest in a run of technology failures to hit American life in a few days. A Microsoft 365 outage that began on Thursday, 12 November, knocked out Outlook and Teams worldwide, and the Federal Aviation Administration ordered a nationwide ground stop on Friday, 13 November, after a router fault.
Microsoft later blamed the 365 outage on a bug introduced in a July software update that had gone undetected for more than three months. The Chase fault is separate, but the run of incidents has put a spotlight on how much everyday life depends on a small number of large technology and financial systems — and how quickly a single fault can spread.
What customers should do
Check your balance and recent transactions once service is back, and keep a record of anything that looks wrong. If a payment was delayed, check with the recipient before sending it again, to avoid paying twice.
Banks will not ask customers to share passwords or one-time codes to fix an outage, so any message claiming to do so should be treated as a scam. Anyone who believes a payment has gone missing should contact their bank directly through its official app or published phone number.
Frequently asked questions
Which banks were affected?
Chase was hit hardest, with nearly 4,800 Downdetector reports at the peak. Customers of Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One also reported problems, but only Chase and Wells Fargo confirmed faults of their own.
Was it a cyberattack?
No. Chase said the cause was a software bug in its on-premise hardware systems and that there was no evidence it was cyber-related.
Did anyone lose money?
No bank reported lost money, and Chase said customers still had access to their accounts and funds. Transactions were delayed rather than cancelled.
Is online banking back to normal?
Chase told NBC News on Monday evening that transactions were posting normally again. Wells Fargo had not confirmed full restoration by then, and reports on Downdetector were falling but still above normal levels.