Pull to refresh
Logo
Software bug at JPMorgan Chase stalls payments across US banks

Software bug at JPMorgan Chase stalls payments across US banks

Built World

A hardware failure inside the largest US lender disrupted transactions at Chase and slowed payments at other banks connected through Zelle.

Overview

Updated 38 minutes ago

Just after 11:30 a.m. Eastern on November 16, JPMorgan Chase customers found that money wasn't moving. Transfers stalled, the app showed 'Some services aren't available,' and the delays reached customers at other banks whose payments passed through Chase.

Chase blamed a software bug in its own on-premise hardware, not a cyberattack, and said customers could still reach their accounts. The incident showed how a single internal failure at the largest US bank can slow the payment network that links competing institutions.

Why it matters

The largest US bank can stall payments across the system with one internal bug, so customers at other banks inherit Chase's failures.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

20,000+
Peak Chase outage reports on Downdetector
User complaints climbed past 20,000 by midafternoon Monday.
7
Banks with reported outage spikes
Chase, Bank of America, Wells Fargo, U.S. Bank, PNC, Citigroup and Capital One.
0
Confirmed links to a cyberattack
Chase said it found no evidence the disruption was cyber-related.

Voices

Curated perspectives — historical figures and your fellow readers.

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

6 events Latest: Today
Tap a bar to jump to that date
  1. Transaction delays begin at Chase

    Today Incident

    Customers start reporting stalled transfers and app errors.

  2. Outage reports surge across major US banks

    Today Incident

    Downdetector spikes at Chase, Bank of America, Wells Fargo, U.S. Bank and Zelle.

  3. Chase blames software bug in on-premise hardware

    Today Statement

    Bank says no evidence of a cyberattack and that accounts remain accessible.

  4. Zelle says its network is operating normally

    Today Statement

    Payment network points to problems at member banks, not its own systems.

  5. Outage reports decline from their peak

    Today Update

    Complaints fall but remain elevated at several institutions.

  6. Microsoft restores service after global outage

    Context

    Outlook and Teams came back online; no link to the bank problems was established.

Scenarios

1

Chase restores full transaction processing within a day

Likely Resolves by Nov 18, 2026

Discussed by: JPMorgan Chase statements; CNBC and Reuters

Chase said it was working to resolve the issue by end of day. If transaction processing returns to normal and no new failures appear, the outage stays a one-day event with limited lasting damage.

2

A federal regulator opens an inquiry into the Chase outage

Possible Resolves by Feb 28, 2027

Discussed by: Banking analysts and trade press

A disruption at the largest US bank that spread to other institutions could draw scrutiny from the Office of the Comptroller of the Currency, the Federal Reserve, or the Consumer Financial Protection Bureau. An inquiry would begin with document requests and could take months.

3

The outage stretches into a multi-day disruption

Unlikely Resolves by Nov 20, 2026

Discussed by: Downdetector data; customer reports

If the software bug proves harder to isolate, delays could persist past Monday and spread further through Zelle payments. That would raise the cost to customers and increase pressure on Chase.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

2010

Chase online banking outage (2010)

JPMorgan Chase's online banking went down for more than a day, locking customers out of account access. Chief Executive Jamie Dimon publicly apologized.

Then

Service was restored and the bank faced customer frustration.

Now

It became a reference point for how the bank handles and communicates technology failures.

Why this matters now

It is the closest precedent for a Chase system failure and the source of the bank's public-apology playbook.

April 2018

TSB Bank IT meltdown (2018)

A botched migration to a new computer system at TSB, a British bank, locked about 1.9 million customers out of their accounts and caused weeks of errors.

Then

Customers could not access funds, and the bank faced fines and a parliamentary inquiry.

Now

The episode became a benchmark for the damage a failed core-banking upgrade can cause.

Why this matters now

It shows how an internal system change, not an attack, can produce a prolonged banking disruption.

August 2012

Knight Capital software failure (2012)

A faulty software deployment at Knight Capital, a US trading firm, sent erroneous orders into the market in about 45 minutes. The firm lost roughly $440 million and nearly collapsed.

Then

Knight was forced into a rescue merger with Getco.

Now

The failure accelerated rules requiring testing of trading algorithms.

Why this matters now

It is the clearest example of a software bug inside a financial firm causing immediate, large-scale market damage.

Sources

(10)