Bank Outage

Chase Bank Outage: 'Software Bug' Slowed Transactions and Rippled to Other Banks; Chase Says It Was Not a Cyberattack

Illustration of a smartphone showing a spinning loading circle beside a stack of generic bank cards on a dim desk, no logos or text
Illustration (AI-generated)

Customers of several major U.S. banks spent part of Monday afternoon, Nov. 16, staring at error messages, frozen balances and transfers that would not go through. The source, according to JPMorgan Chase, was a problem inside its own systems: “a software bug in on-premise hardware systems.” The bank said repeatedly that the disruption was not a cyberattack, and a spokesperson said operations were back to normal by Monday evening, The Washington Post reported.

What happened

Trouble surfaced early Monday afternoon. Chase Support told customers on X that “it appears that we are currently working to resolve an issue with online banking,” and the bank told NBC Chicago that “due to a technical issue, some transactions are taking longer than usual to complete but customers still have access to their accounts and funds.”

Some users of the Chase mobile app saw a notice reading, “Some services aren’t available. We’re working on them. Please try back later,” according to the Post. Customers described trouble logging in, viewing balances, and making bank transfers and wire transfers, the BBC reported, citing its U.S. partner CBS News. One Chase customer in Dallas told CBS he could not deposit a check at a branch and was told the “system was down.”

The outage-tracking site Downdetector showed more than 4,000 error reports for Chase as of 12:19 p.m. CT, with Chicago among the hotspots, NBC Chicago reported. The BBC put the peak at almost 5,000 reports.

Was it a cyberattack?

According to the bank, no. In a later statement quoted by NBC Chicago, JPMorganChase said:

“It is not cyber related. It is taking longer than usual to service some customers. 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.”

Fox News reported that the incident was traced to a software release JPMorgan Chase rolled out earlier Monday that affected a subset of its systems, and that there was no indication of malicious or outside activity. A source familiar with the outage also told Fox it was a technical bug, not a cyber issue.

Chase has not publicly detailed which systems failed or how many customers were affected.

Which banks were down?

This is where reports diverge, and it is worth being precise:

Institution What was reported What the company said
JPMorgan Chase Login, balance and transfer problems; slow transactions Software bug; not cyber-related; back to normal Monday evening
Wells Fargo Customers reported sign-in, balance and transaction problems Website briefly said “Online banking isn’t available right now”; said it was investigating
Zelle Error reports climbed Told NBC Chicago “this is a Chase issue”
Bank of America Customers reported problems Said its systems “have been operating normally today”
U.S. Bank Customers reported trouble transferring funds (BBC) No detailed statement in our sources

Wells Fargo briefly posted a message saying, “We’re having technical issues, but we’re working to resolve them as quickly as possible. Please try again later,” before removing it, NBC Chicago reported. The full extent and cause of problems at banks other than Chase were not immediately clear, according to Fox News. Chase’s own statement suggested that other banks were affected mainly when their transactions involved Chase.

Users also raised questions about other institutions, such as Navy Federal Credit Union, but none of our sources documented a separate confirmed outage there.

Why it matters

Chase is the largest bank in the United States, the BBC notes, so a slowdown in its systems can touch people who never bank there: anyone sending money to a Chase customer, receiving a payroll deposit routed through Chase, or using a payment network in which Chase is a party.

The timing also amplified anxiety. Fox News described the bank problems as the latest in a string of technology failures in just five days, following a Microsoft 365 email disruption and the nationwide FAA ground stop on Nov. 13. Fact-checkers noted that these outages helped fuel unfounded online rumors of a coming “nationwide blackout” on Nov. 17. There is no evidence linking the bank outage to those claims, and Chase attributed its problem to its own software.

What to do if a payment was affected

Chase said customers kept access to their accounts and funds throughout. If you sent or expected money on Monday afternoon:

  • Check your transaction history before resending a payment, to avoid paying twice.
  • Look for pending items. Transfers delayed during the outage may post later than usual.
  • Contact your bank directly if something still looks wrong. Bank of America, for example, told customers who saw delays with other providers to contact those providers.
  • Watch for scams. Outages are a common hook for phishing texts and calls. Banks do not ask for passwords or one-time codes by phone.

This article is for general information and is not financial advice.

FAQ

Is Chase Bank down right now?

A Chase spokesperson said operations were back to normal Monday evening, Nov. 16, and the bank told Fox News that transactions were processing normally.

What caused the Chase outage?

Chase said it was “a software bug in on-premise hardware systems.” Fox News reported it was traced to a software release rolled out earlier Monday.

Was it a cyberattack?

Chase said it was “not cyber related,” and Fox News reported no indication of malicious activity.

Was Wells Fargo down too?

Wells Fargo acknowledged online banking problems and said it was investigating. Chase said other banks may have been affected when they were party to transactions with Chase.

Is it related to the United Airlines outage?

There is no confirmed connection. United also said its Monday outage showed no sign of being cyber-related.

Sources