The Chase Outage and Zelle Delays: How One Bank’s Software Bug Reached Customers Everywhere

By the Founders, Department of Technology | San Diego, California | November 16, 2026

On Monday, November 16, customers of JPMorgan Chase, the largest U.S. bank, began reporting login problems and slow transactions. Within hours, customers at other major banks, including Bank of America, U.S. Bank, Wells Fargo and Truist, reported transfer delays and Zelle errors, even though some of those banks said their own systems were working. Chase said the cause was a software bug in its own hardware, not a cyberattack, and that by evening transactions were back to normal.

This is a financial story, but it is also a technology story, and it follows two others from the past week. Below, we summarize what has been reported, explain in plain terms why one bank’s bug reached customers of other banks, offer a few suggestions for customers, and set out four questions we believe deserve public answers. The story is still developing, and we rely on published reports and say where accounts differ.

What has been reported so far

Here is what the reporting shows as of Monday night.

  • The scale. By about 2 p.m. Eastern, Downdetector had logged more than 4,700 problem reports for Chase, just over 2,000 for Bank of America and 1,060 for U.S. Bank, according to Time. Hundreds more came in for Wells Fargo, Capital One, Truist and Zelle. Downdetector counts user reports rather than confirmed failures, so these numbers are snapshots, not a measure of total impact.
  • What customers saw. Many Chase customers saw a notice in the app saying some services were not available and asking them to try again later, per Time.
  • Chase’s explanation. Spokesman Joe Evangelisti said Chase had a temporary issue tied to “a software bug in an on-premise hardware system,” and that it was not cyber-related, according to Patch. He added that it was not a systemic issue, and that other banks were affected only to the extent they were on the other side of a transaction with Chase. Chase also said customers still had access to their accounts and funds, as Fox Business reported.
  • Regulators. NBC News reported that, according to a person familiar with the situation, regulators were in touch with the big banks immediately and quickly determined the problem was contained and that service was already being restored.
  • The recovery. Bloomberg reported that Chase said it had fixed the issue, and a Chase spokesperson said Monday evening that transactions were back to normal, per AOL.

What Zelle and the other banks said

The statements from the other institutions tell a consistent story: the delays showed up on their customers’ screens, but the trouble started elsewhere.

  • Zelle. Zelle said, “Zelle is not down,” and explained that people use it through their own banks and credit unions, which manage their accounts and hold their money, according to Fox Business. Zelle’s network is run by Early Warning Services, which is owned by banks including Bank of America, Capital One, JPMorgan Chase, PNC, Truist, U.S. Bank and Wells Fargo, per the Associated Press as relayed in the same report.
  • U.S. Bank. A spokesperson said U.S. Bank systems were not directly affected, but that clients sending or receiving Zelle payments with another institution might see delays, according to Time.
  • Truist. Truist told Dallas News that its system was not part of the widespread problems and that its banking services were operating normally.
  • Bank of America. A spokesperson had no immediate comment when Newsweek asked, although reports of problems at the bank began climbing shortly after noon.
  • Wells Fargo. The picture is less clear. Outlets reported conflicting statements, and, as MLQ noted, no bank has said whether Wells Fargo’s online banking trouble shares a cause with Chase’s bug.

What we do not know

Chase has not said which hardware system was involved, how many customers were affected, or how long the problem lasted. Dallas News reported that the bank did not give a restoration time while it worked on the fix, and NBC News noted it was not immediately clear how many accounts were affected. We also do not know whether other banks’ separate difficulties, such as the Wells Fargo reports, are related.

In our reading, “on-premise hardware” means equipment Chase runs itself rather than a cloud service or an outside vendor. That is useful context, but it does not tell us what failed, what triggered the bug, or what will change. Chase deserves credit for saying early that this was not a cyberattack, because that is the first question the public asks. The questions that come after it are still open.

Why one bank’s bug reached customers of other banks

A transfer between two banks has two ends. When you send money from an account at one bank to an account at Chase, or the other way around, both institutions have to process their side before the payment is complete. Zelle does not hold your money in between. As Zelle itself pointed out, it works through participating banks, which keep the accounts. So when one end slows down, the customer at the other bank can see a delay or an error message even though that bank’s own systems are healthy.

This is our plain-language reading of how the pieces fit, and it matches what Chase and U.S. Bank each said about delays reaching other banks’ customers. It also shows why the size of the bank matters. When the largest U.S. bank has a problem, a great many transfers at other institutions have Chase on the other side.

A bad week for everyday technology

Monday’s outage was the third widely reported technology failure in about a week. On Friday, November 13, the FAA grounded flights nationwide, which we covered in The November 13 Ground Stop and our follow-up. Last week, Microsoft 365 also suffered a widespread outage, and a Microsoft executive said Monday that it was driven by three factors, including a software bug that had gone undetected since July, according to Fox Business.

NBC News reported there is no evidence these incidents are connected to one another, and we are not claiming they are. What they share is a pattern: ordinary systems that tens of millions of people rely on failing in ways that are hard to see coming and hard to explain quickly. A bug that sits unnoticed for months, or hardware that fails on an otherwise normal Monday, is the kind of risk that testing, monitoring and clear ownership are meant to catch.

What customers can do now

These are our suggestions, not guidance from any bank. Outages are exactly when expensive mistakes happen.

  • Check before you resend. If a Zelle payment shows as pending or failed, look at your account activity and ask the recipient to confirm before sending it again, so you do not pay twice.
  • Keep a record. Screenshots of error messages and pending payments will help if a late fee or a missed bill needs to be raised with your bank.
  • Watch the next few days. Scheduled payments and deposits that were timed for Monday may post late or not at all, so review your activity this week.
  • Be careful who you talk to. Outages are a favorite moment for scammers. Use the number on your card or the official app, and never share a code or password with someone who contacts you first.

Where a Department of Technology fits, and where it does not

A Department of Technology would not run Chase, supervise a bank, or fix a hardware bug. Banks already answer to their own regulators, and we are not proposing to replace that. We also cannot say it would have prevented Monday’s failure, since the cause has so far been described in a single sentence. Our narrower claim is the same one we made after the FAA outage: when systems that tens of millions of people rely on fail, the public deserves a clear account afterward, and leaders who understand networks and answer to voters are better placed to ask for it. We make that case in Back to Basics.

Two parts of our proposal bear on this kind of event. The first is public reporting, meaning a plain post-incident explanation of what failed, why, and what will change. The second is shared incident protocols across agencies and industry, so that every institution can answer “is this an attack?” quickly and consistently. Both are part of the thinking behind our work on continuity of government, because payments are infrastructure too.

Four questions for banks and officials

  1. What failed, and why did the fix take hours? Will Chase publish a plain-language post-incident report that names the system involved and what will change?
  2. Who was affected, and will they be made whole? How many customers and payments were delayed, and will anyone who was charged a late fee or overdraft because of the delays be reimbursed?
  3. How are changes tested before they reach customers? Whatever the trigger turns out to be, do critical systems get staged rollouts and rehearsed rollback plans? That is our suggestion and goes beyond any rule we know of.
  4. What happens when one large bank’s slowdown reaches the others? What do banks share with one another and with regulators during an incident, and what should the public be told, and when?

The bottom line

Monday’s outage appears to have been contained, and Chase says customers kept access to their accounts and funds. That matters. But the larger lesson, as with the FAA ground stop, is that systems tens of millions of people depend on can slow down because of one bug in one organization’s equipment, and that the public learned about it through error screens, social media and short statements. Clear reporting afterward is how confidence is rebuilt.

Read our FAA series, starting with The November 13 Ground Stop: What a Department of Technology Would Have Done Differently, then Fiber First? and Build It With the Controllers. For the basics of our proposal, read What Is a Department of Technology? We will update this post as more is reported.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *