Chase Bank Outage Hits Millions as Software Bug Freezes Banking and Zelle

Posted on by Sunil Raval,WNW News Desk 10 minutes read

Chase Bank outage — exterior of a modern American bank branch at dusk with people walking past

The Chase Bank outage on Monday, November 16, 2026, left millions of Americans locked out of their online banking accounts and unable to send money through Zelle for nearly eight hours. The Chase Bank outage began around 9:30 a.m. Eastern time, peaked in the early afternoon with nearly 5,000 complaints logged on the outage-tracking site Downdetector, and was not fully resolved until about 6:30 p.m. Eastern. JPMorgan Chase, the largest bank in the United States, blamed a software bug in its own hardware systems — and insisted the failure was not a cyberattack.

The disruption rippled far beyond Chase itself. Because Chase is a party to transactions at other banks, customers at Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One also reported problems, mostly when their payments touched Chase accounts or the Zelle network that the big banks jointly own. For a few hours on Monday, the plumbing of American retail banking simply did not work the way it is supposed to.

The outage was the third major American technology failure in three straight weekdays, after a Microsoft 365 disruption on Thursday and a nationwide Federal Aviation Administration ground stop on Friday, and it came two days before a United Airlines system failure. Officials say there is no evidence the failures are connected or that any of them was a cyberattack. But the pile-up has raised an uncomfortable question: why do the systems Americans rely on most keep breaking in the same week?

Chase Bank outage — a hand holding a smartphone showing a generic banking app loading screen

What caused the Chase Bank outage?

JPMorgan Chase said the problem was a software bug in an on-premise hardware system — equipment the bank operates itself, rather than cloud services. “JPMorgan Chase has experienced a temporary issue related to a software bug in an on-premise hardware system — it is not cyber-related,” spokesman Joe Evangelisti told the Associated Press. A person familiar with the matter told NBC News that the outage was limited to the retail banking business.

An FBI official told Fox Business that the fault stemmed from a software release Chase rolled out earlier on Monday, which affected a subset of the bank’s systems. The official said there was no sign of malicious or external cyber activity, and that the impact was confined to Chase and to transactions at other institutions in which Chase was a party. Chase spokesman Pablo Rodriguez gave the same account, tracing the problem to a software bug in on-premise hardware systems.

The bank has not disclosed the full root cause of the software bug, the precise number of customers affected, or what it will change to prevent another software release from breaking its network. What is known is that the failure was self-inflicted: an update to the bank’s own physical computer systems went wrong, and the bank spent most of the working day putting it right.

How bad was the Chase Bank outage for customers?

At its worst, the outage left customers unable to log in to their online accounts, check balances or complete transactions, and some branch transactions were delayed as well. Downdetector, which relies on self-reported complaints and can be imprecise, logged nearly 5,000 reports against Chase at the peak around 2 p.m. Eastern, with about half tied to account balances and transactions and smaller spikes at Bank of America, U.S. Bank and Wells Fargo.

Chase said customers still had access to their accounts and funds, and that transactions were taking longer than usual rather than failing outright. But for people trying to pay rent, settle a bill or move money on a Monday, a delay of hours is a failure in practical terms. Zelle, the near-instant peer-to-peer payment system owned by a consortium of major banks, was one of the worst-hit services, because Zelle transfers that involved a Chase account could not complete.

The scale of the bank makes the disruption hard to overstate. JPMorgan Chase is the largest US bank by assets, operates about 5,000 branches and 15,000 ATMs nationwide, and holds more than 10 percent of all deposits in the United States. When its systems slow down, the effects show up in other banks’ apps within minutes, because so many American payments pass through Chase at one end or the other.

Why did the Chase Bank outage spread to other banks?

The outage spread because modern banking is a shared network, not a set of separate vaults. Chase said the disruption was centered on its own systems and affected other banks only when their customers attempted transactions involving Chase. In practice, that covers a huge share of everyday payments: a Wells Fargo customer sending money to a Chase account, a Bank of America customer receiving a Zelle payment from a Chase customer, or any transfer that routes through Chase’s systems.

Zelle was the main channel for the spillover. The payment network is jointly owned by the major banks, and a transaction between a Chase customer and a customer of another bank needs both sides to work. When Chase’s side slowed, the other side’s customers saw their payments stall too, even though their own bank’s systems were fine. Downdetector recorded surges in complaints at Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One during the same hours.

The pattern is a reminder of how concentrated American banking has become. A single institution holds more than a tenth of the nation’s deposits and sits in the middle of a large share of its payments. A software bug at that institution is not a local problem; it is a system problem, and Monday showed how quickly it becomes one.

Was the Chase Bank outage a cyberattack?

No, according to every official account so far. Chase said explicitly that there was no evidence of a cyberattack, and the FBI official who spoke to Fox Business said there was no sign of malicious or external cyber activity. The White House and the Department of Homeland Security have also said the recent run of outages, including the Chase failure, shows no sign of coordinated cyberattacks or state-sponsored activity.

Online chatter blamed AI cyberattacks for the outage, but fact-checkers have called those claims unsubstantiated. The simultaneous warnings about AI-powered hacking tools are a coincidence, not evidence: uncertainty about a root cause is not evidence of AI involvement. The known cause — a flawed software release on the bank’s own hardware — is mundane, and that is part of the point. The systems did not fail because someone attacked them. They failed because an ordinary update went wrong at the biggest bank in the country.

The distinction matters for what happens next. A cyberattack would point to security spending and threat hunting. A botched software release points to change management, testing and the way the bank rolls out updates to systems that millions of people depend on. Chase has not said what it will change, and regulators and customers will be watching for that answer.

What happened after the Chase Bank outage ended?

Chase said the problem was resolved later on Monday and that transactions were processing normally by Tuesday. The bank said it expected services to be fully restored by Monday evening, and by about 6:30 p.m. Eastern, transactions were posting normally again, according to NBC News — meaning the disruption ran for nearly eight hours.

The outage closed a remarkable six days of failures across American technology and infrastructure. Between November 12 and November 17, Microsoft, the FAA, United Airlines, Chase, Apple Pay and the National Security Agency’s classified network all suffered outages. Officials say there is no evidence linking them, and the stated causes are different in each case: a software bug at Chase, a patch gone wrong at the NSA, and separate technical faults elsewhere. The common thread is that institutions were taking systems offline to fix known flaws, and then ran into trouble restarting them.

For Chase customers, the practical lesson is narrower. The bank has not said which system failed, how many customers were affected, or what safeguards will change. Until it does, the outage stands as a warning about concentration risk: when the largest bank in America pushes a bad update on a Monday morning, millions of people at five other banks feel it before lunch.

Key Facts

  • The Chase Bank outage happened on Monday, November 16, 2026, beginning around 9:30 a.m. Eastern and lasting nearly eight hours, with transactions posting normally again by about 6:30 p.m. Eastern.
  • JPMorgan Chase blamed a software bug in an on-premise hardware system and said the issue was not cyber-related; an FBI official told Fox Business the fault stemmed from a software release rolled out earlier Monday.
  • Downdetector logged nearly 5,000 reports against Chase at the peak around 2 p.m. Eastern, about half tied to account balances and transactions, with smaller spikes at Bank of America, U.S. Bank and Wells Fargo.
  • The outage disrupted online banking, Zelle payments and some branch transactions, and rippled to customers at Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One through shared payment rails.
  • Chase spokesman Joe Evangelisti said the bank experienced “a temporary issue related to a software bug in an on-premise hardware system”; spokesman Pablo Rodriguez gave the same account.
  • JPMorgan Chase is the largest US bank by assets, with about 5,000 branches and 15,000 ATMs, holding more than 10 percent of all US deposits.
  • The outage was the third straight weekday of a major US technology failure, after a Microsoft 365 disruption on Thursday and a nationwide FAA ground stop on Friday.
  • Chase has not disclosed the full root cause, the precise number of affected customers, or what it will change to prevent a repeat.

Frequently Asked Questions

What caused the Chase Bank outage?

JPMorgan Chase said a software bug in its on-premise hardware systems caused the outage on Monday, November 16, 2026. An FBI official told Fox Business the fault stemmed from a software release Chase rolled out earlier that day. The bank said there was no evidence of a cyberattack.

How long did the Chase Bank outage last?

The disruption began around 9:30 a.m. Eastern on Monday, November 16, peaked around 2 p.m., and was resolved by about 6:30 p.m. Eastern, lasting nearly eight hours. Chase said transactions were processing normally by Tuesday.

Did the Chase Bank outage affect other banks?

Yes. Customers at Bank of America, Wells Fargo, U.S. Bank, Truist and Capital One reported problems, mostly on transactions involving Chase or on Zelle, the payment network the big banks jointly own. Chase said other banks were affected only when their customers attempted transactions involving Chase.

Was the Chase Bank outage a cyberattack?

No. Chase said there was no evidence of a cyberattack, and the FBI official who spoke to Fox Business said there was no sign of malicious or external cyber activity. Officials have said the recent run of US outages shows no sign of coordinated cyberattacks.

Tags:

Sunil Raval,WNW News Desk

WNW News Desk is the editorial team of World Nation Wire, responsible for reporting and publishing fact-checked news and analysis on global politics, business, economy, sports, and technology, following responsible and transparent journalism standards.

Leave a Reply

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