Chase Bank Outage Disrupts US Online Banking November 16
Millions of Americans opened their banking apps on Monday, November 16, 2026, and found their money moving in slow motion. The chase bank outage began in the morning and grew through the afternoon, as customers of JPMorgan Chase reported delayed transactions, stale balances, and error messages in online banking. The disruption did not stop at Chase. Customers of Bank of America, Wells Fargo, U.S. Bank, Truist, and Capital One also reported problems, and Zelle payments slowed for transactions that involved Chase. By Monday evening, Chase said transactions were being processed normally again, and the cause was a software bug, not a cyberattack. This article explains what happened, which banks were affected, why one bank’s problem spread so far, and what customers should do if it happens again.
Table of Contents
What Happened During the Chase Bank Outage

JPMorgan Chase confirmed on Monday that a technical problem in its own systems was slowing transactions. The bank said it had “experienced a temporary issue related to a software bug in an on-premise hardware system.” The bug did not take Chase offline, but it slowed transaction processing, so payments and transfers took longer than usual.
Customers saw the problem in different ways. Some saw a message in the Chase app saying balances and pending transactions might not be up to date, while adding that they could still make payments. Others saw a message that read, “Some services aren’t available. We’re working on them. Please try back later.”
Chase spokesman Joe Evangelisti put it plainly: “This is not a systemic issue, other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us.”
The Outage Hour by Hour
Downdetector, which tracks user reports of online service problems, logged the first Chase reports at about 9:53 a.m. ET. Reports climbed through the late morning and peaked at close to 5,000, about 4,800 reports, around 2 p.m. ET.
That stretch gave Chase its second highest 15 minute outage report total in at least a year, according to Downdetector’s parent company Ookla. By 6:05 p.m. ET, reports had fallen to about 1,450. Shortly after 7 p.m. ET, Chase told USA TODAY that transactions were “being processed normally now.”
Why Other Banks Were Affected Too
The most confusing part of Monday was that the problem seemed to hit several banks at once. Downdetector showed report spikes for Bank of America, Wells Fargo, U.S. Bank, Truist, and Capital One, as well as for Zelle. The pattern suggested a system-wide failure, but the banks told a different story.
Bank of America said its systems had operated normally all day, and U.S. Bank said the same. Their own systems were fine, but their customers felt the effects of the chase bank outage whenever a payment had to pass through Chase.
Zelle holds no customer funds and runs no separate accounts. Consumers use it through their own banks, which hold the money. When a Chase customer sent a Zelle payment to another bank’s customer, the transaction touched Chase systems, so the delay showed up on both sides.
Wells Fargo was the exception. It acknowledged a problem of its own, and its website said online banking was temporarily unavailable. By Monday evening it had not confirmed full restoration, though its reports had fallen from above 1,050 to roughly 370 to 400.
Was the Chase Outage a Cyberattack?
With several major banks apparently down at once, many people asked: was this a cyberattack? Chase answered it directly. In an email to USA TODAY, the bank said: “Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds. We are working to resolve this as quickly as possible. This is a technical issue, not cyber related.”
Evangelisti repeated the point in a statement carried by the Associated Press, and technical experts agreed there was no evidence of a cyberattack.
A software bug is a flaw in a bank’s own code or hardware, while a cyberattack is a deliberate attempt by an outsider to break in or shut a system down. No bank, regulator, or news outlet has reported evidence of the second. Customers should still stay alert: criminals often send fake messages during a real outage, claiming an account is locked, and links in unsolicited messages should never be clicked.
What Customers Could Still Do During the Outage

Even while online banking was slow, customers were not cut off from their money. Chase said accounts and funds remained accessible, and many could still make payments, even if balances looked out of date.
When an app or website is unreliable during the chase bank outage, try another route. If the mobile app fails, try the desktop website, or the other way around. If digital channels fail completely, an in-network ATM can provide cash, and a local branch can handle urgent transactions. A bill can also be paid directly through the biller’s website with a backup payment method, such as a credit card.
Do not submit the same payment twice. If a transfer, Zelle payment, or bill payment freezes partway through, sending it again can produce a duplicate charge once systems recover. Wait and check whether the first payment went through, and save screenshots of error messages and timestamps as evidence for any waiver request.
A Week of Technology Failures
The chase bank outage was the third major technology failure in the United States in five days. On Thursday, a Microsoft outage knocked out Outlook and Microsoft 365 for many office workers. On Friday, the Federal Aviation Administration issued a nationwide ground stop that grounded all United States flights for several hours. Monday added banks, and United Airlines reported a separate technology issue the same day.
Investors watching the US stock market today stayed alert, while technology headlines also covered new American chip export rules and the proposed Union Pacific and Norfolk Southern merger.
Experts say the three failures were separate events, not one connected attack. What they share is scale: a few very large companies run the email, air traffic, and payment systems millions depend on, so a single bug can be felt across the country within hours.
What to Do During a Bank Outage
A banking outage is stressful, especially when bills are due, but a few steps can protect your money. First, verify the outage through official channels, such as the bank’s verified social media accounts or status page. Use Downdetector only to confirm that other customers report the same problem.
Next, try another way in. If the app is down, try the website, and if the website is down, try the app. If neither works, use an ATM or visit a branch for urgent transactions. Keep screenshots and times of anything that goes wrong. For guidance on your rights, the FDIC consumer resources page explains deposit insurance and consumer protections.
Frequently Asked Questions
Was the Chase bank outage a cyberattack?
No, according to Chase. The bank said the cause was a software bug in its on-premise hardware systems and that there was no evidence it was cyber-related.
Which banks were affected by the outage?
The chase bank outage started at Chase. Customers of Bank of America, Wells Fargo, U.S. Bank, Truist, and Capital One also reported problems, and Zelle payments were delayed, but only for transactions involving Chase.
Could customers still access their money during the outage?
Yes. Chase said customers still had access to their accounts and funds throughout, although balances sometimes looked out of date.
When was the outage fixed?
Chase told USA TODAY shortly after 7 p.m. ET that transactions were “being processed normally now.” Reports had fallen to about 1,450 by 6:05 p.m. ET, down from a peak of about 4,800.
What should I do if a bank outage delays my payment?
Do not submit the payment twice, because that can create a duplicate charge once systems recover. Check whether the first payment went through, save screenshots of any errors, and ask the bank or biller about a waiver.
Conclusion
The chase bank outage on November 16, 2026, showed how quickly a single software bug can ripple across the American banking system. A fault inside JPMorgan Chase slowed transactions for its own customers and delayed payments at other banks whenever Chase was involved, yet accounts and funds stayed accessible. Chase said the cause was not a cyberattack, and by Monday evening transactions were processing normally again. For customers, the lesson is practical: keep a backup payment method ready, avoid duplicate payments during an outage, and check official bank updates before assuming the worst.