Live, updating: last checked at 21:30 UTC (4:30 p.m. ET) on Monday 16 November 2026. We re-check the banks and the outage reports every 30 minutes and add to the timeline.
Customers of Chase, Bank of America, Wells Fargo and U.S. Bank reported problems with online banking on Monday 16 November 2026. There is no evidence of a cyberattack. Chase says the cause is “a software bug in on-premise hardware systems” and that it is working to fix it by the end of the day, NBC News reports.
The reports did not start together. Downdetector logged Chase first, at 9:53 a.m. ET, and the other banks one to four hours later. Plaid, the service many finance apps use to connect to bank accounts, opened an incident for Chase at 10:11 a.m. ET and has none for the other banks. A fault shared by all of them would more likely show up at the same moment. CNBC, citing a source, reports no sign of one bug affecting several banks, according to Reuters.
Chase says other banks were slowed only in transactions that involved Chase. Zelle and U.S. Bank describe the same thing from their side. Zelle says its own network is working, and a spokesman told NBC News the delays started with Chase. U.S. Bank says its systems “are not directly impacted”, but that Zelle payments to or from another bank may be slow, Hearst Television reports.
Wells Fargo has acknowledged a problem too. Its website says there are technical issues and that it is working to fix them, ABC7 reports. It has not said whether they are connected to Chase. Bank of America and Citigroup were not having issues with their own banking services, AP reports.
BREAKING: Customers are reporting difficulty accessing online accounts at banks including Bank of America, Chase, J.P. Morgan, U.S. Bank and Wells Fargo. https://t.co/iCs2KIE3ZU
— The Associated Press (@AP) November 16, 2026
In brief
- Cause: Chase says a software bug in its on-premise hardware systems is slowing transactions, that it is not cyber-related, and that it is working to fix it by the end of the day.
- Other banks: Chase says they were slowed only in transactions that involved Chase, and Zelle says its delays started there. AP reports that Bank of America and Citigroup had no issues with their own services. Wells Fargo says it has technical issues and gives no detail.
- Who is affected: Downdetector shows report spikes for Chase and J.P. Morgan, Bank of America, Wells Fargo, U.S. Bank, Capital One and the Zelle payment network. CBS News also names Truist.
- Scale: Chase reports peaked at close to 5,000 soon after 2 p.m. ET and were down to about 2,700 by 4:25 p.m. Bank of America has eased from about 2,100 to 1,200 and Wells Fargo from about 1,050 to 700. U.S. Bank is at about 800.
- Your money: Chase says all customers still have access to their accounts and funds. No bank has reported lost money.
- Shared systems: the status pages of Cloudflare, Akamai, Amazon Web Services and Microsoft Azure showed no incident that would explain the reports when we checked at 2:28 p.m., 3:15 p.m. and 3:50 p.m. ET.
- Still unknown: which Chase systems failed, whether the technical issues at Wells Fargo are connected, and whether Chase will meet its end-of-day target.
Was the bank outage a cyberattack?
Nothing published so far points to one. Chase says its problem is a software bug and is not cyber-related. Its spokesperson had earlier told AP it was “a technical bug issue, not a cyber issue”. None of the other banks has reported an attack. Wells Fargo calls its problems technical, and U.S. Bank says its own systems are not directly affected. CNBC’s source saw no sign that bad actors were involved at JPMorgan.
People are asking because this is the third large technology failure in the United States in a week. Microsoft 365 was down for about a day from 12 November, and a nationwide ground stop halted flight departures days later. Microsoft said its outage was not an attack. No one has shown a link between the three.
Which banks are affected?
These are the services with report spikes on Downdetector, in the order the reports began. Downdetector counts reports from users, so a spike tells you customers are having trouble and nothing about the cause.
Free tool
How does your own site score?
Run the same forty passive checks against your own domain: TLS and certificates, security headers, SPF and DMARC, cookies before consent, and what your stack quietly reveals. A grade out of 100 in about fifteen seconds.
No signup. Nothing installed. We only request what your site already serves publicly.
| Service | Reports began (ET) | What the bank has said |
|---|---|---|
| Chase | 9:53 a.m. | A software bug in its on-premise hardware systems is slowing transactions. Not cyber-related. Fix targeted for the end of the day. |
| Zelle | 11:33 a.m. | Its network is working. The delays started with Chase, a spokesman told NBC News. |
| Bank of America | 11:42 a.m. | No statement of its own found. AP reports it had no issues with its banking services. |
| U.S. Bank | 12:35 p.m. | Its systems are not directly affected. Zelle payments involving another bank may be delayed. |
| Wells Fargo | 12:46 p.m. | Its website says there are technical issues and it is working to fix them, ABC7 reports. |
| Capital One | 1:41 p.m. | No public statement found |
“No public statement found” means we could not find one by 4:30 p.m. ET. Chase’s support account acknowledged the problem on X at 12:48 p.m. ET, about an hour before the bank’s statement reached AP.
We saw your post and want to reach out. I do apologize, it appears that we are currently working to resolve an issue with online banking. Please try again at a later time. We're sorry for any inconvenience, and appreciate your patience. ^RR
— Chase Support (@ChaseSupport) November 16, 2026
How did the outage unfold?
Chase was the first bank to show up on Downdetector, which posted its alert on X a little after 10 a.m. ET. The timeline below is updated as the banks respond.
How the US bank outage unfolded
Monday 16 November 2026. Times are US Eastern (ET), with UTC alongside.
- Monday 16 November: reports spread from bank to bank
9:53 a.m. ET 14:53 UTC Downdetector
Reports of problems at Chase begin.
10:11 a.m. ET 15:11 UTC Plaid
Plaid, which connects bank accounts to finance apps, opens an incident for Chase connections. It says Chase is experiencing downtime and that it will post an update when Chase has fixed the issue.
11:33 a.m. ET 16:33 UTC Downdetector
Reports begin for Zelle, the payment network built into the banks’ apps.
11:42 a.m. ET 16:42 UTC Downdetector
Bank of America reports begin.
12:35 p.m. ET 17:35 UTC Downdetector
U.S. Bank reports begin.
12:46 p.m. ET 17:46 UTC Downdetector
Wells Fargo reports begin.
12:48 p.m. ET 17:48 UTC Chase
Chase’s support account on X tells a customer the bank is working to resolve an issue with online banking.
1:41 p.m. ET 18:41 UTC Downdetector
Capital One reports begin.
1:43 p.m. ET 18:43 UTC Chase
AP reports Chase’s explanation: a technical issue, not a cyber issue. Chase says some transactions are taking longer than usual and customers still have access to their accounts and funds.
Why it matters: Chase was the first bank to give a cause, and it rules out an attack.
1:50 p.m. ET 18:50 UTC Downdetector
Chase passes 4,600 reports. Bank of America is above 1,900, U.S. Bank above 900 and Wells Fargo at 800, NBC reports.
2:15 p.m. ET 19:15 UTC Downdetector
Chase reports peak at close to 5,000.
2:18 p.m. ET 19:18 UTC CNBC
CNBC, citing a source, reports no sign that bad actors are involved in JPMorgan’s issue and no sign of one bug hitting several banks, according to Reuters.
2:28 p.m. ET 19:28 UTC Our check
The status pages of Cloudflare, Akamai, Amazon Web Services and Microsoft Azure show no incident that would explain the reports.
2:31 p.m. ET 19:31 UTC Zelle, U.S. Bank
Hearst Television reports statements from Zelle and U.S. Bank. Zelle says its network is working and an issue at financial institutions may be delaying payments. U.S. Bank says its own systems are not directly affected.
Why it matters: it is the first explanation of why several banks show problems on the same day.
2:58 p.m. ET 19:58 UTC Wells Fargo
ABC7 reports that Wells Fargo’s website says the bank has technical issues and is working to resolve them. Wells Fargo had earlier told NBC Chicago it was investigating.
3:10 p.m. ET 20:10 UTC Zelle
A Zelle spokesman tells NBC News the delays on its network started with Chase.
Why it matters: Zelle is built into the other banks’ apps, so a fault at Chase can slow payments for their customers too.
3:12 p.m. ET 20:12 UTC Downdetector
Chase reports have eased to about 3,700. Bank of America is steady near 2,000 and Wells Fargo near 1,000.
3:48 p.m. ET 20:48 UTC NBC
NBC News reports that the problems at Chase are affecting some branch transactions as well as online banking.
3:49 p.m. ET 20:49 UTC Downdetector
Reports are falling. Chase is at about 3,200, Bank of America 1,650, Wells Fargo 800 and Zelle 340. U.S. Bank is steady near 1,000.
4:10 p.m. ET 21:10 UTC AP
AP reports that the problems centre on Chase customers and on customers of other banks trying to transact with Chase. Bank of America and Citigroup were not having issues with their own services.
4:17 p.m. ET 21:17 UTC Chase
Chase names the cause, NBC News reports: a software bug in its on-premise hardware systems. The bank says the issue is not cyber-related, that other banks were slowed only in transactions involving Chase, and that it is working to fix it by the end of the day.
Why it matters: it is Chase’s first account of what failed, and the first target for a fix.
4:26 p.m. ET 21:26 UTC Downdetector
Reports keep falling. Chase is at about 2,700, Bank of America 1,200, U.S. Bank 800, Wells Fargo 700 and Zelle 300.
Status Now
Chase says it is working to fix a software bug by the end of the day. Reports are falling at every bank we track but are still far above a normal day, and Plaid’s incident for Chase is still open. Wells Fargo says it is working on technical issues. Checked at 21:30 UTC (4:30 p.m. ET) on 16 November.
Start times are from Downdetector’s posts on X. Report counts are Downdetector figures, read by us or as published by the outlets linked in this article. Last checked 21:30 UTC, 16 November 2026.
What should customers do?
- Do not send a payment twice. Chase says transactions are slow, so a payment that looks stuck may still go through. Check your balance before you repeat it.
- Try another route if it is urgent. Wells Fargo pointed its customers to ATMs, branches and phone banking, NBC Chicago reports.
- Ignore messages about your account. Outages are a common cover for fake texts, emails and calls. Open the bank’s app yourself or call the number on your card.
Frequently asked questions
Is Chase down right now?
At 4:30 p.m. ET on 16 November 2026, customers were still reporting problems, mostly with balances, transactions and web login, at a little over half the level of the 2 p.m. peak. Chase says a software bug is slowing transactions, that customers can still reach their accounts and funds, and that it is working to fix it by the end of the day. NBC News reports that some branch transactions are affected too.
Was the bank outage a cyberattack?
There is no evidence of one. Chase says the cause is a software bug in its own hardware systems and is not cyber-related, and no other bank has reported an attack.
Is Zelle down?
Zelle says its own network is working and that the delays started with Chase. Payments to or from an affected bank may be slow. Downdetector logged a rise in Zelle reports from 11:33 a.m. ET on 16 November 2026, mostly about transfers.
Is Bank of America down?
Bank of America was not having issues with its own banking services on 16 November 2026, AP reports. Its customers still filed about 2,000 problem reports on Downdetector at the peak. Chase says other banks were slowed only in transactions that involved Chase.
Is Wells Fargo down?
Wells Fargo’s website said on 16 November 2026 that the bank had technical issues and was working to resolve them, ABC7 reports. Downdetector logged a rise in customer reports from 12:46 p.m. ET. They peaked at about 1,050 and were down to about 700 by 4:25 p.m.
Are the bank outages linked to the Microsoft outage?
No link has been shown. Microsoft said its outage of 12 to 13 November 2026 was caused by a network capacity upgrade and was not an attack.
Sources and further reading
- AP: Customers at some of the nation’s largest banks are reporting difficulty accessing accounts online
- Reuters, via The Korea Times: Downdetector reports outages at major US banks
- NBC: Are Chase, Bank of America and Wells Fargo down?
- NBC News: Nationwide outage impacts Chase banking online and at some branches
- WBAL and Hearst Television: statements from Zelle and U.S. Bank
- ABC7: Bank outages today, live updates
- CBS News: Major U.S. banks report widespread service outages
- Plaid status: Service disruption impacting Chase connections
- Downdetector: Chase and Downdetector on X
- Status pages: Cloudflare, Akamai, Amazon Web Services, Microsoft Azure
- Ransomnews: Microsoft 365 outage, was it a cyberattack?
The Ransomnews Monthly
One email a month. Original leak-site data, victim census updates, and the findings that did not make the articles. No spam, unsubscribe any time.
Double opt-in. We store your email, signup time, and IP for consent records (GDPR Art. 7). See our privacy policy.