Updated 21 November 2026, with statements from JPMorgan Chase, Visa and Mastercard.
It has been an unsettling week for anyone who checks a bank app before breakfast. On Monday, 16 November, a software bug at JPMorgan Chase slowed online banking and delayed some Zelle payments, with knock-on errors reported by customers of other big US banks. On Thursday, Chase said hackers had reached some customer names and email addresses held by outside marketing vendors, and Visa and Mastercard confirmed separate third-party incidents. Police are now warning that scammers use exactly this kind of week to send fake “your account is frozen” messages.
None of this means your money has gone anywhere. It does mean the next text or email that claims to be from your bank deserves more suspicion than usual. Here is what actually happened, what was and wasn’t exposed, and the few steps worth taking now.
Key takeaways
- The 16 November Chase disruption was a software bug, not a cyberattack, the bank said. Services were back to normal by that evening.
- The separate vendor breach exposed marketing data that may include names and email addresses, according to Chase. Visa and Mastercard said no card numbers or payment data were affected.
- Leaked names and emails are exactly what a convincing phishing message needs. Don’t click links in unexpected “account alert” messages. Call the number on the back of your card instead.
- FDIC insurance protects deposits at insured banks up to at least $250,000 per depositor, per bank. Federal rules also limit what you lose to unauthorised transfers, but only if you report them quickly.
What went wrong on Monday
Outage reports for Chase started climbing around 10 a.m. Eastern on 16 November and peaked at nearly 4,700 at 2 p.m., according to Downdetector figures reported by Banking Dive. Customers of Bank of America, Wells Fargo and U.S. Bank, and to a lesser degree PNC, Capital One and Truist, also reported errors. Most Chase complaints were about balances and transactions, with smaller shares about logins and transfers.
Chase said on X that the problem was “a software bug in on-premise hardware systems” and that “there is no evidence this is cyber-related.” It added that customers “still have access to their accounts and funds.” Other banks were affected only where they were on the other side of a transaction with Chase, which is why some Zelle payments between banks were slow. By Monday evening, transactions were processing normally.
The data leak is a separate story
On Thursday, Chase said third parties that provide services to the bank had been hit by a cyberattack. “Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses,” the bank said, in a statement reported by BleepingComputer. Chase said the incident did not disrupt its services and was unrelated to Monday’s outage.
Visa said its incident involved a third-party provider in Asia Pacific and that “no payments data such as card numbers were affected.” Mastercard said a third-party provider had exposed “a limited amount of email addresses” belonging to a small group of cardholders enrolled in a specific benefit program, and that the exposure had been contained, according to Cybersecurity Dive. A ransomware group calling itself n0n has claimed the attacks. Security researchers quoted by Cybersecurity Dive said its claims about major brands should be treated with caution, and the companies have not publicly named the vendor involved.
So the realistic risk for most people is not an empty account. It is a well-targeted email or text that uses your real name and arrives at the address your bank actually uses.
What fake “outage” messages look like
Local police in Texas warned this week that criminals routinely use service interruptions to send fraudulent texts, emails and calls, FOX 26 Houston reported. The common versions say your account has been frozen, a payment failed during the outage, or you must “verify” your details to restore access. Caller ID can be spoofed, so a call that appears to come from your bank’s real number proves nothing.
The advice from Capt. Jonathan Zitzmann of the Harris County Precinct 4 Constable’s Office was simple: don’t respond, don’t click, and “turn that card around, look at the phone number on the back, call that phone number.” A real bank problem will still be there when you call the number you already trust.
Five things to do this weekend
- Use your own route in. Open your bank’s app or type its web address yourself. Never sign in through a link in a message, even one that uses your name.
- Turn on transaction alerts. Instant alerts mean you see a payment you didn’t make in minutes, not at the end of the month. Money.com’s guide to this week’s outages also suggests unique passwords, up-to-date devices and digital wallets or virtual cards, which keep your real card number away from merchants.
- Never share a one-time code. Your bank doesn’t need the code it just sent you. Anyone asking for it is trying to get into your account.
- Check your statements line by line. Small test charges often come before larger ones.
- Keep a small cash and savings buffer. An outage that delays a payment for a day is annoying, not a crisis, if you have money set aside. Our guide to how big your emergency fund should be and the emergency fund calculator can help you size one. Pulling all your cash out of the bank is not the answer.
Is my money safe in the bank?
Yes, if it is in a deposit account at an insured institution. The FDIC insures checking, savings, money market deposit accounts and CDs at insured banks to at least $250,000 per depositor, per bank. The National Credit Union Administration gives similar cover at federally insured credit unions. Deposit insurance covers bank failure, not fraud, but there is separate protection for that. If your high-yield savings is with an online bank, our guide to high-yield savings accounts in the US explains how to check that insurance applies.
For debit cards and bank transfers, the Consumer Financial Protection Bureau says your liability for a lost or stolen card is capped at $50 if you report it within two business days, and can rise to $500 if you report it later. If an unauthorised transfer shows up on your statement, report it within 60 days of the statement being sent. Otherwise you could be liable for later transfers. The details are in the CFPB’s guide to getting money back. Speed matters more than anything else.
If you already clicked
Call your bank’s fraud line first, using the number on your card or its official website, so it can try to stop pending payments. Then change your online banking password and any account that shares it, and report the incident to local police. You can also report the scam to the Federal Trade Commission at ReportFraud.ftc.gov. If a scam has already cost you money on a card, our explainer on how credit card interest works covers what a disputed balance can cost while it is being resolved.
For more on how investment and payment scams are dressed up to look legitimate, see our earlier report on the BTCMining Limited shutdown.
This article is general information, not personal financial or legal advice. Figures and statements are as reported on the dates shown in the linked sources.
FAQ
Was my Chase card number stolen?
Chase has said the vendor breach involved marketing data that may include names and email addresses. Visa and Mastercard said no card numbers or payment data were affected by their incidents. If you are worried, check your recent transactions in the app you normally use and call the number on your card.
Was the Chase outage a hack?
No, according to Chase. The bank said the 16 November disruption came from a software bug in on-premise hardware and that there was no evidence it was cyber-related.
Should I withdraw my cash?
No. Deposits at FDIC-insured banks are insured to at least $250,000 per depositor, per bank, and an app outage doesn’t touch your balance. Keeping large amounts of cash at home brings its own risks.


