HomeCryptoUS Bank Outages: Chase Blames Software Bug as Reports Hit Bank of...

US Bank Outages: Chase Blames Software Bug as Reports Hit Bank of America, Wells Fargo and U.S. Bank

US bank outages on Nov. 16 hit Chase, Bank of America, Wells Fargo and U.S. Bank. Chase cites a software bug, not a cyberattack. Here is what we know.

Customers at several of the largest US banks reported trouble with online accounts on Monday, November 16. Reports on Downdetector began climbing shortly after 9 a.m. Eastern Time. Chase drew the most complaints, with nearly 4,800 reports by 2 p.m. ET, according to CBS News. Bank of America logged more than 1,900 reports, while U.S. Bank passed 900 and Wells Fargo reached roughly 800. Customers described failed balance checks, stalled transfers and wires, and sign-in errors. Some Chase users saw a message saying certain services were unavailable. By 4 p.m. ET, reports appeared to decline, although they stayed elevated across several banks.

What Chase Says Caused the Problem

Chase is the only bank that has named a cause so far. A spokesperson called the incident a technical issue and said it was not a cyber issue. According to Reuters, the bank said some transactions were taking longer than usual to complete. However, Chase said customers still had access to their accounts and funds. In a social media post, the bank said a software bug affected other institutions during transactions that involved other banks. Chase also said the issue was not systemic. Importantly, no outside party has verified that account, and the bank has not published a full technical explanation.

Why Zelle Sits at the Center of the Story

Zelle appeared on the Downdetector list alongside the banks, which raised questions about shared payment rails. Zelle’s operator, Early Warning Services, has seven bank owners. Those owners include Bank of America, Capital One, JPMorgan Chase, PNC, Truist, U.S. Bank and Wells Fargo. Zelle said its service operated as it should and pointed to problems at customers’ own financial institutions. The company also noted that it does not hold consumer funds. Meanwhile, U.S. Bank said its own systems were not directly affected. The bank warned that Zelle payments with other institutions could still see delays. CBS News reported that the outage appeared to start at Chase and spread to other banks through shared payment networks. Neither Chase nor the other banks have confirmed that description of a chain reaction.

Conflicting Accounts Across the Banks

The picture varies sharply from one bank to the next. Capital One told reporters it was operating normally. Reuters reported that some banks it contacted saw no significant issues, despite the spike in user reports. In contrast, Wells Fargo customers described trouble signing in and completing transactions. One outlet said the Wells Fargo website showed online banking as temporarily unavailable. Fox Business, however, reported that Wells Fargo said Monday’s events did not affect it. These conflicts matter because Downdetector counts user submissions rather than verified outages. A spike in reports can reflect real failures, but it can also reflect customers who see delays on payments sent from another bank.

A String of Recent Infrastructure Failures

The bank problems arrived after other high-profile technology disruptions. CBS News noted a recent Microsoft outage that hit Outlook and Teams, which Microsoft blamed on a technical issue rather than a cyberattack. Days earlier, overloaded routers led the FAA to issue a rare nationwide ground stop. Mike Chapple of the University of Notre Dame told CBS the incidents point to “the complexity and fragility of the systems that we depend on every day.” Separately, Kayne McGladrey of the IEEE advised affected customers to screenshot failed transactions and error messages. He also suggested asking banks to reverse any fees tied to the outage. Each of these events had a different cause, so analysts should not treat them as one trend.

What It Means for Payments Infrastructure

No report reviewed for this article linked Monday’s disruption to any crypto network. Even so, the episode highlights how many bank-to-bank payments depend on a small number of shared systems. When one large participant introduces a fault, other institutions can feel the effects. Stablecoin and onchain settlement networks use a different design, since many validators keep them running at all hours. Nevertheless, those networks have their own outage histories and software risks. Furthermore, most users still reach stablecoins through banks and exchanges, so a bank failure can still block access. Readers should therefore watch the Chase post-mortem closely. A detailed explanation will show how far one software fault can travel across modern payment rails.

*Disclaimer: News content provided by Genfinity is intended solely for informational purposes. While we strive to deliver accurate and up-to-date information, we do not offer financial or legal advice of any kind. Readers are encouraged to conduct their own research and consult with qualified professionals before making any financial or legal decisions. Genfinity disclaims any responsibility for actions taken based on the information presented in our articles. Our commitment is to share knowledge, foster discussion, and contribute to a better understanding of the topics covered in our articles. We advise our readers to exercise caution and diligence when seeking information or making decisions based on the content we provide.

RELATED ARTICLES
spot_img

Latest

Most Popular