JPMorganChase attributed a nationwide banking disruption on Monday, Nov. 16, to a software bug in hardware systems within the bank. The problem slowed some transactions, including those involving other financial institutions. Chase told Denver7 Investigates that customers retained access to their accounts and money, and that it had found no evidence of a cyberattack.
In Colorado, Lainey Lien said she and her family could not complete transactions at two drive-up Chase ATMs between approximately 9:45 and 10:15 a.m. One was near 64th Avenue and McIntyre Street in Arvada, and the other was at Denver West on Colfax Avenue in Lakewood. Both displayed messages saying the transactions could not be processed. Her son later visited the Arvada branch again and successfully used its lobby ATM.
Thousands of reports appeared on Downdetector, including reports concerning other banks and payment services. Chase said its internal software problem did not represent a failure across the banking system. Other institutions could encounter delays when participating in transactions with Chase, the bank explained. According to the Associated Press, Bank of America and Citigroup were not having problems with their own banking services.
Steve Beaty, a computer science professor at MSU Denver, told Denver7 Investigates that financial institutions' connections can spread the effects of a slowdown. When one endpoint processes transactions slowly, other transactions can accumulate behind it. He compared the effect to traffic backing up for miles behind a relatively minor accident, noting that banks must exchange money with one another.
U.S. Bank said its systems were not directly affected, although customers sending or receiving Zelle payments involving another institution could experience delays. Eric Blankenbaker, vice president of communications for Zelle operator Early Warning, said the payment service was functioning properly. He explained that problems at participating financial institutions, which maintain customer accounts and hold their money, could delay some customers' Zelle payments.
Beaty interpreted Chase's statement about the absence of evidence of a cyberattack as suggesting an internal technical failure rather than an outside intrusion. He cautioned, however, that understanding the full cause and determining how to prevent another disruption could take longer than restoring service. Chase was aiming to resolve the issue by Monday's end, but had not publicly confirmed a full recovery when the source report was written.
For customers facing a delayed payment, Beaty recommended recording the transaction details and checking with the intended recipient before attempting another transfer. Repeating a payment immediately could result in both transactions eventually going through. Colorado Bankers Association president and CEO Jenifer Waller similarly urged customers to allow pending payments and deposits time to post and to obtain updates directly from their financial institution.
The association also warned customers to watch for scams, saying banks would not contact them to request passwords, PINs or one-time security codes. Beaty advised against using contact details supplied in unexpected account alerts. Customers should instead use an official banking app or website, the telephone number on their card, or another trusted contact method.
The disruption followed separate technology failures involving Microsoft services and a nationwide FAA ground stop. No evidence connected those incidents to Chase's software problem, and national reporting described them as separate technical failures. Beaty said a connection would surprise him, while noting that conclusions depended on the organizations investigating their systems.







