Chase Says Bug, Not Cyberattack, Behind 4,700-Report Outage

Update, 17 November 2026, 14:17 UTC: Homeland Security Secretary Markwayne Mullin says he is 98% certain officials are not seeing a cyberattack. “I can tell you with 98% certainty we’re not seeing the cyberattack,” he said on Fox News’s Hannity on 16 November, Fox News reported. “We’re not seeing the footprints going in. We’re not seeing the footprints going out.” Fox said he described the disruptions as “individually unrelated”. He also said: “We used to have backup systems and the backup systems are overwhelmed by the new systems now.”

On 17 November, a headline attributed to CNBC and relayed on X quoted him as saying the issues at Microsoft, Chase and United had to do with new technology being pushed on top of old computer systems; we have not seen the full interview. Chase’s own explanation, above, remains a software bug in on-premise hardware systems, and United said there was no indication of a cybersecurity issue. Our earlier outage piece covers his 15 November remarks on the FAA and Microsoft.

Resolved, 17 November 2026, 04:16 UTC: Chase says transactions are posting normally again; by our arithmetic the disruption ran about 8 hours 37 minutes from the first reports. “Transactions are now posting normally”, a Chase spokesperson said around 6:30 p.m. on Monday, NBC News reported. In a post on X at 20:57 UTC, JPMorganChase said it “has experienced a temporary issue related to a software bug in on-premise hardware systems – there is no evidence this is cyber-related”, that “this is not a systemic issue” and that “Customers still have access to their accounts and funds”. By Monday night the bank reported transactions were processing normally again, 6abc Philadelphia reported. Downdetector noted the first Chase reports at 9:53 a.m. ET (14:53 UTC); taking the 6:30 p.m. all-clear as Eastern time (23:30 UTC), that is about 8 hours 37 minutes, by our arithmetic. NBC News reported it was not immediately clear how many Chase accounts were affected; the bank counts about 94 million customer relationships in the United States.

Chase’s services are experiencing a technical bug issue, not a cyber issue, a spokesperson said on Monday, the Associated Press reported, as Downdetector recorded more than 4,700 Chase reports by 2 p.m. ET, FOX 29 reported, citing the AP. Zelle and U.S. Bank spokespeople told Hearst Television their own systems were not the source.

By our arithmetic, Chase made up about 54% of at least 8,700 reports across the four banks FOX 29 listed. No bank has said what the bug was or when service will be fully restored.

Business Pill · Concentration Explained

An evergreen Business Engineer explainer on concentration, when a few big pieces make the total. It teaches the general idea only and does not discuss the banks or these reports.

The key insight: As we read the statements, they narrow where the fault sits without naming it: Chase calls it a technical bug, not a cyber issue, while Zelle points to issues at financial institutions and U.S. Bank says its own systems are not directly impacted.

What Did Chase Say About the Cause?

The AP reported that a Chase spokesperson said the bank’s services are experiencing “a technical bug issue, not a cyber issue”. The spokesperson’s statement read: “Due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds”.

Chase’s support account first acknowledged the problem to a customer on X at 17:48 UTC, writing that “we are currently working to resolve an issue with online banking”. That was 2 hours 55 minutes after the first reports Downdetector noted at 9:53 a.m. ET, by our arithmetic. Some Chase customers received a message that said “Some services aren’t available”, the AP reported.

Chase drew more than 4,700 of at least 8,700 Downdetector reports across four banks by 2 p.m. ET on 16 Novembe
Chase drew more than 4,700 of at least 8,700 Downdetector reports across four banks by 2 p.m. ET on 16 November, about 54% by our arithmetic. Data: Downdetector user reports as reported by FOX 29, citing the AP; they count reports, not affected customers.

What Did Zelle and U.S. Bank Say?

A Zelle spokesperson said the issues were because of financial institutions, not the payment network itself, according to the AP story. “An issue at the financial institutions may be delaying Zelle payments for some of their customers”, the spokesperson told Hearst Television by email.

A U.S. Bank spokesperson told Hearst Television that “U.S. Bank systems are not directly impacted” but that “clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays”. Bank of America and Wells Fargo had not commented in the reports we read.

How Big Were the Reports?

FOX 29 reported that by 2 p.m. ET, Downdetector recorded more than 4,700 reports for Chase, 2,000 for Bank of America and over 1,000 each for U.S. Bank and Wells Fargo. That is at least 8,700 across the four, with Chase about 54%, by our arithmetic.

Gizmodo reported over 4,300 Chase reports as of 1:27 p.m. ET, up from over 3,800 just 15 minutes earlier, about 13% in a quarter hour by our arithmetic. The San Francisco Chronicle reported smaller spikes at Capital One and Zelle. Downdetector counts are user reports, not affected customers.

Timeline of statements on 16 Nov 2026: first Chase reports 14:53 UTC, Chase support on X 17:48, JPMorgan to Yahoo Finance 18:49, 4,700+ Chase reports by 19:00, cyberattack question on X 19:04, Chase says bug not cyber and Zelle and U.S. Bank point elsewhere by 19:31 (AP)
Who said what as the Chase outage spread on 16 November, in UTC. Sources: Downdetector and @ChaseSupport on X, Yahoo Finance, FOX 29 and Hearst Television citing the AP, and Andrew Curran on X; time conversions are our arithmetic.

Was It a Cyberattack?

Chase says no. Posts on X had raised the question: Andrew Curran wrote at 19:04 UTC that the situation was “not yet confirmed as a cyberattack”. Chase’s spokesperson called it a technical bug, not a cyber issue, the AP reported in a story updated at 2:31 p.m. ET; the AP did not give the time of that comment. In the reports we read, no regulator or government cyber agency had commented.

Chase said customers “still have access to their accounts and funds”. It has not said which transactions were delayed or how many customers were affected.

How Does This Fit the Week’s Outages?

It is the third major outage in days, after Microsoft’s 12 and 13 November outage and the FAA ground stop. Microsoft traced its outage to a latent defect, as our explainer in seven numbers sets out. Nothing in the sources we read links the bank reports to either event or to a shared provider. Our first report on the bank outages has the timeline and the share moves.

The Structural Read

As we read the counts, Chase carried most of the load: more than 4,700 of at least 8,700 reports across four banks by 2 p.m. ET, about 54% by our arithmetic.

As we read U.S. Bank’s comment, a fault at one bank can show up as Zelle delays for customers of another, which is how a single bank’s problem can look like a sector outage on Downdetector.

A Zelle spokesperson, by email to Hearst Television, 16 November 2026

“Consumers use Zelle through participating banks and credit unions, which manage their accounts and hold their funds”

Three Implications

FOR CHASE CUSTOMERS Chase said some transactions are taking longer than usual to complete, while customers still have access to their accounts and funds.

FOR OTHER BANKS’ CUSTOMERS U.S. Bank said clients sending or receiving Zelle payments with another financial institution may experience transaction delays.

ON THE CYBER QUESTION Chase’s spokesperson said it is not a cyber issue, the AP reported; in the reports we read, no regulator or government cyber agency had commented.

The Business Engineer Lens

This story maps onto the Business Engineer framework AI Agents & The New Payment Infrastructure.

The framework argues that in any infrastructure transition, “the entities that own the connective tissue underneath capture the economics regardless of which consumer-facing interface wins.”

As we read it, Zelle’s own description shows the reverse side of that connective tissue: Zelle runs through participating banks, so an issue at one of them can delay payments for customers elsewhere, as U.S. Bank said. The framework predates the outage and does not discuss it.

Related coverage (the Microsoft outage is context only; no link to the bank outage has been reported)

What Is Not Established

We do not know what the bug was, which Chase system it hit, how many customers were affected, or whether Bank of America and Wells Fargo had faults of their own. Zelle and U.S. Bank attribute their customers’ delays to issues at other financial institutions without naming them.

We did not contact the banks or Zelle for this piece. The report counts come from Downdetector as relayed by FOX 29, Gizmodo and the San Francisco Chronicle.

This Week In The AI Supercycle

AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source

This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.

Read the full issue →

Business Engineer Framework

AI Agents & The New Payment Infrastructure

The Business Engineer premium analysis of who owns the payment layer underneath every consumer-facing interface.

Read the Map of AI →

The Bottom Line

Chase says a technical bug, not a cyber issue, is slowing some transactions, and that customers still have access to their accounts and funds. Zelle and U.S. Bank say their own systems were not the source. With more than 4,700 Chase reports by 2 p.m. ET, Chase was about 54% of at least 8,700 across four banks, by our arithmetic.

95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. This follow-up rests on statements relayed by news outlets. The Chase spokesperson’s cause statement and the Zelle and U.S. Bank comments come from the Associated Press story as carried by Hearst Television; the 2 p.m. ET Downdetector counts come from FOX 29, citing the AP; Chase’s support reply is its own post on X. Gizmodo and the San Francisco Chronicle supplied earlier counts.

Downdetector counts are user reports, not affected customers, and several are lower bounds. The 8,700 total, the 54% share, the elapsed time and the 13% rise are our own arithmetic. We did not contact the banks or Zelle for this piece.

Sources: Associated Press via Hearst Television: Chase spokesperson, Zelle and U.S. Bank statements (updated 2:31 p.m. EST, 16 Nov 2026) · FOX 29, citing the AP: Downdetector counts by 2 p.m. ET (16 Nov 2026) · @ChaseSupport on X, 17:48 UTC, 16 Nov 2026 · Yahoo Finance live blog: JPMorgan statement (18:49 UTC, 16 Nov 2026) · Gizmodo: Chase, Bank of America and Wells Fargo app outages (2:16 p.m. ET, 16 Nov 2026) · San Francisco Chronicle: Chase customers report widespread online banking problems (16 Nov 2026) · Fox News: Mullin on Hannity, 16 Nov 2026

Scroll to Top
FourWeekMBA