Close Menu
  • Home
  • News
  • Security
  • Privacy
  • Cybercrime
    • Threat Groups
    • Ransomware
    • Explainers
    • Stealer Logs
  • AI
  • OSINT
  • Tools
    • Ransomtracker
    • Ransomware attacks today
    • Stealercheck
    • FortiBleed Checker
    • Site Check
  • Data
    • Ransomware statistics
    • Ransom payment rate
    • Breach verification
    • Infostealer statistics
  • Newsletter
  • About Us
Facebook X (Twitter) Instagram Threads
Ransomnews
  • Home
  • News
  • Security
  • Privacy
  • Cybercrime
    • Threat Groups
    • Ransomware
    • Explainers
    • Stealer Logs
  • AI
  • OSINT
  • Tools
    • Ransomtracker
    • Ransomware attacks today
    • Stealercheck
    • FortiBleed Checker
    • Site Check
  • Data
    • Ransomware statistics
    • Ransom payment rate
    • Breach verification
    • Infostealer statistics
  • Newsletter
  • About Us
Facebook X (Twitter) LinkedIn
Ransomnews
Security

Chase and Bank of America outage: was it a cyberattack?

Ransomnews Research TeamBy Ransomnews Research TeamNovember 16, 2026Updated:November 17, 2026No Comments13 Mins Read174 Views
Share Facebook Twitter Pinterest LinkedIn Tumblr Email Copy Link
Cover: Banks down. Line drawing of a bank building with one strip displaced.
Share
Facebook Twitter LinkedIn Pinterest Email Copy Link

Final update, 00:05 UTC on 17 November 2026 (7:05 p.m. ET on 16 November): Chase says transactions are posting normally again. Live updates have ended.

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 said on X that the cause was “a software bug in on-premise hardware systems” and that there is no evidence it was cyber-related. At about 6:30 p.m. ET, roughly eight and a half hours after the first reports, a Chase spokesperson told NBC News: “Transactions are now posting normally.”

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.

JPMorganChase has experienced a temporary issue related to a software bug in on-premise hardware systems – there is no evidence this is cyber-related. It is taking longer than usual to service some customers.

Where we were party to a transaction involving other banks, those…

— Chase (@Chase) November 16, 2026

In brief

  • Recovery: a Chase spokesperson told NBC News at about 6:30 p.m. ET that transactions were posting normally again. Chase had not posted that on X by 7:05 p.m., and Plaid still listed its Chase incident as open.
  • Cause: Chase says a software bug in its on-premise hardware systems slowed transactions and that there is no evidence it was cyber-related. A source told NBC News the problem was confined to retail banking.
  • 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, and Capital One told CBS News it was not affected. 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 1,050 by 7 p.m. Bank of America had eased from about 2,100 to 500 and Wells Fargo from about 1,050 to 260. U.S. Bank was at about 240.
  • Your money: Chase says customers kept access to their accounts and funds throughout. 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, how many customers were affected, and whether the technical issues at Wells Fargo were connected.

Was the bank outage a cyberattack?

Nothing published so far points to one. Chase says its problem was a software bug and that there is no evidence it was 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.

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

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.

ServiceReports began (ET)What the bank has said
Chase9:53 a.m.A software bug in its on-premise hardware systems slowed transactions. No evidence it was cyber-related. Transactions were posting normally again from about 6:30 p.m. ET, a spokesperson told NBC News.
Zelle11:33 a.m.Its network is working. The delays started with Chase, a spokesman told NBC News.
Bank of America11:42 a.m.No statement of its own found. AP reports it had no issues with its banking services.
U.S. Bank12:35 p.m.Its systems are not directly affected. Zelle payments involving another bank may be delayed.
Wells Fargo12:46 p.m.Its website says there are technical issues and it is working to fix them, ABC7 reports.
Capital One1:41 p.m.Not affected and operating normally, a spokesperson told CBS News.

We could not find a statement from Bank of America itself by 7:05 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. Chase said transactions were back to normal at about 6:30 p.m. ET.

User reports indicate problems with Chase since 9:53 AM EST.
How is it affecting you? #ChaseDownhttps://t.co/2pKcMUBEbp

— Downdetector (@downdetector) November 16, 2026
How the US bank outage unfolded
Monday 16 November 2026. Times are US Eastern (ET), with UTC alongside.
User reports on Downdetector
Bank statements, reporting and our checks
9 a.m.noon3 p.m.6 p.m.9 p.m.
  1. Monday 16 November: reports spread from bank to bank
  2. 9:53 a.m. ET 14:53 UTC Downdetector
    Reports of problems at Chase begin.
  3. 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.
  4. 11:33 a.m. ET 16:33 UTC Downdetector
    Reports begin for Zelle, the payment network built into the banks’ apps.
  5. 11:42 a.m. ET 16:42 UTC Downdetector
    Bank of America reports begin.
  6. 12:35 p.m. ET 17:35 UTC Downdetector
    U.S. Bank reports begin.
  7. 12:46 p.m. ET 17:46 UTC Downdetector
    Wells Fargo reports begin.
  8. 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.
  9. 1:41 p.m. ET 18:41 UTC Downdetector
    Capital One reports begin.
  10. 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.
  11. 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.
  12. 2:15 p.m. ET 19:15 UTC Downdetector
    Chase reports peak at close to 5,000.
  13. 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.
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. 3:57 p.m. ET 20:57 UTC Chase
    Chase posts its explanation on X: a software bug in its on-premise hardware systems, with no evidence that it is cyber-related. The bank says 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.
  22. 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.
  23. 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.
  24. 4:52 p.m. ET 21:52 UTC Capital One
    Capital One tells CBS News it has not been affected and is operating normally.
  25. 5:02 p.m. ET 22:02 UTC Downdetector
    Chase reports are down to about 2,100, less than half the peak. Bank of America is at about 900, U.S. Bank 650, Wells Fargo 600 and Zelle 230.
  26. 5:34 p.m. ET 22:34 UTC Downdetector
    Chase reports are at about 1,650, a third of the peak. Bank of America is at about 700, U.S. Bank 470, Wells Fargo 400 and Zelle 160.
  27. 5:43 p.m. ET 22:43 UTC NBC
    NBC News reports that regulators contacted the affected banks and, according to a person familiar with the matter, found the problem contained and service already being restored. Several Chase branches in Manhattan appear to be operating normally.
  28. 6:05 p.m. ET 23:05 UTC Downdetector
    Chase reports are at about 1,450, under a third of the peak. Bank of America is at about 650, U.S. Bank 400, Wells Fargo 370 and Zelle 150.
  29. 6:30 p.m. ET 23:30 UTC Chase
    A Chase spokesperson tells NBC News that transactions are posting normally again.
    Why it matters: it is the first word from Chase that the fault is fixed, about eight and a half hours after the first reports.
  30. 6:34 p.m. ET 23:34 UTC Downdetector
    Chase reports are at about 1,150, a quarter of the peak. Bank of America is at about 550, Wells Fargo 350, U.S. Bank 300 and Zelle 140.
  31. 7:04 p.m. ET 00:04 UTC Downdetector
    Reports are still coming in but falling. Chase is at about 1,050, Bank of America 500, Wells Fargo 260, U.S. Bank 240 and Zelle 110.
  32. Status Final
    Chase says transactions are posting normally again. User reports are at about a fifth of the peak and falling. Chase had not posted the recovery on X, and Plaid still listed its Chase incident as open. Last checked at 00:05 UTC on 17 November (7:05 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 00:05 UTC, 17 November 2026.

What should customers do?

  • Check before you resend a payment. Chase said transactions were slow during the outage, so a payment that looked stuck may have gone through. Look at 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?

Chase said at about 6:30 p.m. ET on 16 November 2026 that transactions were posting normally again, NBC News reports. The bank blamed a software bug that slowed transactions online and in some branches from that morning. Customers were still filing reports on Downdetector at 7 p.m. ET, at about a fifth of the peak level.

How long did the Chase outage last?

About eight and a half hours by the public record. Downdetector logged the first reports at 9:53 a.m. ET on 16 November 2026, and a Chase spokesperson said transactions were posting normally at about 6:30 p.m. ET.

Was the bank outage a cyberattack?

There is no evidence of one. Chase says the cause was a software bug in its own hardware systems, with no evidence that it was 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 260 by 7 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?
  • Chase on X: statement on the cause of the outage
  • NBC News: Chase says transactions back to normal after outage 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.

Share. Facebook Twitter Pinterest LinkedIn Tumblr Telegram Email Copy Link
Previous ArticleOld Bitly links hijacked in Burger King, McDonald’s and Trump tweets
Next Article n0n lists Eli Lilly, Visa and JPMorgan: no breach confirmed
Ransomnews Research Team

The Ransomnews Research Team is the collective byline used for collaborative pieces, editorial briefings, and articles drawing on contributions from multiple researchers. Coverage spans ransomware operations, breach economics, threat actor profiling, OSINT methodology, and emerging risks across security, privacy, and AI.

Related Posts

Old Bitly links hijacked in Burger King, McDonald’s and Trump tweets

November 15, 2026

Microsoft 365 outage: was it a cyberattack? What we know

November 12, 2026

CSC Telecom leak: 125 million Baltic SMS, readable in real time

November 11, 2026

Comments are closed.

The Ransomnews Monthly

What leaked, what held up

One email a month: the datasets we verified, and the ones that fell apart under scrutiny.

Double opt-in. We store your email, signup time, and IP for consent records (GDPR Art. 7). See our privacy policy.

Free tool

How does your own site score?

Forty passive checks on TLS, security headers, email spoofing and privacy. A grade out of 100 in about fifteen seconds.

No signup. Nothing installed. We only request what your site already serves publicly.

Free tool

Were you in a leak?

Check whether an email address has surfaced in infostealer logs. No signup, no data stored.

Run StealerCheck

Live data

Ransomtracker

Victims as they are posted to ransomware leak sites, tracked continuously and checked against the claims.

Open the tracker

9,753 confirmed attacks tracked

Facebook X (Twitter) LinkedIn
© 2026 Ransomnews.com

Type above and press Enter to search. Press Esc to cancel.

Cookies on Ransomnews

We use strictly-necessary cookies to run the site and may use first-party analytics to understand which articles are read. Some pages contain affiliate links; when you click one, the affiliate network sets cookies on the merchant's domain to attribute the referral. See the Cookie Policy and Affiliate Disclosure for detail.

RANSOMNEWS.COM

Tracking the criminal infrastructure of the internet.

Independent coverage of ransomware, breach economics, threat actors, privacy, AI security, and the open-source investigation toolkit.

Topics

  • News
  • Security
  • Privacy
  • Cybercrime
  • AI
  • OSINT
  • Threat Groups
  • Stealer Logs
  • Ransomtracker
  • Stealercheck
  • FortiBleed Checker
  • Site Check

Site

  • About Us
  • Editorial Team
  • Contact
  • Tip Line
  • Editorial

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • Funding & Independence
  • RSS Feed
© 2026 Ransomnews.com · Tracking the criminal infrastructure of the internet.