People using ATMs on a city street.
Illustrative photo: Pexels / Jan van der Wolf.

It was two in the afternoon, Eastern time, and the counter would not stop climbing: nearly 4,800 people reporting problems with Chase at the same time. It was not one bank or one phone. It was the whole banking system, wobbling on a Monday afternoon.

A software bug at JPMorgan Chase, the largest bank in the United States, slowed payment and transfer processing on Monday, November 16, at several of the country’s biggest banks — and left thousands of customers fighting with the app, the ATM, and Zelle — for hours. By about 6:30 p.m. Eastern, the bank confirmed transactions were posting normally again. It is over. But the question that lingers is the one that matters: what exactly broke, and why did a failure at a single bank drag so many others down with it?

What happened, hour by hour

The morning started off wrong and nobody noticed in time. The first reports of Zelle problems showed up around 9:30 a.m. Eastern. Then the trickle turned into a flood: customers at Chase, Bank of America, Wells Fargo, U.S. Bank, and Truist began reporting they could not get into their accounts, check their balances, or complete transfers.

The peak came near 2 p.m. Downdetector, the site that tracks user complaints in real time, logged around 4,800 reports for Chase alone at that hour, with complaints about Bank of America, Wells Fargo, and Zelle spiking too. Anyone who tried to open the Chase app ran into a blunt notice: “Some services aren’t available. We’re working on them. Please try back later.”

Chase acknowledged it that same afternoon. In a post on X and in emails to news outlets, the bank described “a temporary issue related to a software bug in an on-premise hardware system.” In plain language: it was not an attack, not a hacker, it was its own failure. Spokesman Joe Evangelisti put it bluntly: it is “not cyber-related.”

No, it was not a cyberattack — but the scare was real

Watch out for this one, because the moment a big bank goes down, the first suspicion is always the same. And this time the official answer came fast and through several channels at once.

Chase insisted there was no evidence of malicious activity. Homeland Security Secretary Markwayne Mullin said on Fox News on Monday night that his investigators also found no proof of a cyberattack. And an FBI official cited by Fox Business pointed to something more specific: the cause was reportedly a software update that JPMorgan itself rolled out that same Monday, affecting part of its systems.

None of that takes away from the fact that the scare was legitimate. When your bank will not let you see your balance, your mind goes to the worst in seconds. That is why it helps to separate two things: the fear — understandable — and the facts, which say it was an internal technical failure, not a theft or a break-in.

Why banks with nothing broken got tangled up too

Here is the part that confused people most, and it has a simple explanation: in American banking, banks do not live in isolation. When a transfer goes through Chase — because one of the two sides has an account there — the delay spreads, even if your bank is perfectly fine.

That is exactly what happened. U.S. Bank said its systems were not directly affected, but warned its customers could face delays on Zelle payments with other institutions. Capital One and Truist said the same: their services were operating normally. And Zelle, the person-to-person payment network used by nearly all the big banks, said its network was operating “as it should”: the problem sat with the participating banks, not with Zelle.

Chase summed it up like this: “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.” In other words: if your payment did not touch Chase, it had no reason to fail. If it did, it sat waiting.

Was your money at risk?

The short answer: no. The long one: that does not mean nothing happened.

Chase repeated all day that customers still had access to their accounts and their money, and that the only effect was that some transactions took longer than usual to complete. Accounts were not emptied, balances did not vanish, and there are no reports of money lost because of the failure.

What there was, though, was money stuck in place. A Zelle payment that does not arrive on time can mean rent that runs late, a payment to a contractor left hanging, or a transfer to a relative that never shows up. And that, even if the bank fixes it within hours, leaves a mark: late fees, broken commitments, and an entire afternoon staring at a screen.

And now? The bank confirmed on Monday night, first to NBC News and then to USA TODAY, that transactions were processing normally again. If you sent a payment on Monday and it still has not shown up, do not assume it is lost: check your history before sending it again, because the real risk now is sending it twice.

What to do today, in order

  1. Check your Monday activity. Open your bank’s app and look for every payment, transfer, or deposit from November 16. If anything appears twice, or does not appear at all, write it down.
  2. Verify pending Zelle payments. If you sent money through Zelle on Monday and the recipient says it never arrived, confirm the status in the app before sending it again. A duplicated payment is worse than a slow one.
  3. Do not resend blindly. If the transaction shows as “pending” or “in progress,” let it resolve. Sending it again creates a second charge you will have to fight later.
  4. Keep the receipts. Screenshots of the error notices, of the pending transaction, and of any late fee the delay caused you. If the bank charged you something because of its own failure, that is your backup to claim it back.
  5. Do not trust the messages that arrived right after. Every big outage brings its wave of scams: texts pretending to be your bank, asking for your password or a code to “verify your account.” Your bank never asks for that by text. If you got one, delete it and call the official number on your card.

The third failure in a week, and it is no accident that it worries people

The bank outage did not arrive alone. It is the third blow to the country’s digital infrastructure in less than a week: on Thursday, November 12, Microsoft suffered a worldwide outage that knocked out Outlook, Teams, and its AI assistant for hours; on Friday the 13th, the FAA ordered a nationwide ground stop over a failure in air traffic control communications — the Arkansas router we already told you about here.

There is no confirmed connection between the three incidents. The reported causes are different: a software bug at Chase, aging equipment at the FAA, a failure at Microsoft. But the pileup is unsettling, and not only for experts. Jody Westby, CEO of cybersecurity advisory firm Global Cyber Risk, told Al Jazeera she worries everything is being waved away as “a technical issue” without a deeper investigation: “I don’t think that any of that is a complete explanation the public deserves.”

Overreaction or prudence? For now, the only official word is that they were unrelated technical failures. But when, in five days, the email of half the country, the flights, and the banks all go down, the question stops sounding paranoid: how fragile is the infrastructure your money depends on?

What is still unconfirmed

Chase has not published a detailed technical report on the failure: it is known that a software bug hit its internal systems, probably tied to a Monday update, but not the exact component or how many transactions were delayed in total. There are also no official figures on how many customers were affected beyond Downdetector’s reports, which measure complaints, not customers.

If that information appears — or if any bank announces compensation for charges caused during the outage — we will update this story here. For now, the essentials are clear: it was a Monday of banking at half speed, it was fixed the same night, it was not an attack, and your money never moved from where it was. What did move was trust, and that takes a little longer to come back.

If you are waiting on a government payment, check the dates

And if what you are waiting on is a refund

Official sources

Sources and verification

Check the corresponding official sites to confirm current requirements:

Last update of this article: .

Informational content, not tax, legal, or financial advice. Always consult official sources. Informational content, not tax, legal, or financial advice. Always consult official sources.

Comentarios

Leave a Reply

No compartas datos personales sensibles (SSN, ITIN, números de cuenta) en los comentarios.