Skip to main content
Diagram: how one bank's transaction backlog reached customers at five institutions. Illustration: SecurityXP

Five US Banks Hit by Outage Reports as Chase Blames Software Bug

· 7 min read · SecurityXP Editorial Desk

Key Facts

  • JPMorgan Chase said a software bug in on-premise hardware systems slowed transaction processing on Monday, November 16, 2026, and that there was no evidence the incident was cyber-related.
  • Downdetector recorded about 4,800 reports for Chase around 2 p.m. Eastern, plus more than 2,100 for Bank of America and more than 1,050 each for US Bank and Wells Fargo at their peaks.
  • Bank of America, US Bank, PNC, Capital One and Truist said their own systems were not directly affected or were operating normally.
  • Zelle said its network was operating normally and that delays came from problems at participating banks.
  • Chase said transactions were posting normally again by about 6:30 p.m. Eastern; Plaid resolved its Chase-connections incident at 7:34 p.m.

Customers at five large US banks ran into failed logins, unavailable balances and stalled transfers on Monday afternoon, in a disruption that JPMorgan Chase traced to a software bug in hardware it runs itself. Chase, Bank of America, Wells Fargo, PNC and US Bank all drew clusters of reports on Downdetector between about 1:40 p.m. and 2 p.m. Eastern. Chase said there was no evidence the problem was a cyberattack.

The common thread was Chase. The bank is the largest in the United States and a counterparty for a large share of interbank and peer-to-peer payments, so when its transaction processing slowed, customers at other institutions felt it even where those banks’ own systems were healthy. Bank of America, US Bank, PNC, Capital One and Truist said they were not directly affected or were operating normally. Wells Fargo acknowledged an online-banking problem on its website, and Chase’s app told some customers that “some services aren’t available.”

What Happened

The first public signal came shortly after 12:30 p.m. Eastern, when Chase’s customer-support account on X replied to a complaint by saying it was “currently working to resolve an issue with online banking.” Reports on Downdetector climbed through the early afternoon and peaked around 2 p.m., with about 4,800 reports for Chase, according to USA Today. The BBC’s live coverage put the peaks above 2,100 for Bank of America and above 1,050 each for US Bank and Wells Fargo.

Those numbers measure customer complaints, not confirmed outages, and they fall quickly once service returns. By 6:30 p.m. Eastern, the BBC reported that Chase reports had dropped to about 1,300, Bank of America to about 700, US Bank to more than 450 and Wells Fargo to almost 400.

Chase posted its fullest statement at 3:57 p.m. Eastern:

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.

A Chase spokesperson told NBC News around 6:30 p.m. that transactions were “now posting normally.” The bank said in an email to USA Today shortly after 7 p.m. that transactions were “being processed normally now.” The data aggregator Plaid, which connects fintech apps to bank accounts, resolved its own “service disruption impacting Chase connections” incident at 7:34 p.m. and said the intermittent errors on Chase’s side had cleared.

The Federal Reserve’s financial systems, including the ACH network that moves payments between banks, were operating normally, ABC News reported.

Why One Bank’s Bug Reached Five

The five banks did not suffer five independent failures. Chase sits in the middle of a payment graph that includes direct interbank transfers and Zelle, the peer-to-peer network owned by Early Warning Services. Early Warning is itself owned by Bank of America, Capital One, JPMorgan Chase, PNC Bank, Truist, US Bank and Wells Fargo.

Zelle said its own network was not down. “An issue at the financial institutions may be delaying Zelle payments for some of their customers,” a spokesperson said. US Bank put it more plainly: its systems were not directly impacted, but “clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays.”

That is how a single backlog becomes a five-bank story. A customer at PNC or US Bank can see a stalled transfer without either bank’s core systems being degraded, because the other leg of the transaction sits at Chase. Bank of America told USA Today that clients experiencing delays with other providers “may wish to contact them directly.”

Independent security researcher Katie Moussouris told the New York Post that the pattern suggested a shared backend component. “It could be a really wild coincidence, but it seems like they share a component on the backend,” she said. Chase’s own account is narrower: the shared component was Chase itself, and only for transactions where it was a party.

What Each Bank Said

Institution Position
JPMorgan Chase Software bug in on-premise hardware; no evidence of cyber involvement; not systemic; transactions posting normally by about 6:30 p.m. ET
Bank of America Systems not directly impacted; customers with delays involving another provider should contact that provider
Wells Fargo Website said online banking was unavailable; the notice was later removed; no later public resolution statement
PNC Bank Not directly impacted, but aware of reports about delays
US Bank Systems not directly impacted; cross-institution Zelle payments may be delayed
Capital One Not impacted; operating normally
Truist Operating normally; no broad service disruptions
Zelle / Early Warning Network operating normally; delays originate at participating banks

Wells Fargo’s website carried the clearest customer-facing admission of the group. “Online banking isn’t available right now,” the message said, according to NBC Chicago. It disappeared from the site later in the afternoon. The bank did not publish a subsequent all-clear that matched Chase’s level of detail.

The Security Question

Chase’s statement answers the first question a security team asks after an outage: was this an attack? The bank says no evidence points that way, and a Justice Department official, speaking anonymously to MS NOW, said there was “no evidence of any attack” linked to the disruptions. Those are statements about evidence, not proof of absence, and Chase has not published a technical root-cause report.

The distinction matters because reliability failures and security incidents can look identical from the customer’s side. A failed login, a stale balance and a payment stuck in pending are the same three symptoms whether the cause is a bad deploy, a hardware fault, a certificate expiry or an intruder. Until the bank publishes a timeline and a cause, customers and counterparties are relying on its characterization.

Jody Westby, chief executive of Global Cyber Risk, told Al Jazeera that the public deserves more than a one-line explanation. “I think it’s very concerning that everyone’s just jumping to the conclusion it’s a technical issue, it’s a software bug, it was old equipment,” she said. “I don’t think that any of that is a complete explanation the public deserves.”

The incident lands in a crowded week for US infrastructure. Microsoft spent Thursday and Friday recovering from a global outage that took Outlook, Teams and Copilot offline. The Federal Aviation Administration imposed a nationwide ground stop on Friday after a router upgrade flooded its air-traffic-control network. United Airlines suffered its own system outage on Monday. No connection between those events and the bank disruption has been confirmed, and their stated causes are different. The common lesson is not a common attacker; it is that a handful of shared providers can turn separate failures into a week that feels systemic.

What Customers Should Do

  • Check whether a delayed payment is still pending before sending it again. Duplicate transfers can take days to reverse.
  • Keep screenshots of error messages, timestamps and any fees or late charges that follow a failed payment.
  • Use the bank’s official app or branch rather than links in texts or emails. Outages are a reliable hook for phishing.
  • Ask the bank to reverse overdraft or late fees caused by a delayed transfer; keep the reference number.
  • Watch for unusual login prompts or password-reset messages in the days after an outage, and report them to the bank.

Timeline

Time (ET) Event
12:48 p.m. Chase Support acknowledges an online-banking issue on X
~2:00 p.m. Downdetector reports peak at about 4,800 for Chase
3:57 p.m. Chase posts statement blaming an on-premise software bug
~6:30 p.m. Chase says transactions are posting normally
7:34 p.m. Plaid resolves its Chase-connections incident

Chase has not said which hardware system failed, how long the bug was present or whether the fix required a restart, a rollback or a configuration change. Those details will determine whether the incident was a one-off or a warning about the bank’s concentration risk. For now, the public record supports a narrower conclusion than the first wave of social posts: five banks showed symptoms, one bank described the fault, and no evidence of an attack has been made public.

Tags: JPMorgan Chase Bank of America Wells Fargo PNC Bank U.S. Bank Zelle Operational Resilience Payment Systems

Sources & References

SE SecurityXP Editorial Desk
SecurityXP Editorial Desk Vulnerability Research & News Board

Automated and analyst-reviewed threat intelligence briefings tracking active exploitation campaigns, CVE disclosures, and extortion group activity.

Security Digest

The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.

Related Articles