Chase Attributes Payment Disruption to Software Bug, Says It Was Not a Cyberattack
A software bug in a Chase system reportedly delayed some banking services and payments involving other major banks on a Monday. Chase said the problem was not a cyberattack. The date, payment services affected and number of customers involved remain unknown.
- Chase blamed a bug in an “on-site hardware system.”
- The bank said other institutions were affected only when transactions involved Chase.
- Transactions were reportedly posting normally again by about 6:30 p.m. Eastern.
- The scale and final outcome of delayed payments remain unclear.
What happened, and what remains unclear
Chase blamed the disruption on a software bug in an on-site hardware system and said it was not linked to a cyberattack. The bank has not identified the system or explained the fault in more detail. The phrase “on-site hardware system” doesn’t specify which payment services or technical components were involved.
Chase spokesperson Joe Evangelisti described the issue as non-systemic, saying other banks were affected only when dealing with Chase. That reflects the bank’s account of the disruption, not an independent assessment of its wider financial-stability implications.
Customers at other banks may have faced delays when a payment involved Chase. That doesn’t mean their own banks’ systems were down. A transaction can get held up at one institution while the other continues operating normally.
Reports to Downdetector, a service that tracks user-submitted reports of service problems, reportedly peaked around 2 p.m. Eastern and eased later in the day. These reports can show when users are having trouble, but they don’t count affected customers or transactions.
The disruption was described as taking place on a Monday, but the account does not give the calendar date. It also does not specify which payment types were affected, how many customers or transactions were involved, or what steps Chase took to prevent a recurrence.
Why a problem at one bank can affect customers elsewhere
Payments move through connected institutions and services. When one bank has trouble processing transactions, people who bank elsewhere can still face delays if their payments depend on that bank.
A Federal Reserve research note, “Using Service Provider Connections to Model Operational Payment Networks, ” by Chase Englund and Zach Modig, published January 3, 2025, offers general context: disruptions can affect firms indirectly through their connections to other firms. The note does not examine this Chase incident or establish its impact.
The distinction matters. A disruption at one institution can affect customers beyond its own base because centralized payment networks rely on connected systems. But this incident alone doesn’t show how widespread the effects were or prove that decentralized payment systems would be safer. Different systems come with different dependencies and risks.
Transactions reportedly recovered, but delayed is not the same as failed
Transactions were reported to be posting normally again by about 6:30 p.m. Eastern. That suggests processing had recovered, but it doesn’t confirm the final status of every payment submitted during the disruption.
A delayed payment may post later, while another may need attention. The available details don’t say whether payments failed, were duplicated or led to late fees. Customers expecting a payment to clear should check its status and contact the biller if it remains delayed.
Key questions and answers
-
What caused the reported disruption?
Chase blamed a software bug in an on-site hardware system. The bank has not identified the specific system or fault.
-
Was it a cyberattack?
Chase said it was not linked to one. That is the bank’s assessment, and the available details do not independently establish the cause.
-
Why were customers at other banks affected?
Some payments involved Chase, so a processing issue there could delay transactions for people who bank elsewhere. The payment services involved have not been confirmed.
-
When did transactions return to normal?
They were reported to be posting normally again by about 6:30 p.m. Eastern. That doesn’t confirm the outcome of every delayed payment.
-
What should customers do?
Check recent and scheduled payments. If a due payment remains delayed, contact the biller to confirm its status and discuss any potential late charge.
Related developments include JPMorgan and Coinbase’s crypto partnership for Chase customers, Deribit and SignalPlus’s Summer Chase, and a JPMorgan Chase insider fraud case.