Skip to main content

News

Chase Went Down: Is Your Money Safe? What to Do

Chase, Bank of America and Wells Fargo went down on Monday. Your money was never gone — what happened, what FDIC cover really means, and what to do next time.

By MoneyHabit Editorial Team

17 November 2026 · 10 min read

Phone with a frozen banking app and warning sign, brass shield and seedling from a gold coin, bank tower behind
In this article

On Monday, 16 November 2026, the largest bank in the United States went dark — at least on screen. Chase customers woke to login errors, missing balances and transfers that would not go through. Within hours, Bank of America, Wells Fargo, U.S. Bank, Truist and Zelle users were reporting problems too. By the evening, Chase said transactions were posting normally again. Your money was never gone. But the outage showed how fragile the systems we trust with our money really are — and how unprepared most of us are when they stop working.

Here is what happened, what it means for your money, and the backup plan worth building before the next one.

What happened on Monday

Chase was first on Downdetector, the outage tracker, at 9:53 a.m. Eastern. Reports climbed fast — more than 2,000 by 11:04 a.m. and close to 5,000 by 2 p.m. Customers could not log in, balances were missing or wrong, and transfers would not complete. Some saw an in-app banner: "Some services aren't available. We're working on them. Please try back later."

Chase acknowledged the problem on X at 12:48 p.m. and issued a fuller statement at 3:57 p.m. By about 6:30 p.m., a spokesperson told NBC News transactions were posting normally again; shortly after 7 p.m., the bank told USA Today they were "being processed normally now". Plaid, the service behind many budgeting apps' bank connections, marked its Chase incident resolved early Tuesday.

Time (ET), Mon 16 NovWhat happened
9:53 a.m.First Chase reports appear on Downdetector
12:48 p.m.Chase acknowledges the problem on X
~2 p.m.Reports peak near 5,000 (Chase); ~2,000 BofA, ~1,000 each Wells, U.S. Bank
3:57 p.m.Chase issues its statement blaming a software bug
~6:30 p.m.Chase tells NBC News transactions are posting normally again

Downdetector counts reports, not customers — the real number was almost certainly higher. Chase serves more than 86 million people; a few thousand reports is the visible tip, not the size.

Why one bank's bug slowed other banks

Why did Bank of America, Wells Fargo, U.S. Bank and Truist customers report problems too? Chase's answer: the problem was not systemic — other banks were slowed only on transactions involving Chase. A payment often passes through more than one bank — a transfer to a Chase account, a Zelle payment routed through Chase's systems, a card transaction settled between banks. If one end of that chain stalls, the other end feels it. Zelle saw the same effect: more than 500 Downdetector reports by early afternoon, 69% about funds transfers.

Your bank app is only the front door. Behind it sits a web of shared pipes — and a blockage in one of them can back up the whole street.

Was it a cyberattack?

No — nothing published so far points to one. Chase said the cause was "a temporary issue related to a software bug in on-premise hardware systems" and that there is "no evidence this is cyber-related". Spokesman Joe Evangelisti added: "This is not a systemic issue." A source familiar with the matter told Fox News the same: a technical bug, not a cyber issue.

The timing is worth noting: the third major technology failure in seven days, after an FAA outage that grounded flights nationwide for four hours and a Microsoft outage that blacked out Office 365 for nearly 24 hours. The causes differed, but as Notre Dame IT expert Mike Chapple told CBS News, they all point to "the complexity and fragility of the systems that we depend on every day".

The viral "November 17" rumour — false

While the outage was still unfolding, a claim spread online that bank balances would be wiped and the internet shut down on 17 November. It was false: it traces to an anonymous source, no regulator has said any such thing, and by Monday evening Chase was already saying transactions were posting normally again.

Do not move money, close accounts or buy "protection" because of a viral post about banks collapsing. Check the bank's own status page and a reputable news outlet first — if neither is reporting it, it is a rumour, and acting on it is how people lose real money to scammers.

Is your money safe during a bank outage?

Yes — in the sense that matters most. An outage is not a bank failure. In the US, deposits at FDIC-insured banks are covered up to $250,000 per depositor, per ownership category, per bank — a single account and a joint account are covered separately, as is an IRA. The FDIC says that "since the FDIC was founded in 1933, no depositor has lost a penny of FDIC-insured funds". But that insurance pays out when a bank fails. An app outage is a technical problem: the deposits are still in the account, you just cannot see or move them until the service comes back.

WhatFDIC-insured?
Checking, savings and CDsYes — up to $250,000 per depositor, per category, per bank
Stocks, bonds and mutual fundsNo — even if bought through your bank
Crypto assets and annuitiesNo
Safe deposit boxes and their contentsNo

Remember: the limit is per ownership category, not per account, and a balance that looks wrong mid-outage is usually a display problem. Transactions in flight generally post once the system recovers.

What to do when you cannot log in

  1. Do not re-send a payment. If a payment seemed to fail, wait until you can see your account history before trying again — it may have gone through, and sending it twice means paying twice.
  2. Try another channel. When the app and website are down, the ATM, a branch and phone banking often still work — Wells Fargo told customers exactly that on Monday. Your debit card will usually still work at shops too — card payments run on separate networks.
  3. Check the official status, not social media. The bank's X account or status page, and Downdetector, will tell you whether it is just you or everyone.
  4. Protect any bill due that day. If a payment was due, contact the biller — most have grace periods, and a documented outage is a strong reason to waive a late fee. Afterwards, check the payment posted, and screenshot errors and balances: if a fee follows, that paper trail gets it reversed.
  5. Escalate if it is not fixed. If your account is still wrong, complain to the Consumer Financial Protection Bureau — most companies respond within 15 days. The CFPB takes complaints online or by phone at (855) 411-2372.

The most useful habit is the boring one: check your account history before you act. Almost every duplicate payment starts with someone tapping "send" twice because the first tap seemed to do nothing.

Watch out for the scams that follow an outage

Outages are prime hunting season for scammers. Within hours of a bank going down, fake "your account is locked" texts and emails circulate, with bogus support numbers and links to lookalike login pages. The playbook is always the same: urgency, a link, and a request for your password, one-time code or card number.

Your bank will never text or email asking for your password or a one-time code, or ask you to log in through a link. If you get one, do not click it — open the bank's app yourself. If you already clicked a link or shared a code, call the number on the back of your card immediately and change your password from the official app.

Build a backup plan before the next outage

Monday's outage lasted most of a business day; the next could last longer. A backup plan need not be complicated — it just needs to exist.

  • Keep a second account at a different bank. Even a basic no-fee account with a small balance covers groceries and fuel. The point is a different bank, not a different app from the same bank.
  • Keep some cash at home. A modest buffer for a few days of essentials covers the gap when cards and apps both fail — the one backup that works when every screen is down.
  • Carry a card from a different issuer. A credit card from a different bank gives you a second way to pay.
  • Keep your emergency fund reachable. An emergency fund reachable only through one app is less useful than it looks — keep part of it reachable by phone or branch too.
  • Save statements and key numbers offline. A recent statement — paper or PDF — gives you your balance and account number when the app will not. Keep the bank's phone number in your contacts.

The UK version: Barclays, January 2025

This is not an American problem. Barclays suffered a three-day outage from the morning of 31 January 2025, leaving customers unable to log in or make payments. The timing could hardly have been worse: 31 January is the self-assessment tax deadline and payday for many workers. Barclays later said it expected to pay £5–7.5 million in compensation, on top of nearly £5 million for earlier outages — 33 between January 2023 and February 2025.

The UK safety net works the same way, with different numbers: the Financial Services Compensation Scheme protects up to £85,000 per person, per bank, if a bank fails — not if its app stops working.

Frequently asked questions

Did anyone lose money in the Chase outage?

No bank has reported lost money. Chase said customers kept access to their accounts and funds, and transactions were posting normally again by Monday evening. Balances that looked wrong were display delays, not missing deposits.

Was the Chase outage a cyberattack?

No. Chase blamed a software bug in its on-premise hardware; other banks were slowed only on transactions involving Chase.

Is my money covered if my bank's app goes down?

FDIC insurance covers bank failure, not app outages — but an outage does not put your deposits at risk either. Your money stays in your account; you just cannot see or move it until the service returns.

What should I do if a payment failed during the outage?

Wait until you can see your history and check whether it posted before sending it again — re-sending is how duplicate payments happen. If a fee resulted, ask the bank to reverse it, and complain to the CFPB if it will not.

Key takeaways

  • Chase, Bank of America, Wells Fargo, U.S. Bank, Truist and Zelle all had problems on Monday 16 November — a software bug, not a cyberattack.
  • Transactions were posting normally again by Monday evening; no bank reported lost money, and the viral "balances wiped" claim was false.
  • FDIC insurance covers up to $250,000 per depositor, per ownership category, per bank — but it covers bank failure, not an app outage.
  • During an outage, never re-send a payment until you can see your history; try the ATM, branch or phone banking instead.
  • The real fix is a backup plan built in advance: a second account at a different bank, some cash at home, a card from another issuer, and statements saved offline.

The outage ended quietly, with a statement and a slow return to normal. The people who suffered most had no other way to reach their money — no second account, no cash, no card from another bank, and a bill due that day. Set up the second account this week, while your main bank is working. The next outage will not send a warning first.

Sources

Share this article

MoneyHabit Editorial Team

The MoneyHabit editorial desk researches, writes and reviews every article against our editorial policy.

More from MoneyHabit Editorial Team

The Sunday Habit

One useful money idea, every week.

A short, practical email every Sunday — no spam, no selling your address, unsubscribe anytime.

Advertisement

More in Money News & Explainers