Tuesday, 17 November 2026

Is Chase outage fixed? Yes, but check for double payments

Chase says everything is back after Monday's software bug, but missed bills, double charges and outage-themed scams can still cost you. Here's what to check, and how.

Bank branch entrance and ATM at dusk on a wet city street

The short version

  • JPMorgan Chase says transactions were processing normally again by about 6:30 p.m. ET on Monday, November 16.
  • The bank blamed a software bug in its own on-premise systems, and an FBI official saw no sign of a cyberattack.
  • Bank of America, Wells Fargo, Capital One and Zelle said their own systems kept working, though Chase-linked payments slowed.
  • Customers should check for failed or duplicate payments and can ask banks to reverse fees caused by the outage.
Quick read · 1 min

The Chase outage is over. JPMorgan Chase said transactions were back to normal by about 6:30 p.m. ET on Monday, November 16, after a software bug in its own systems slowed payments, transfers and balance checks for hours. An FBI official said there was no sign of a cyberattack.

Customers at other banks noticed it too, because Chase-linked payments stalled. Bank of America, Wells Fargo, Capital One and Zelle said their own systems kept working.

What to do now:

  • Check for bills that didn't get paid on Monday, and for anything charged twice.
  • Ask your bank to reverse any late, overdraft or NSF fee the outage caused, with screenshots as proof.
  • Ignore calls, texts or emails about the outage that ask you to move money or share a code.

Yes, the Chase outage is fixed. JPMorgan Chase said transactions were processing normally again by about 6:30 p.m. ET on Monday, November 16, and by early Tuesday the tracking site Downdetector showed the bank and Zelle back to normal. The cause was a software bug inside the bank’s own systems, not a hack.

That’s the good news. The less comfortable part is what the glitch may have left behind in your account. For several hours, payments stalled, transfers to other banks crawled and some people couldn’t see their balances at all. If a mortgage, card bill or rent payment was due that day, it’s worth checking now that it actually went through, and only once.

01

Is the Chase outage fixed? What the bank says now

JPMorgan Chase says its systems are back and money is moving normally. A spokesperson put the recovery at around 6:30 p.m. Eastern on Monday, and the bank separately said that evening that operations had returned to normal.

The trouble began Monday morning. A teller at one Washington, D.C., branch said problems both in the branch and online started around 10 a.m. and cleared there shortly after 3 p.m. Elsewhere, reports on Downdetector were still climbing at 2:20 p.m. ET and only began to ease around 4 p.m.

At the worst point, Downdetector had logged nearly 4,800 reports about Chase by 2 p.m. ET. People said they couldn’t check balances, send wires, deposit checks or move money. One Texas customer was told by a teller at a Dallas branch that the system was down.

Chase serves more than 86 million customers through about 5,000 branches, so even a partial slowdown reaches a lot of people. The bank hasn’t said how many accounts were hit, and its statements haven’t mentioned any compensation.

Phone with a dark screen beside paper bills on a kitchen table
02

What broke: a software bug, not a cyberattack

JPMorgan Chase blamed a temporary bug in what it called on-premise hardware systems, meaning computers the bank runs in its own facilities rather than rented cloud servers. It said there was no evidence the problem had anything to do with a cyberattack.

An FBI official backed that up, saying there was no sign of malicious or outside activity. The official traced the disruption to a software release the bank rolled out earlier on Monday that affected part of its systems.

The bank hasn’t said exactly what the bug was. It did stress that this wasn’t a failure of its whole network: customers kept access to their accounts and money, it said, but some transactions took much longer than normal.

The timing made people nervous. The outage landed days after a Microsoft disruption that knocked out Outlook and Teams and a nationwide FAA ground stop on Friday, and United Airlines reported its own system outage on Monday evening. There’s no evidence the incidents are linked, and United said its problem wasn’t about cybersecurity.

Chicago security expert Andrew Hoog offered a wider theory: companies are under pressure to patch software faster to stay ahead of AI-assisted attackers, and that speed will bring more service hiccups across industries. That’s his read on the trend, since the precise cause at Chase remains unclear.

03

Were Bank of America, Wells Fargo and Zelle down too?

Mostly not, according to the companies themselves, though plenty of their customers felt something. Downdetector showed spikes for Wells Fargo, Zelle, U.S. Bank, Bank of America and Capital One, with smaller bumps for TD Bank and Citi.

The banks tell a different story:

  • Bank of America said its systems had been running normally all day.
  • Wells Fargo and PNC said Monday’s problems didn’t touch them.
  • Capital One said it wasn’t affected and kept operating as usual.
  • U.S. Bank said its own systems weren’t directly hit, but Zelle payments to or from another bank might be delayed.
  • Zelle said its network was working as designed, adding that trouble at member banks can still slow payments for some customers.

Both versions can be true at once. Chase said that when it was one side of a transaction with another bank, that bank may have been affected too. So a Wells Fargo customer waiting on money from a Chase account could have seen a real delay without Wells Fargo breaking anything.

Zelle’s setup explains why. People don’t hold money in a Zelle account; they use it through their own bank or credit union. Its network operator, Early Warning Services, is owned by several big banks, Chase among them.

Server racks with blue lights and one amber warning light
04

What the Chase outage means for your bills and fees

The biggest risk now is a payment that quietly failed. Adam Taub, a consumer protection lawyer based in Southfield, near Detroit, said most people hurt by the outage will be those with a bill due that day whose payment never went through. A missed mortgage payment, for example, could bring a non-sufficient funds (NSF) fee.

He also flagged the opposite problem: duplicate payments, where a creditor’s charge goes through twice because the glitch interrupted the first attempt.

Fees caused by the outage are worth challenging. The Consumer Financial Protection Bureau’s standing advice for bank outages says you can ask your bank to reverse late, overdraft or insufficient-funds fees the disruption caused, and to credit charges you ran up while working around it. Taub said his clients get such fees removed over the phone about half the time, although banks sometimes make you work for it.

Expect scammers to use the news. Craig Timm of the anti-money-laundering group ACAMS said customers should assume they’ll be targeted with fake bank alerts, phishing texts and emails. The Federal Trade Commission has long flagged a familiar trick: someone phones pretending to be your bank, says they’ve caught suspicious activity and urges you to shift your savings into a so-called protected account. Never move it and never share a verification code; call your bank on the number printed on your statement instead.

05

How to check a missed or double payment after the outage

  1. Go through every transaction since Monday morning, looking for payments that should have left your account but didn’t, and for anything charged twice.
  2. Check automatic withdrawals and scheduled payments. If one didn’t go out, the CFPB suggests paying another way if you can.
  3. For Zelle transfers, open the activity section in your bank’s app or website. A completed status means the money reached the other person’s bank; a pending one can mean they haven’t enrolled the phone number or email you used.
  4. Save screenshots of failed transactions and error messages. Security expert Kayne McGladrey said these can help when you ask for a fee to be reversed.
  5. If the app still acts up, try an ATM, your card, phone banking or a branch, which often keep working when apps don’t. Taub prefers going in person and asking a manager what can be done.
  6. Ignore unsolicited emails about the outage and get updates only from your bank’s official channels.

If you find a real error, such as a wrong or missing transfer, the federal rule known as Regulation E gives you a formal route. You generally have 60 days after the bank sends the statement showing the problem to report it, including your name, account and the type, date and amount of the error. Just asking whether a payment went through doesn’t count as a dispute, so say clearly that you believe there’s a mistake.

Banks generally get 10 business days to investigate and should tell you the result within three business days after finishing. Some cases can run to 45 days, with rules on temporary credit while they look. If the bank won’t fix it, you can complain to the CFPB, which asks for dates, amounts and copies of statements or letters.

06

Quick answers

Is Chase down right now?

No. Chase said transactions were processing normally by Monday evening, and Downdetector showed Chase and Zelle back to normal by early Tuesday. If something still fails, try an ATM or phone banking and contact Chase directly.

Was the Chase outage a hack?

There’s no evidence of that. Chase blamed a software bug in its own systems, and an FBI official said there was no sign of malicious or outside cyber activity.

Will Chase refund fees from the outage?

Chase hasn’t announced any compensation. You can still ask it to reverse late, overdraft or NSF fees the outage caused, and screenshots of failed payments will help your case.

You're reading the quick version.