Back

Chase Bank Outage, November 16 2026: Why Wells Fargo, Bank of America and U.S. Bank Lit Up Too

Downdetector made Monday look like a nationwide banking collapse. The confirmed story is narrower: a software bug inside JPMorgan Chase that slowed transactions and dragged on any payment where Chase was on the other end.

Jagdish Patil

•

Incident Overview (TL;DR)

  • What failed: JPMorgan Chase online and mobile banking logins, transaction processing, and some branch systems. Payments between Chase and other banks, including Zelle transfers, were delayed.

  • When it started: Monday, November 16, 2026. Downdetector reports for Chase started trickling in around 9:30 a.m. ET (14:30 UTC) and spiked around midday ET.

  • Peak: Around 2 p.m. ET (19:00 UTC). Counts varied by source and moment. Tom's Guide tracked Chase near 5,000 reports. Fortune reported Chase passing 20,000 by 2:22 p.m. ET.

  • Other banks on Downdetector: About 1,900 to 2,000 reports for Bank of America, and roughly 800 to 1,000 each for Wells Fargo and U.S. Bank, in early afternoon ET. Capital One, Truist and Zelle also spiked, with no published counts.

  • Confirmed cause: Chase blamed a software bug in hardware it runs in its own data centers and said there was no evidence of a cyberattack. An FBI official told Fox Business it traced to a software release Chase rolled out earlier Monday.

  • Status: Recovered. Chase told reporters transactions were posting normally around 6:30 p.m. ET (23:30 UTC), which was already early Tuesday, November 17 in India and much of Asia. Individual delayed payments may still be finishing. No formal incident report has been released.

Affected Institutions and Customer Impact

Downdetector counts people who report a problem. It doesn't confirm an outage. That distinction matters a lot here, because the banks' own statements tell a very different story from the chart.

JPMorgan Chase: confirmed incident. Customers reported failed logins on the website and app, trouble withdrawing funds and stalled transactions. Chase's statement was careful: "some transactions are taking longer than usual to complete," while customers "still have access to their accounts and funds." Not everyone's experience matched that line. Reddit users said tellers told them branch systems were down. A Washington, D.C. teller told Fox Business that problems started around 10 a.m. and cleared just after 3 p.m. A branch employee said the branch computers had "been up and down." ATMs at the branches Fox Business described reportedly worked normally. Plaid said its own network was fine but saw connection problems with Chase accounts, so budgeting and payment apps that link to Chase through Plaid would have stumbled too.

U.S. Bank: spillover delays. U.S. Bank said its "systems are not directly impacted," but warned that clients sending or receiving Zelle payments with other institutions "may experience transaction delays." That's the clearest description of the spillover.

Bank of America: no confirmed fault. Bank of America drew the second most Downdetector reports, around 2,000 at the peak. It told Fox Business its systems were operating normally.

Wells Fargo: unclear. This is the one real contradiction in the record. Early Monday, Wells Fargo's website showed online banking as "temporarily unavailable" and said it was working on technical issues. It pointed customers to ATMs, branches and phone bankers. ABC News later noted the message had come down, and Fox Business reported Wells Fargo saying it was not affected. Whether Wells Fargo had a separate short issue, or briefly posted a precaution during the Chase spillover, hasn't been explained.

Capital One: no confirmed fault. Capital One appeared among the Downdetector spikes, but told Al Jazeera its services were operating normally. Truist said the same, and PNC said it had no direct impact.

What wasn't reported. We found no credible reports of card network failures, wire outages or missed direct deposits tied to this incident. If you saw one of those, check with your bank directly rather than assuming it was part of Monday's event.

Technical Breakdown and Root Cause

What has been confirmed

  • Chase, initially: "Due to a technical issue, some transactions are taking longer than usual to complete."

  • Chase, to Tom's Guide: "This is a technical issue, not cyber related."

  • Chase, later Monday: a temporary issue caused by a software bug in an on premises hardware system, with no evidence of cyber activity. Spokesperson Joe Evangelisti told Al Jazeera "This is not a systemic issue."

  • FBI official, to Fox Business: the disruption traced to a software release rolled out earlier Monday that affected a subset of Chase's systems. Impact was limited to Chase and to transactions at other institutions where Chase was a party.

  • Zelle: "Zelle is not down. Zelle is operating as it should," adding that "an issue at the financial institutions may be impacting broader services."

  • Federal Reserve: its financial services status page showed systems operating normally, which covers its ACH operation between banks.

That's the whole confirmed record. Chase hasn't named the system, the release or why the bug slowed processing instead of failing outright.

Shared vendor, payment rail, DNS, or one bank? (Our interpretation)

When five big brands spike on Downdetector together, it's reasonable to look for a common dependency first. Here's how each candidate holds up against the evidence. This section is our analysis, not anything the banks have confirmed.

A shared outside vendor. It's possible in principle, since banks share core processors, fraud tools and login providers. But no bank pointed to a vendor, and Chase took ownership of a fault in its own hardware. If a shared provider had failed, we'd expect several banks to report direct impact. Instead Bank of America, Capital One, Truist and PNC said they were fine. Weak fit.

A payment rail such as Zelle, RTP or ACH. Zelle said its network was healthy and the Fed said ACH was normal. We saw no reports about RTP at all. A rail failure would also break payments between banks that never touch Chase, and nobody reported that. Weak fit.

A DNS or CDN layer. These failures usually take down websites across unrelated companies in one go, and they don't make posted transactions take longer. Chase's own description points at backend processing, not the front door. Weak fit.

An independent backend failure at Chase, plus spillover. This one fits every confirmed statement. A bad release slows Chase's transaction processing. Any payment with Chase on one end, whether a Zelle transfer from U.S. Bank or a Plaid link, then waits on Chase. That's exactly what U.S. Bank and the FBI official described. Strong fit.

That leaves the reports at banks that said they were fine. Two effects likely explain most of them:

  1. Counterparty delays. A Bank of America customer whose Zelle payment to a Chase account stalls sees the delay in the Bank of America app and reports Bank of America.

  2. Sympathy reporting. Once "banks are down" trends, people check their own bank, hit any small hiccup, and file a report. The Tom's Guide reporter tested Wells Fargo during the peak and could log in fine.

Neither effect explains Wells Fargo's own "temporarily unavailable" banner. That stays an open question until Wells Fargo addresses it.

Context, not a link: this came days after the global Microsoft 365 outage that began November 12 and a nationwide FAA ground stop. No bank or agency has connected those events, and Chase's cause is internal. Three big failures in one week is a coincidence worth noticing, not evidence of a common cause.

Guidance for Customers and IT/Finance Teams

For customers

  • Don't resend payments. A Zelle transfer or bill payment that shows as pending is most likely sitting in a queue, not lost. Sending it again risks paying twice, and a Zelle payment to an enrolled recipient usually can't be canceled once it goes through.

  • Check your activity over the next day or two. Look for duplicates, missing deposits or a delayed transfer that never posts. Raise anything odd through the bank's app or the phone number on the back of your card.

  • Expect outage scams. Banking disruptions bring texts and calls that pretend to be your bank and "help" you restore access. A real bank won't ask for your password, a one time code or a transfer to a "safe account." Hang up and call the number on your card yourself.

  • Get status from the source. Use your bank's app banners, its website and its official support account on X (Chase Support posted during this incident). Downdetector tells you other people are struggling. It doesn't tell you which bank is at fault.

For IT and finance teams

  • Reconcile Monday's activity before rerunning anything. Pull status for every payment, ACH batch and payroll file touching a Chase account on November 16. Rerunning a batch that already processed late is how one incident turns into a duplicate payment problem.

  • Check your idempotency handling. If your systems retried payment API calls during the slowdown, confirm each retry carried the same idempotency key. That's what stops a slow response from becoming a second charge.

  • Audit aggregation links. Plaid reported connection problems with Chase accounts. Any feature that reads balances or starts transfers through an aggregator may have failed quietly on Monday and may need customers to reconnect.

  • Talk to your relationship manager, not the hotline. For treasury or commercial accounts, your Chase contact is the fastest way to confirm whether specific wires or ACH files went out on time.

  • Keep a timeline. Note when your own payments stalled and recovered. You'll want it for vendor conversations and to compare against whatever incident report Chase eventually publishes.

The Monitoring Lesson in a One Bank Outage

The most useful signal on Monday wasn't the Downdetector chart. It was U.S. Bank speaking for itself: its systems were fine, but payments headed to Chase were slow. A crowd chart blurs the outage across every brand. A direct check on the thing you depend on tells you exactly where the break is.

The same applies to anyone running a business that takes money online. If your checkout, payment webhook or billing page breaks because a provider upstream is struggling, you want to hear it from your own check, fast, and not from a customer email hours later.

That's why we built SIOPS around a phone alarm. When an endpoint you monitor stops responding, SIOPS rings a native alarm that bypasses silent mode and Do Not Disturb, and it can also call you. Point it at what you own, like your checkout page, your payment webhook route, or a health endpoint that tests your payment provider. It won't monitor Chase's internals, but it will tell you within a minute that your own payment flow has stopped working. The free Hobby plan covers 5 monitors.

Similar Stories

Similar Stories