On November 16, 2026, JPMorgan Chase experienced a significant software glitch that disrupted its banking operations, impacting thousands of customers who faced issues with accessing their accounts and completing transactions. The disruption also affected services at Bank of America, Wells Fargo, U.S. Bank, and Zelle, although there were no confirmed outages at these institutions.
Root Cause and Impact on Chase Customers
The issue was traced back to Chase’s internal hardware systems, specifically a temporary software bug within their on-premise setup. Chase quickly clarified that there was no cybersecurity breach involved, describing the problem as localized rather than affecting the broader banking network.
Customers reported difficulties in checking balances, viewing transaction histories, and executing transfers. Some were unable to withdraw cash, and both online and branch services faced delays. Despite these issues, Chase assured customers that their funds and accounts remained accessible, albeit with slower processing times.
Effect on Other Financial Institutions
The ripple effect of Chase’s software issue was felt by other banks, though not due to internal failures at these institutions. The delays primarily affected transactions involving Chase, causing slower processing for other banks like Bank of America and Citigroup, which reported no internal service disruptions.
U.S. Bank also confirmed that its systems were not directly compromised. However, customers using Zelle for transactions with Chase-affiliated accounts might experience delays, highlighting that the widespread reports did not indicate systemic failures across all banks.
Technical Analysis and Recovery
According to reports, the glitch stemmed from an update to Chase’s physical computer systems, as confirmed by a source familiar with the situation. Chase’s public communication cited a software bug, yet specifics about the affected component remain undisclosed.
By the end of Monday, Chase announced that normal transaction processing had resumed, suggesting recovery from the issue. However, the bank did not provide a comprehensive explanation of the software fault, leaving the exact cause and preventive measures unclear.
In the context of recent cybersecurity incidents, such as the separate Microsoft 365 service outage, Chase’s disruption underscores the importance of robust system management and preparedness against potential technical failures.
