
Chase bank outage: what happened, why several banks went down and what to do
According to Chase, Monday's outage at Chase and other U.S. banks on November 16, 2026 was caused by a technical bug and not a cyberattack. The bank says customers still have access to their accounts and funds, though some transactions are taking longer than usual. Nobody has confirmed the root cause yet, or why several banks drew complaints at the same time, or when service will be fully back.
We're writing this while the incident is still unfolding. The latest update we found was posted at 3:11 p.m. Eastern (20:11 UTC) in Tom’s Guide’s live coverage. Below we separate what is confirmed from what is our analysis, and finish with what to do today.
What happened: the U.S. online banking outage
Starting Monday morning, Chase customers began reporting that they could not log in on the web, see balances or move money. CBS News reports that complaints began in the morning and grew through the afternoon. Complaints also spiked for Bank of America, U.S. Bank, Capital One, Truist, Wells Fargo and the payments app Zelle. According to reporting from the USA Today network, Downdetector showed problems at Wells Fargo, Bank of America, Chase and TD Bank shortly after noon.
Downdetector numbers vary by time and outlet, and they need careful reading: they count user reports, not affected customers.
| Time (ET) | Data point | Source |
|---|---|---|
| 11:04 a.m. (8:04 a.m. PT) | More than 2,000 Chase reports; web login was the most common complaint | GV Wire |
| 12:48 p.m. (17:48 UTC) | Chase’s support account on X acknowledges an online banking issue | FourWeekMBA |
| Around 1:00 p.m. (10 a.m. PT) | Reports suddenly spike | Tom’s Guide |
| 1:55 p.m. | More than 4,700 Chase reports, more than 2,000 for Bank of America, more than 1,000 for Wells Fargo | NBC Miami |
| Monday afternoon | Nearly 10,000 total Chase reports | GV Wire |
| 3:11 p.m. | Latest live-blog entry we reviewed | Tom’s Guide |
Other outlets took lower snapshots at other times: Yahoo Finance counted more than 1,900 reports for Bank of America, more than 900 for U.S. Bank and 800 for Wells Fargo. There is no official count of affected customers because no bank has published one.
What the banks said
- Chase: a spokesperson told the AP it was “a technical bug issue, not a cyber issue,” as reported by CBS News. In a separate statement, Chase said some transactions were slower than usual but customers kept access to their accounts and funds (USA Today network). The app showed a notice that some services were unavailable (NBC Miami).
- Wells Fargo: its website said online banking was temporarily unavailable and directed customers to ATMs, branches and phone bankers available 24/7 (NBC Miami).
- U.S. Bank: a spokesperson said its systems were not directly impacted, but clients sending or receiving Zelle payments with another bank could see delays (41NBC).
- Bank of America, Wells Fargo and U.S. Bank have not given a cause, and no bank has said when service will be fully restored (Yahoo Finance).
On ATMs, a report citing Reuters mentions Chase customers having trouble with both online and in-person services. No one has officially confirmed an ATM failure. JPMorgan shares fell more than 2.4% and Bank of America more than 2.1% on a day the broader market was also down (Fox Business), so the drop can’t be blamed on the outage alone.
Context matters here. This comes days after the global Microsoft 365 outage, which Al Jazeera says began Thursday, November 12, hit users in 74 countries and lasted about 24 hours. One outlet describes it as starting Friday, but Al Jazeera and TechRadar both put the start on Thursday. No bank has linked the two events (Yahoo Finance).
How it happened: what is confirmed and what is still a hypothesis
Confirmed
- Chase calls it a technical bug, not an attack.
- The main problem was access: web login, balances and transfers (San Francisco Chronicle).
- Chase says the money is still there and the problem is slow processing for some transactions, not lost funds.
- U.S. Bank says its customers were affected through Zelle, not through its own systems.
Not confirmed
- The root cause of Chase’s bug: a software release, a database, a vendor or the network.
- Whether Bank of America, Wells Fargo and others had failures of their own or were hit by spillover.
- Any link to the Microsoft outage. There is no evidence of one so far.
Our analysis (unconfirmed): why several banks seem to go down at once
The useful lesson for a business owner is that one large bank’s failure can look like a system-wide collapse even when it isn’t. There are three plausible mechanisms, and U.S. Bank’s statement supports the first:
- Shared networks. Zelle connects many banks. If one large bank processes slowly, payments to and from it stall, and a customer at a different bank sees their payment “not going through.” Their own bank works fine, but the payment depends on both ends.
- Reporting noise. Downdetector counts complaints. When an outage is in the news, especially right after the Microsoft incident, more people open their apps and report glitches that may be minor or unrelated. The numbers for the “secondary” banks deserve some skepticism.
- A common vendor. Banks share cloud, network, authentication and processing providers, and a failure at one of them would hit several banks at once. That’s possible, but nobody has confirmed it here, and we won’t guess at names.
One technical point does follow from Chase’s statement. “Access preserved, transactions slow” usually means the core ledger (the record of who owns what) is intact, and the trouble is in the layers around it: the app, authentication or payment queues. If so, this is a service failure, not a data-integrity failure. We won't know for sure until Chase shares more.
How it could have been prevented (or contained)
Until the root cause is known, nobody can say which specific control failed. What we can say is which practices reduce this kind of incident. They apply to a bank as much as to your online store or ERP.
- Gradual, reversible releases. What it is: shipping changes to a small slice of users first (a canary) and behind feature flags. Why it works: if a change is the culprit, few people are hit and it can be switched off in minutes. Effort: moderate. It takes process discipline more than expensive tooling.
- Graceful degradation. What it is: designing the system so that if transactions fail, balances still show in read-only mode. Why it works: what upset people most on Monday was not even being able to see their balance. Effort: moderate to high, because the architecture has to separate reading data from writing it.
- Circuit breakers and idempotent queues. What it is: when an outside service such as a payment network slows down, the system stops hammering it, queues the operation and retries it with a unique ID. Why it works: one slow component doesn’t drag everything else down, and a user who taps “send” three times doesn’t pay three times. Effort: moderate. It’s sound engineering, not a product you buy.
- Dependency mapping and concentration risk. What it is: knowing which providers each critical function relies on and what happens if each one fails. Why it works: last week’s Microsoft outage, which Al Jazeera reports grew out of an earlier network-capacity upgrade, showed how one provider can stall thousands of companies. Effort: low for the inventory, high if you decide to duplicate providers.
- Clear, early communication. What it is: a status page and messages that say what works, what doesn’t and what to do instead. Why it works: Wells Fargo at least named other channels customers could use. A generic “try again later” leads to more calls, more retries and more openings for scammers. Effort: low.
- Failure drills. What it is: deliberately switching off a component in a controlled environment to see how the system and the team react. Why it works: when the real failure comes, there is already a rehearsed plan. Effort: moderate, and it has to be repeated.
If your operation runs on a single system with no plan B, now is a good time to review its architecture. At Disruptive we build custom software with these failure modes in mind from day one.
What to do today
For businesses
- Don’t resend payments or transfers. If something is stuck as “pending,” wait for confirmation or check your statement first.
- Review payroll, supplier payments and collections scheduled for today and tomorrow that rely on Chase, Zelle or another affected bank, and let anyone waiting on a payment know.
- Keep a fallback: a second bank account or another way to collect payments in an emergency.
- Warn your team about fraud. Fake “support” messages show up during outages. No bank will ask for passwords or one-time codes.
- Document times, transactions and receipts in case you need to dispute something later.
For everyday users
- Use the channels the banks point to: ATMs, branches or phone, as Wells Fargo suggested.
- Don’t send the same Zelle payment more than once; check your history once service returns.
- Contact your bank only through the official numbers on its website or your card.
Frequently asked questions
Was the Chase outage a hack?
According to Chase, no. A spokesperson called it a technical bug, not a cyber issue (CBS News). The other banks have not given a cause.
Is my money safe?
Chase says customers still have access to their accounts and funds and that some transactions are only slower. There are no official reports of lost money.
Why did several banks fail at the same time?
That isn’t confirmed. U.S. Bank said its systems weren’t directly affected but that Zelle payments with other banks could be delayed. That points to a knock-on effect rather than necessarily separate failures.
When will online banking be back?
No bank has given a time. At one point an outage-tracking site listed Chase as working and Bank of America as having partial issues (Yahoo), but that does not confirm a full recovery.
Comments
No comments yet. Be the first to share what you think.


