JPMorgan Chase Suffers Disruption Due to Software Bug
On Monday, November 16, a critical software malfunction within JPMorgan Chase led to substantial interruptions in banking services for several hours, exacerbating delays in payments at various financial institutions involved in transactions with Chase.
This incident, reported in The Rundown’s November 17 edition, followed a sequence of notable outages affecting both Microsoft and aviation services across the United States.
Joe Evangelisti, a spokesperson for Chase, informed the Associated Press that the disruption stemmed from a software glitch in a system housed on the bank’s premises, emphasizing that there was no evidence to suggest a cyberattack was involved.
Impact on Payments and Accounts
U.S. Bank confirmed that its systems were not directly impacted, and the operator of the Zelle payment network asserted that its services remained fully operational.
However, the disruption permeated physical banking environments, as AP reported malfunctioning Chase ATMs.
Plaid, known for linking bank accounts with various applications, acknowledged intermittent errors associated with Chase accounts, noting that the connectivity issues were resolved by 7:34 p.m. EST on the same day.
By Tuesday, November 17, Chase communicated to AP that the issue had been rectified and that transactions were subsequently functioning as expected.
The Significance of the Outage
The disruption experienced by Chase was one of a trifecta of significant failures impacting essential services between November 12 and November 16.
Additionally, Microsoft encountered service outages affecting Outlook and Teams beginning on November 12, which were not fully restored until November 14.
Furthermore, on November 13, the FAA suspended flight departures nationwide for around five hours due to an overload of new technology on outdated systems, resulting in communication and radar failures. The restrictions were lifted later that evening.
While no connections have been established between the incidents, the overlapping timelines prompt an inquiry into the resilience of vital services amid technical failures, how they mitigate adverse effects, and the efficacy of their customer communication strategies during recovery periods.
For customers utilizing Chase services, this incident underscores the vulnerability inherent in the operational dependencies of transactions.
Even with a fully functional bank, payments may still experience delays due to the involvement of other financial institutions. Thus, while U.S. Bank’s systems and Zelle’s network may be fully functional, payments involving Chase can still face interruption.
Consequently, the service status of a single bank can, at times, offer customers only a partial understanding of a delayed transaction.
Similarly, the errors recorded by Plaid indicate a limitation for users accessing their accounts via third-party applications.
An alternative app may provide a different pathway to reach a Chase account, yet reliance on Chase’s response remains essential. As a result, switching applications may fail to deliver a reliable contingency.
This situation highlights the crucial necessity for effective communication from financial institutions. Customers need clarity on which connections are disrupted, the status of payment delays, and the accessibility of various account options.
While a general assurance regarding the operation of a payment network may be accurate, it can leave customers uncertain regarding the reasons for their stalled transactions.

Chase’s identification of a software bug points to the underlying issue, yet it raises pertinent questions as to why normal transaction processing was delayed for hours, how backup systems activated during the crisis, and what preventive measures can be instituted to avert a recurrence of such disruptions.
Source link: Therundown.ai.





