
US Bank Outage: Chase Software Bug Disrupts Banking and Zelle Payments
*Disclaimer: We may earn a commission if you make a purchase through our affiliate links, at no extra cost to you.
A software bug at JPMorgan Chase disrupted online banking and payments for thousands of customers across the United States on Monday, with the knock-on effects reaching Bank of America, Wells Fargo and the Zelle payment network. Downdetector reports peaked at around 2pm Eastern Time as customers reported login failures, slow transactions and delayed money transfers.
Chase moved quickly to rule out foul play, blaming a temporary fault in its own hardware systems and stressing that customer funds were never at risk. By Monday evening the bank said transactions were posting normally again, closing a day of disruption that showed how far a single bank’s technical fault can travel through America’s shared payment plumbing.
US Bank Outage — Quick Reference Summary
| Detail | What happened |
|---|---|
| Event | US bank outage affecting online banking and payments |
| Date | Monday, 16 November 2026 (United States) |
| Trigger | Software bug in a JPMorgan Chase on-premise hardware system |
| Cyberattack? | No — Chase said there was no evidence of malicious activity |
| Banks named in reports | JPMorgan Chase, Bank of America, Wells Fargo, US Bank, Truist, Capital One |
| Payment service affected | Zelle transfers delayed where Chase was party to the transaction |
| Peak disruption | Downdetector reports peaked around 2pm ET (19:00 GMT) on Monday |
| Resolution | Chase said transactions were posting normally again from about 6:30pm ET on Monday |
| Customer funds | Chase said customers still had access to their accounts and funds |
How a Chase software fault spread to other banks
The disruption began inside Chase’s own systems. Chase spokesman Joe Evangelisti said the bank had “experienced a temporary issue related to a software bug in an on-premise hardware system” and added that it was not cyber-related. The fault slowed transaction processing at Chase, and because banks settle payments with each other constantly, the delay spilled over to customers of other banks whenever Chase was on the other side of a transfer.
That shared plumbing explains why customers of several banks saw problems at the same time even though most of those banks had no fault of their own. According to Al Jazeera’s report on the outage, the disruption extended to customers of at least five other banks. US Bank said its own systems were not directly affected, while Bank of America and Citigroup reported no issues with their own banking platforms.
Downdetector, which tracks outages through user reports, recorded more than 3,300 complaints involving Chase and around 1,400 combined for Bank of America and Wells Fargo. A separate count put Chase reports at nearly 5,000 and Bank of America at about 2,100, showing how widely the disruption was felt even as the banks themselves played down the scale.
Which banks and services were hit hardest
Chase bore the brunt of the disruption, with customers reporting error messages when logging in and long waits for transactions to clear. Some Chase users trying to log in were met with a notice saying some services were not available and asking them to try again later. Zelle, the near-instant payment system used by major US banks, was also hit, with customers reporting delays sending and receiving money.
Bank of America, Wells Fargo, US Bank, Truist and Capital One all appeared in Downdetector listings, though the picture varied sharply from bank to bank. Chase confirmed a technical problem of its own, while other banks said their systems were operating normally and only transactions involving Chase were affected. The contrast underlines a recurring feature of modern banking outages: the bank named in the headlines is not always the only one whose customers feel the pain.
The episode echoed the United Airlines outage a day earlier, when a technology failure delayed hundreds of flights across the US — a reminder that a single point of failure can ground planes and freeze payments alike.
What Chase and the other banks said
Chase’s message to customers was consistent through the day: a technical issue was making some transactions take longer than usual, but customers still had access to their accounts and funds. Evangelisti stressed that the problem was a Chase-only issue, saying there was no evidence of cyber involvement and that other banks were affected only by slowness in transactions where they dealt with Chase.
US Bank told customers its systems were not directly impacted, while warning that Zelle payments involving another financial institution could still be delayed. Capital One and Truist also said their services were operating normally. The careful wording from each bank reflected the same underlying fact: the fault sat in one place, but the payments system connects everyone.
By shortly after close of business on Monday, at approximately 6:30pm Eastern Time, Chase said transactions were posting normally again, according to NBC News. The bank had earlier said it was working to restore full service by the end of the day.
Is your money safe? What customers should do
Chase said throughout the outage that customer funds were safe and accounts remained accessible, with only the speed of some transactions affected. No bank reported money going missing, and there was no evidence of unauthorised access to accounts. Customers who saw a delayed payment were advised to wait for it to post rather than sending it a second time, which could create a duplicate transfer.
Anyone still seeing a missing or duplicated transaction after Monday evening should check their account statement first and then contact their bank with the transaction reference. For Zelle payments, the receiving bank can confirm whether a transfer is still in transit. Keeping screenshots of error messages and payment confirmations makes any dispute easier to resolve.
A second major outage inside a week
The banking disruption followed a major Microsoft outage last week that disrupted Outlook, Teams and the Copilot assistant for hours on 12 and 13 November 2026. Microsoft has since apologised for that disruption. Two large-scale technology failures in the space of a few days have put fresh focus on how much daily life depends on a small number of shared systems.
Chase is the largest bank in the US, serving 86.6 million consumers and 7.4 million small businesses, according to its own website. When a bank of that size hits a fault, the effects are felt far beyond its own customer base — and regulators, customers and rival banks will all want to know what went wrong and how it is being prevented next time.
Frequently Asked Questions
What caused the US bank outage?
A software bug in an on-premise hardware system at JPMorgan Chase slowed transaction processing on Monday, 16 November 2026. Chase said the fault was temporary and not cyber-related.
Was the bank outage a cyberattack?
No. Chase spokesman Joe Evangelisti said there was no evidence the disruption was cyber-related, and the bank described it as a software bug in systems it runs in-house.
Which banks were affected by the outage?
Customers of JPMorgan Chase, Bank of America, Wells Fargo, US Bank, Truist and Capital One reported problems, along with delays to Zelle payments. Not all of those banks had faults of their own — several said only transactions involving Chase were affected.
Is my money safe after the Chase outage?
Chase said customers still had access to their accounts and funds throughout the disruption, and no bank reported money going missing. Only some transactions took longer than usual to complete.
Are Zelle payments still delayed?
Chase said transactions were posting normally again from about 6:30pm ET on Monday. Any payment still not showing after that should be checked with the sending or receiving bank.
Myth-busting: what the outage was not
Myth: hackers took down America’s biggest banks. The evidence points the other way: Chase identified a software bug in its own hardware, said there was no sign of malicious activity, and other banks confirmed their own systems were not breached.
Myth: every bank’s system failed at once. Only Chase confirmed a fault in its own systems. Other banks appeared in outage trackers because their customers’ transactions with Chase were slowed, not because their own platforms went down.
Myth: customers lost their money. No bank reported lost funds. The disruption delayed transactions; it did not remove money from accounts, and Chase said access to accounts and funds continued throughout.



