- Reports involving several banks reflected payment delays and access problems; Chase says issue was not systemic or cyber-related
- Zelle says its network remained operational, highlighting how problem at one bank can affect customers elsewhere
A software problem at JPMorgan Chase disrupted banking services in the US on Monday, generating thousands of customer complaints and delaying some transactions involving other financial institutions.
Reports involving Chase, Bank of America, U.S. Bank, Wells Fargo and payment network Zelle initially raised questions about whether several major banking systems had failed simultaneously.
Subsequent statements pointed to a more specific explanation: Chase identified a bug in its internal systems, while other institutions said their services were operating but payments involving another bank could be delayed.
Chase said transactions were posting normally by Monday evening. It said there was no evidence of a cyberattack and described the problem as an operational issue rather than a systemic failure.
The incident highlights the distinction between a bank’s own systems failing and its customers experiencing delays because another institution involved in a payment is having problems.
What happened on Monday?
Customers reported difficulties logging into banking websites and apps, checking balances and completing transactions.
Downdetector recorded more than 4,600 reports involving Chase and over 1,500 involving Bank of America as of 1845GMT Monday. Reports also appeared for Wells Fargo, U.S. Bank and Zelle.
Some Chase customers received a message saying that certain services were unavailable and asking them to try again later.
The disruption also affected some in-person transactions at Chase branches, according to NBC News, indicating that the problem extended beyond banking apps and websites.
However, a report filed under a particular bank’s name did not establish that the bank’s own systems had failed. Later statements from banks and payment providers helped clarify that distinction.
What caused Chase’s disruption?
Chase attributed the incident to a “temporary issue related to a software bug in on-premise hardware systems.”
That description places the fault in systems operated within the bank’s own infrastructure. It does not identify a failure at a shared cloud provider or establish that other banks had the same software defect.
The bank said the problem slowed service for some customers and could affect other institutions when they were involved in transactions with Chase.
Its public explanation did not provide a detailed technical account of which components failed, how the bug developed or why it disrupted transaction processing.
Those details matter for assessing how the failure occurred and what changes could prevent a recurrence.
Why did customers at other banks report problems?
A payment between two banks requires participation from both institutions. A customer’s own bank can be functioning while a transfer is delayed because the institution on the other side cannot process it normally.
Chase said other banks could have experienced slower transactions when they were party to a payment involving Chase.
For example, a customer sending money from another bank to a Chase account could experience a delay even if the sending bank’s systems were operating.
U.S. Bank said its systems were not directly affected, although customers sending or receiving Zelle payments involving another financial institution could encounter delays.
Bank of America told CBS News its systems were operating normally Monday. Wells Fargo told NBC Chicago it was investigating customer reports concerning online banking.
These statements explain some of the overlapping complaints without establishing the cause of every individual report.
Was Zelle itself down?
Zelle said its network was “operating as it should,” while problems at financial institutions could affect payments for some customers.
Zelle facilitates payments between participating banks and credit unions. Customers generally access it through their financial institution’s website or banking app.
It does not hold money in a separate Zelle balance. Instead, it helps institutions exchange payment instructions so funds can move between eligible bank accounts.
That structure means the payment network can remain operational while a participating bank has difficulty completing a transaction.
A customer experiencing a failed or delayed Zelle payment may therefore report a Zelle problem even when the underlying disruption is at a bank.
What did Chase say about customers’ funds?
Chase said customers retained access to their accounts and funds, although some transactions were taking longer than usual.
That assurance accompanied reports of problems with particular services. It should not be read as a claim that every customer could complete every transaction normally throughout the incident.
The bank said there was no evidence the disruption was cyber-related. Its explanation concerned transaction processing and service availability.
An inability to log in or complete a transfer does not, by itself, establish that money has been lost or that an account has been compromised.
How many people were affected?
There is no confirmed total for the number of affected customers.
Downdetector measures reports of problems rather than conducting a census of affected accounts.
Its methodology compares incoming reports with the usual volume for a service at that time of day. A significant increase can signal an incident, but it does not independently determine its cause.
The website also limits how frequently repeated reports from the same user contribute to public totals.
Consequently, the figures cannot be treated as the precise number of customers affected, and reports under different banks’ names cannot simply be added together to calculate the scale of a single technical failure.
Have services returned to normal?
Chase said transactions were posting normally Monday evening, NBC News reported.
“Transactions are now posting normally,” a spokesperson said around 6:30 pm Eastern time (2330GMT) Monday.
That update superseded the bank’s earlier statement that it was working to resolve the issue by the end of Monday.
A full assessment would still require more information about how many customers experienced problems, which transactions were delayed and how long individual disruptions lasted.
Was this connected to other recent technology outages?
The banking disruption followed last week’s Microsoft outage and a separate failure affecting US air traffic control communications.
Their timing prompted questions about a possible connection, but public explanations identified different technical problems.
Microsoft attributed its incident to a network issue associated with an earlier capacity upgrade. Chase identified a software bug in its own systems.