@2026 Finance News International. All Rights Reserved.

Blends Media
A Blends Media Group Production

Outage Reports Hit Major U.S. Banks as Chase Cites Software Bug

Arry Hashemi
Arry Hashemi
Nov. 17, 2026
JPMorganChaseJPMorganChase blamed a software bug, not a cyberattack, for the disruption that also hit customers at other major U.S. banks. (Felix Lipov/Shutterstock)

New York — JPMorganChase said a software bug in on-premise hardware systems slowed service for some Chase customers, as user reports of problems climbed at several of the largest banks in the United States, including Bank of America, Wells Fargo and U.S. Bank.

The bank addressed the disruption in a post on Chase's X account. It ruled out, on the evidence it had, a cyber incident, and said lenders that dealt with Chase on a transaction might have felt the effects, while stressing that the problem was not systemic. Customers could still reach their accounts and money, it added, and it aimed to have the issue fixed before the day ended.

JPMorganChase said in the statement: “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. We’re working diligently to resolve this by the end of the day today.”

Trouble had surfaced hours earlier. Outage tracker Downdetector flagged user reports about Chase from 9:53 a.m. Eastern Time, and by lunchtime the bank's customer care team was answering complaints on X. One reply from the Chase Support account, posted at about 12:48 p.m., read: “We saw your post and want to reach out. I do apologize, it appears that we are currently working to resolve an issue with online banking. Please try again at a later time. We're sorry for any inconvenience, and appreciate your patience.”

Other names followed on the tracker over the next two hours. Downdetector's own alerts showed reports building for Zelle from 11:33 a.m., Bank of America from 11:42 a.m., U.S. Bank from 12:35 p.m. and Wells Fargo from 12:46 p.m., then PNC from 1:40 p.m. and Capital One from 1:41 p.m. These alerts are driven by problems that users submit to the site, so they show where customers ran into trouble rather than confirming a failure inside each bank.

The type of complaint points to everyday banking rather than a single app. On Downdetector's Chase status page, checked early on Tuesday and covering the previous 24 hours, 53% of reports concerned account balances and transactions, 20% web login and 17% transfers and wires.

U.S. Bank, one of the lenders named on the tracker, said its own platform was working. Replying to a customer on its official X account at about 4 p.m., U.S. Bank said: “U.S. Bank systems are not directly impacted. However, clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays.”

The scale of the Chase franchise helps explain why a fault there may travel. JPMorganChase says its Consumer & Community Banking business serves 80 million individuals, families and businesses, and that its technology operation is powered by more than 60,000 technologists. The bank did not say how many customers were affected on Monday, and by early Tuesday it had not posted a further update on X confirming that the issue was fully resolved.

The disruption capped a week of high-profile technology failures in the United States. On November 12, Microsoft began investigating problems with access to Exchange Online mailboxes in the Americas. In an update on November 13, the Microsoft 365 Status account said the incident was a technical issue not related to cyber or AI / agents, and was introduced by an issue during an earlier network capacity upgrade that surfaced after a recent network change.

That Friday, the Federal Aviation Administration (FAA) issued a nationwide ground stop at about 3:30 p.m. Eastern Time after what it called a technical problem. According to the agency's questions and answers, its legacy equipment became unstable when data flooded its telecommunications network at a rate of 1,000 connection attempts every 4 to 5 seconds, and air traffic resumed at 8:15 p.m. The FAA said it had no indication of a cyberattack, and that operators canceled about 12,462 flights that day, though not all of those cancellations were directly caused by the ground stop.

There is no public evidence linking the three incidents, and each operator has given its own technical explanation. They may still sharpen questions from customers and regulators about how older on-site systems and routine upgrades are managed at institutions that millions of people rely on daily. Finance has felt this before: an Amazon Web Services outage in October 2025, traced to a Domain Name System (DNS) resolution issue in its US-EAST-1 region, temporarily locked most Coinbase users out of their accounts.

Microsoft has said it will publish a full post-incident report once its review is complete, and the FAA said it and its network provider L3Harris continue to investigate the root cause of Friday's failure. JPMorganChase has not yet said whether it will release further detail on the hardware systems behind Monday's bug.