
Photo: Harrison Keely, 2025, via Wikimedia Commons (CC BY 4.0)
If your banking app showed a blank balance, refused to log you in or left a Zelle payment hanging on Monday, November 16, 2026, you were not imagining it, and it may not have been your bank’s fault. JPMorgan Chase, the largest bank in the United States, says a "software bug in on-premise hardware systems" slowed its own transactions for most of the day, and that the slowdown spilled over to other banks whenever Chase sat on the other side of a payment.
The short answer: Chase says the problem was a temporary software bug in its own data-center hardware, not a cyberattack. Customers kept access to their accounts and funds, but some transfers, deposits and branch transactions stalled. Bank of America, Wells Fargo, U.S. Bank and Zelle users reported trouble too, mostly because their payments touched Chase. By about 6:30 p.m. Eastern, Chase said transactions were "now posting normally."
It was the third major technology failure in the United States in five days, after a nearly 24-hour Microsoft 365 outage and a nationwide air-traffic ground stop. Here is what happened, hour by hour, why one bank’s bug looked like a nationwide banking collapse, and what to check in your own accounts now.
What happened, hour by hour
All times below are Eastern, the time zone most of the reporting used.
Morning: Trouble started early. A person familiar with the matter told NBC News the outage began Monday morning, and Wired’s read of the outage-tracking site Downdetector put the first wave of reports across banks, credit unions, fintech apps and card companies at around 9:30 a.m. CNBC said users were reporting errors by 11:30 a.m.
Midday: Reports piled up. Downdetector logged almost 5,000 reports about Chase alone, according to the BBC, while other reports named Bank of America, Wells Fargo, U.S. Bank, Capital One, TD Bank and Navy Federal Credit Union. Wired put the peak at around 2 p.m. Some Chase customers saw an app message that read, "Some services aren’t available. We’re working on them. Please try back later."
In branches: The problem was not only online. NBC News reported that both online and in-person branch transactions were affected, and a Chase customer told CBS News, the BBC’s U.S. partner, that he could not deposit a check at a Dallas branch, where a teller said the "system was down."
About 4 p.m.: Chase posted its explanation on X, quoted in full below. The post drew more than 1.5 million views within a few hours.
Early evening: Reports fell off. By 6 p.m., Downdetector reports for Chase, Bank of America and U.S. Bank were dropping, the BBC said. Around 6:30 p.m., a Chase spokesperson told NBC News, "Transactions are now posting normally."
What Chase actually said
Chase’s full statement, given to several outlets and posted on X, reads:
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 banks may have been impacted, but this is not a systemic issue. Customers still have access to their accounts and funds.
The bank told CNBC it was "working diligently to resolve this by the end of the day today," and CNBC’s Eamon Javers reported there was no indication that bad actors were involved. A person familiar with the matter told NBC News that "this is really retail banking," meaning the problem sat with Chase’s consumer bank rather than the rest of JPMorgan Chase, and that regulators were in touch with the affected banks right away and "quickly determined this was contained."

Photo: ajay_suresh, 2026, via Wikimedia Commons (CC BY 4.0)
The scale explains why a single bug was felt so widely. Chase counts about 94 million customer relationships in the United States, with roughly 5,000 branches and 15,000 ATMs, according to NBC News. Wired notes that the bank holds more than 10 percent of all U.S. deposits. It is also one of the biggest technology spenders in banking: at its company update in February 2026, JPMorgan said it planned to spend $19.8 billion on technology this year, up about 10 percent from 2025.
Why other banks seemed to go down too
Every transfer has two ends. When you send money from a Wells Fargo account to someone at Chase, or a Chase customer pays you through Zelle, both banks have to process their half. If Chase’s side is slow, the whole transfer waits, and the customer at the other bank sees an error or a delay even though their own bank is working.
That is what the other companies described. "Zelle is not down. Zelle is operating as it should," a Zelle spokesperson told Wired, adding that "consumers do not have a separate Zelle account, and Zelle does not hold consumer funds." Zelle is a messaging layer between banks; the money stays in bank accounts. U.S. Bank spokesperson Jeffrey Shelman said its systems "are not directly impacted," but that "clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays."
The card networks said they were fine. "Our network is operating normally," said Mastercard’s Seth Eisen, and a Visa spokesperson told Wired that Visa’s systems were operating normally too. PNC, Truist and Capital One all said they had not been directly affected. Wells Fargo posted on its website that it had "technical issues" and did not comment further; Citi declined to comment.
Downdetector itself also made the outage look bigger than it was. The site counts user reports, not confirmed failures, and people tend to blame the app in front of them. Mastercard’s Eisen told Wired the Downdetector reports were "not correct" in his company’s case.

Photo: MostlyDross, 2023, via Wikimedia Commons (CC BY 2.0)
What "on-premise hardware systems" means
"On-premise" (usually written on-premises by engineers) means computers a company owns and runs in its own data centers, as opposed to rented capacity in a public cloud from Amazon, Microsoft or Google. Big banks run both. Core systems that post deposits, move money and keep the ledger often still live on the bank’s own hardware, for reasons of control, security and regulation.
Chase has not said which system failed, what the bug was, or whether it came from a recent change. The wording points to software running on its own machines rather than a cloud provider or a third-party vendor, but it rules out little else. As the Microsoft incident showed last week, a defect can sit unnoticed for months until traffic or load changes in just the wrong way.

Photo: Derrick Coetzee, 2011, via Wikimedia Commons (CC0)
A week of outages, and why they are probably not connected
Monday’s bank trouble landed at the end of a bad stretch for American technology, and plenty of people online assumed a single cause. There is no evidence for that. NBC News reported that "there is no evidence that these incidents are connected to one another," and each company has given its own, unrelated explanation.
Microsoft 365, Thursday to Friday
From 11:20 a.m. Eastern on Thursday, November 12, until 11:10 a.m. on Friday, November 13, most Microsoft 365 users could not reach their Outlook mailboxes. In a preliminary post-incident report, Microsoft blamed three things at once: a bug introduced in a July update for the networking gateway servers that sit in front of Exchange Online, a routine Teams failover about 15 hours earlier that added load to those gateways, and nearly 14 percent of gateway capacity already out of service for an unrelated reason. As overloaded servers dropped out, traffic was redirected to the rest, which then failed too. "At its lowest, more than 80% of servers were unresponsive," Microsoft wrote, as quoted by BleepingComputer. The company said its load tests had missed the bug because they used weaker hardware with fewer cores than production servers.
The FAA ground stop, Friday
At about 3:30 p.m. Eastern on Friday, November 13, the Federal Aviation Administration halted departures nationwide after its legacy telecommunications network became unstable. According to the agency’s own Q&A, data began flooding its network "at a rate of 1,000 connection attempts every 4 to 5 seconds," disrupting aircraft communications and radar feeds at 17 of its 22 en-route control centers. Investigators traced the flood to two remote sites, including a radio site in El Dorado, Arkansas, where the network contractor L3Harris had been installing a new router. Flights resumed at 8:15 p.m., and the FAA says operators canceled about 12,462 flights that day, not all of them because of the ground stop.
United Airlines, Monday
On the same day as the bank trouble, United Airlines reported what it called a "widespread system outage" affecting departing flights. The BBC reported that it was resolved within a few hours, that United said it was not related to cybersecurity, and that no other airline appeared to be affected.
A bug can sit quietly in production for months. What changes is the load around it.
The common thread is not an attacker. It is how tightly modern systems are coupled. The 2024 CrowdStrike incident is the starkest example: a single faulty security update knocked out an estimated 8.5 million Windows devices, which Microsoft said was less than one percent of all Windows machines; the damage was so broad, Microsoft wrote, because so many enterprises running critical services relied on that one product. Banks have their own cautionary tale. In April 2018, the British bank TSB moved its customers onto a new IT platform; the platform failed immediately, much of TSB’s 5.2 million-customer base was affected, and full normal service did not return until December 2018. UK regulators later fined TSB £48.65 million, and the bank paid £32.7 million in redress.
What we know, and what’s still unclear
What we know: The problem started inside Chase’s own systems, according to the bank. Chase says it was not a cyberattack, that customers did not lose access to their money, and that transactions were posting normally by early Monday evening. Zelle, Visa and Mastercard say their networks were working throughout, and several other banks say they were only affected where Chase was on the other side of a payment.
What’s still unclear: Chase has not said how many customers were affected, exactly which system failed, what triggered the bug, or whether any transactions were duplicated or lost. It also has not said publicly whether it will reverse overdraft, late or returned-payment fees caused by the delays. A fuller explanation, like the preliminary post-incident report Microsoft published two days after its outage ended, would answer most of these questions.
What to do if your money was caught in it
Check before you retry
If a transfer or Zelle payment failed or hung on Monday, look at your pending and posted transactions before you send it again. Delayed payments can still go through, and resending can mean paying twice.
Watch for fees and missed payments
If a delay caused an overdraft, a returned payment or a late fee, call your bank and ask for it to be reversed, and keep a note of the date and the error message you saw. Do the same with any company that charged you a late fee because a payment arrived late.
Be wary of outage-themed messages
Big outages are a gift to scammers. If a text, email or call about "the outage" asks you to log in through a link or to share a code, ignore it and contact your bank using the number on the back of your card or in its official app.
Keep a backup way to pay
A card from a second bank and a little cash cover the hours when one bank’s app or Zelle is not working. Monday showed that card networks can keep running even when a bank’s own transfers stall.
The bottom line
Monday’s outage was a Chase problem with a national footprint. A software bug in the bank’s own data-center hardware slowed its transactions for much of the day, and because Chase is on one end of a huge share of American payments, customers at other banks and on Zelle felt it too. The bank says no money was lost and no attacker was involved, and service was back to normal by early evening. The bigger lesson, after Microsoft’s and the FAA’s failures last week, is that even well-funded systems can fail all at once. It is worth checking your recent transactions, asking for any fees to be refunded and keeping a second way to pay.
Further reading

Release It!: Design and Deploy Production-Ready Software
Michael Nygard’s field guide to why production systems fail in cascades, and the circuit breakers and bulkheads that stop one fault from taking everything down.

The DevOps Handbook, 2nd Edition
How companies ship software changes safely and often, including the staged rollouts and monitoring that catch a bad update before it spreads.

SentrySafe Fireproof and Waterproof Lock Box (FHW40100)
A fire- and water-resistant file box for an emergency cash reserve, checkbooks and account paperwork you may need when apps are down.

Timberland Men’s Genuine Leather RFID Blocking Trifold Wallet
Room for a backup card from a second bank and some cash, the simplest insurance against one bank’s outage.

INIU 10000mAh 45W Portable Charger
A small, flight-safe power bank that keeps your phone and banking app alive through a long day of retries and hold music.
