CyberSecurityNews

Chase Software Bug Disrupts Banking Services as Customers Report Outages at Major US Banks


A software bug at JPMorgan Chase disrupted banking services on November 16, 2026, leaving thousands of customers reporting trouble with account access and payments. Complaints also appeared for Bank of America, Wells Fargo, U.S. Bank and Zelle, though reports did not establish separate outages at each bank.

Chase linked the disruption to a temporary software issue in its “on-premise hardware systems,” meaning equipment within its own computing setup. The bank said there was no evidence of a cyberattack and described the problem as isolated rather than a failure across the wider banking system.

Customers reported problems checking balances, viewing transactions and completing transfers. Some Chase users also faced trouble withdrawing money, while delays affected both online services and branch transactions. Chase said customers retained access to their accounts and funds, although some requests were taking longer than usual to complete.

Chase Outage Affected Other Banks

The wider impact came from transactions involving Chase, not confirmed failures inside every bank named in customer complaints. Chase said other institutions could experience slower processing when it was involved in a payment. Bank of America and Citigroup were not experiencing failures in their own banking services.

U.S. Bank made a similar distinction, saying its systems were not directly affected. Customers sending or receiving Zelle payments involving another financial institution could still face delays. This explains why reports across several banking brands did not mean every institution had suffered its own technical failure.

Zelle said its network was “operating as it should.” Its operator, Early Warning Services, linked delayed payments to problems at financial institutions. As the Associated Press explained, customers using other banks could encounter delays when sending money to, or receiving money from, a Chase customer.

The available evidence points to a service availability problem, not a confirmed data breach. CNN reported that an update to Chase’s physical computer systems caused the issue, citing a person familiar with the matter. Chase’s public explanation identified a software bug without naming the affected component or releasing a detailed technical report.

That distinction matters when assessing banking disruptions. Cyber Security News previously covered DDoS attacks causing financial-sector outages, but Chase reported no evidence of such activity here. The incident also followed the separate Microsoft 365 service outage, with no established connection between the two events.

Chase Reports Recovery

By Monday evening, Chase said transactions were posting normally, according to NBC News. The recovery update marked an improvement after hours of customer complaints. It did not provide a full breakdown of the software fault, leaving the exact failure mechanism and steps to prevent a repeat unclear.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.



Source link