A Software Glitch Disrupts JPMorgan Chase Banking Services
On November 16, 2026, a software glitch at JPMorgan Chase significantly disrupted banking services, prompting a flurry of reports from thousands of customers experiencing difficulties in accessing their accounts and processing payments.
Complaints also emerged regarding Bank of America, Wells Fargo, U.S. Bank, and Zelle. However, these reports did not confirm distinct outages at each institution.
JPMorgan Chase attributed the disruption to a brief software issue within its “on-premise hardware systems,” referring to the equipment housed within its internal computing framework.
The bank clarified that there was no indication of a cyberattack and described the incident as a localized problem rather than an overarching failure within the broader banking infrastructure.
Customers encountered a myriad of issues, from checking account balances and viewing transactions to completing transfers.
Additionally, some Chase users faced challenges when attempting to withdraw funds, while delays cascaded through both online platforms and physical branches.
Despite the difficulties, Chase assured clients that they continued to have access to their accounts and funds, though certain requests were experiencing longer processing times than usual.
Impact of Chase’s Disruption on Other Banks
The ripple effects of the disruption primarily originated from transactions involving Chase, rather than affirmed failures within each bank mentioned in customer complaints.
Chase indicated that other financial institutions might face slower processing times for payments connected to its operations. Notably, Bank of America and Citigroup reported no failures within their banking services.
U.S. Bank similarly noted that its systems were not directly impacted. However, customers engaging in Zelle transactions involving other banks could still experience delays.
This distinction elucidates why multiple banking brands reported issues, despite it not indicating that each institution had encountered its own technical faults.
Zelle maintained that its network was functioning adequately, while its operator, Early Warning Services, attributed the delayed payments to complications at various financial institutions.
As outlined by the Associated Press, users of different banks may face delays when sending or receiving payments from or to a Chase customer.
The prevailing evidence suggests that the incident reflects a service availability issue rather than a verifiable data breach.
CNN reported that the glitch stemmed from an update to Chase’s physical computing systems, as confirmed by an anonymous source.
Chase’s public statement acknowledged a software bug but refrained from specifying the affected component or providing a comprehensive technical analysis.
This differentiation is crucial for evaluating banking disruptions. Although Cyber Security News has previously reported on DDoS attacks leading to outages in the financial sector, Chase found no evidence linking this event to such activities.
Notably, the incident occurred in the wake of a separate Microsoft 365 service outage, yet no correlation between the two incidents has been established.
Chase Announces System Recovery
By Monday evening, Chase indicated that transactions were processing normally, as reported by NBC News. This update signaled a restoration of services following hours of customer dissatisfaction.

However, Chase did not furnish a detailed account of the software malfunction, leaving the precise nature of the failure and preventative measures obscured.
Source link: Cybersecuritynews.com.






