A Chase Bug Locked Thousands Out. X Isn't Buying the Excuse
By Hamza Rouane, the AI Whisperer · 2026-11-17 · 1 reads
On November 16, 2026, a software bug at JPMorgan Chase stalled logins, ATMs and Zelle payments for thousands of Americans. Chase says it was not a cyberattack. Here is the timeline, the viral replies, and the scam wave experts say comes next.
On Monday, November 16, 2026, a software bug inside JPMorgan Chase, the biggest bank in America, left thousands of people unable to log in, move money or finish a Zelle payment, and the trouble spread to customers at Bank of America, Wells Fargo and U.S. Bank. Chase says it was "not cyber-related." Its explanation on X has been viewed 2.3 million times, and a lot of the people replying do not believe it.
What happened: a timeline of the Chase outage
The trouble began Monday morning, according to a source who spoke to NBC News. Tom's Guide saw reports on Downdetector start trickling in around 10 a.m. Eastern, then spike about two hours later.
By 2 p.m. ET, more than 4,700 people had reported problems with Chase, CNN reported. CBS News counted nearly 4,800, the most of any bank. Bank of America passed 2,000 reports, and Wells Fargo and U.S. Bank each passed 1,000, IBTimes found. Those are user reports, not confirmed accounts.
Some Chase customers got a blunt message: "Some services aren't available. We're working on them. Please try back later," France 24 and the AP reported.
It was not only the app. In Colorado, a customer told Denver7 that two drive-up Chase ATMs showed "Unable to process your transaction at this time." In Atlanta, a customer told Atlanta News First the card reader "didn't work," so he had to fill out a paper slip. One traveler spent about 45 minutes in a Midtown branch to get $3,000 in cash before a flight.
Around 4 p.m. ET, Chase posted its explanation on X. Around 6:30 p.m., a spokesperson told NBC News: "Transactions are now posting normally." Tom's Guide described the whole thing as a "nearly eight hour outage."
The post 2.3 million people read
This is the statement Chase pinned to its own X account. It blames "a software bug in on-premise hardware systems" and says "there is no evidence this is cyber-related."
See it on X
When we opened the post, it showed 2.3 million views, about 6,700 likes and 821 replies. The bank promised it was "working diligently to resolve this by the end of the day today."
The top replies tell you the mood. "So did all the banks decide to have a software bug on the same day?" asked one user, @nfino_, in a reply with 117,000 views. Another account, @ebtqueens, wrote: "We sure are having a lot of 'not cyber attacks' on our critical infrastructure in America lately," a reply seen 44,000 times.
The trend even reached X's own news panel, where an AI-written summary of the posts sits under the warning "Grok can make mistakes, verify its outputs."
What Chase and the other banks actually said
Chase spokesman Joe Evangelisti gave the AP the line every outlet repeated: "JPMorgan Chase has experienced a temporary issue related to a software bug in an on-premise hardware system — it is not cyber-related." He added: "This is not a systemic issue — other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us."
A source told CNN the outage was not a cloud problem or an attack: "an update on the company's own physical computer systems inadvertently caused issues." Fox News reported the incident was traced to a software release Chase rolled out earlier Monday that hit a subset of its systems.
The other names on Downdetector pushed back. "Bank of America systems have been operating normally today," that bank said. U.S. Bank said its systems were not directly hit, but "clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays."
Zelle was the most direct. "Zelle is not down. Zelle is operating as it should," Eric Blankenbaker of Early Warning, the company that runs Zelle, told Denver7. "An issue at the financial institutions may be delaying Zelle payments for some of their customers."
So the honest picture is this: one bank broke, and because Chase sits in the middle of so many transfers, people at other banks felt it too. NBC News notes Chase has about 94 million customer relationships in the US, 5,000 branches and 15,000 ATMs. That is why one bad update looked like the whole system going dark.
Wall Street noticed. Shares of JPMorgan Chase, Bank of America, Citigroup and Wells Fargo fell around 2% on Monday, Yahoo Finance reported.
Why people doubt it: three outages in five days
The suspicion did not come from nowhere. Monday was "the third straight weekday with a massive technical failure," CNN wrote.
On Thursday, a Microsoft 365 outage knocked out Outlook, Teams and Copilot. Microsoft blamed a previously undetected software defect, more traffic and reduced server capacity, according to Fox News, and said there was "no indication" of a cyberattack or "action by artificial intelligence agents," the AP reported. On Friday, the FAA stopped departures nationwide for hours after a router problem flooded its systems. On Monday afternoon, United Airlines had its own systemwide computer problem.
Officials say none of these are connected. "There is no evidence that these incidents are connected to one another," NBC News wrote. Experts point to something more boring and more worrying. "They all point to a common theme: the complexity and fragility of the systems that we depend on every day," Notre Dame professor Mike Chapple told CBS News.
Security expert Bruce Schneier was harsher with Tom's Guide: "Our systems are very fragile these days. Fragile systems are the most profitable in the near term."
A rumor added fuel. Viral posts claimed a 2023 episode of The Simpsons had predicted a "Great Blackout" on November 17, the day after the outage. IBTimes points out that the episode never names 2026, and a USA TODAY Network fact-check found no such prediction.
The AI angle: the scam comes after the outage
Here is the part that should worry you more than the bug. Security experts agree that the dangerous moment is right now, after service comes back, while people are still nervous about their money.
"The biggest cybersecurity risk for the public right now may actually come after the outage," security officer Sean Connery told Newsweek. "Criminals watch these. They can send you a text message saying your account was affected, click here to verify your account. Do not click that link."
That is where AI makes things worse. A scammer no longer needs to write a clumsy fake message. A chatbot can write a clean, calm text in a bank's tone in seconds, in any language, thousands of times over, each one slightly different. Voice cloning tools can make a call that sounds like a real support agent. And AI image tools can produce a fake app error screen or fake bank alert that looks exactly like the real thing.
The tell is never how real it looks. The tell is what it asks for. The Colorado Bankers Association told Denver7 that banks will not call, text or email you asking for a password, PIN or one-time security code. If a message does, it is a scam, however perfect it looks.
Notice how even the replies under Chase's own post blur the line. One reply claiming "I had 12 million in my checking account and now it's only showing $1,200" was viewed 27,000 times. On a day like Monday, a joke, a panic post and a scam all look the same in your feed.
What this means for you
- Do not send a stuck payment twice. "If a payment or deposit is delayed, don't send it again. That can create duplicate transactions once things catch up," Jenifer Waller of the Colorado Bankers Association told Denver7.
- Check your account yourself. Open the official app, type the website yourself, or call the number on the back of your card. Never use a link from a text.
- Screenshot errors. If the outage caused a late fee or overdraft, screenshots and timestamps help you ask for a refund, as USA TODAY's guide advises.
Questions people ask
Was the Chase outage a cyberattack?
Chase says no. The bank blamed "a software bug in on-premise hardware systems" and said there is "no evidence this is cyber-related." Fox News reported the problem was traced to a software release Chase rolled out earlier that Monday.
Was Zelle down on November 16?
Zelle says its network kept working. Payments stalled because Chase, one of the banks people use Zelle through, was having problems, so transfers to or from Chase customers were delayed.
Is my money safe after the Chase outage?
Chase said customers kept access to their accounts and funds, and by Monday evening transactions were "posting normally." The bigger risk now is scam texts and calls about the outage, so check your balance only through the official app, website or phone number.