Small text, dark mode

Chase Software Bug Delays Transactions Across U.S. Banking Network

A Chase technical problem slowed some transactions involving other banks on November 16. The bank said the disruption was not a cyberattack.

Chase Software Bug Delays Transactions Across U.S. Banking Network

A software problem at JPMorgan Chase delayed transactions and disrupted online banking for some customers on November 16. The effects also reached transactions involving other banks, illustrating how a problem at one institution can ripple through connected payment services.


What Chase said happened

Chase said a software bug was affecting its internal hardware systems and slowing some transactions, according to The Associated Press. The bank said the issue was temporary and was not the result of a cyberattack. Some customers reported difficulty accessing services or received messages that certain services were unavailable.

The distinction between a delayed transaction and an inaccessible account matters. Chase said customers still had access to their accounts and funds while it worked to restore services. Individual experiences varied, and an outage report by itself does not establish what happened to a specific payment.


Why other banks appeared in reports

Customers at Bank of America, Citi and other institutions could experience delays when transactions involved Chase, according to a Chase spokesperson cited by the AP. The AP reported that Bank of America and Citigroup were not experiencing problems with their own banking services.

That does not mean every complaint involving another bank was imaginary. A payment can depend on more than one institution, and a delay at one point in the chain can be visible to customers on either side. It does mean that reports naming several banks should not automatically be read as proof that each bank’s systems failed.


The wider outage picture

Customers also reported problems involving the Zelle money-transfer service. The disruption arrived after a separate Microsoft outage and amid other recent technology interruptions. The timing attracted attention, but Chase described its issue as an isolated technical problem. The available reporting does not establish a common cause linking these incidents.

By November 17, CBS reported that the widespread service disruptions appeared to be over. Customers with a transaction still pending should check its status with their bank before attempting it again, since an earlier payment could complete after a delay.


Why this matters for digital finance

Modern payments rely on networks of banks, software and service providers. A user may see a single app, but a transfer can pass through several systems before it reaches its destination. When one major participant has a problem, the visible effects can spread beyond that institution.

The episode is a reminder to distinguish temporary access or processing problems from confirmed losses, and to separate an institution’s own system failure from delays in transactions with a counterparty. The cause and scope described by Chase remain the basis for the current account of the event.