JPMorgan Chase says its systems were back to normal by Monday evening after a software-bug outage that disrupted online banking and delayed some transfers. A Chase spokesman described it as a temporary issue tied to a software bug in an on-premise hardware system, not a cyberattack. If you sent money involving a Chase account, check the transaction in your official banking app before trying again.
If you initiated a Zelle transfer or another payment involving a Chase account during Monday’s outage, check your transaction status before resending funds. Because the failure stemmed from a software bug on Chase’s on-premise hardware systems rather than a failure of the Zelle network itself, Zelle said its network stayed up and that the disruption was tied to transfers involving Chase accounts. Avoid duplicate submissions and watch for post-outage phishing texts.
## Why one Chase bug produced reports at other banks
Chase’s Downdetector reports began climbing shortly after 9 a.m. ET, peaked at roughly 4,800, and had fallen to about 1,780 by 4:45 p.m. ET. Downdetector also logged reports for Bank of America, U.S. Bank and Wells Fargo.
Bank of America said its systems were operating normally. U.S. Bank said its own systems were not directly affected, but customers sending or receiving Zelle payments could see delays with another institution. Zelle, which is operated by Early Warning Services, said its network stayed up and that the reports were tied to transfers involving Chase accounts.
## What federal rules say about a non-cyber outage
The Office of the Comptroller of the Currency says a computer-security incident can include a nonmalicious hardware or software failure that harms a system’s availability. Its rules require a service provider to alert affected banks when covered services are materially disrupted for four or more hours. A bank must notify the OCC within 36 hours after deciding that a notification incident occurred.
For customers, use the app or website you normally use, record the payment time, and do not share a one-time passcode with an unsolicited caller. The [consumer guidance after a major network outage](https://www.karmactive.com/three-mobile-requires-individual-compensation-claims-after-14-hour-network-outage-hits-9300-users/) offers a comparison for documenting a service problem.
## What to do with a pending Zelle payment
Look for a completed, pending or failed status in the official app and keep timestamps if a delayed payment triggers a late fee. Ignore contacts offering to “release” funds. Keeping cash and printed account details is also part of the preparation described in Karmactive’s [emergency-kit guidance](https://www.karmactive.com/be-ready-emergency-kit-uk-2026-checklist-medication-list/).
**Why did reports spike at other US banks on Monday?**
Only JPMorgan Chase reported the software failure. Customers of other banks saw delays when a payment involved a Chase account. Bank of America said its own systems were operating normally, and U.S. Bank said its systems were not directly affected.
**Was the Chase outage a cyberattack?**
No. Chase said the outage came from a software bug in on-premise hardware systems, and it said the issue was not cyber-related.
**Was Zelle itself down?**
No. Zelle’s network remained operational, but a transfer can remain pending when a participating bank cannot promptly confirm its side of the payment.
Chase customers and people waiting on a transfer should continue to check their account status rather than submit a second payment. Karmactive will update this story if the OCC or Early Warning Services publishes a formal account of the outage.
—