Bank outage hits Chase, spreads to Wells Fargo, BofA and delays Zelle payments
The technical glitch that began on Monday morning triggered a wide‑reaching bank outage affecting JPMorgan Chase and spilling over to other large institutions such as Wells Fargo, Bank of America, US Bank, Truist and Capital One. Customers reported being unable to log in, view balances or complete transfers, while a number of users also experienced delays when sending money through the Zelle peer‑to‑peer network. The problem was traced to a software bug in Chase’s on‑premise hardware system, a spokesperson said.
Joe Evangelisti, the official spokesperson for JPMorgan Chase, told reporters the issue was “temporary” and unrelated to any cyber‑attack. He explained that the fault lay in an internal hardware component that slowed the processing of transactions, especially those involving other banks. While Chase’s own customers could still access their accounts, the slowdown created a ripple effect that made it harder for partner institutions to settle payments in real time. “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,” Evangelisti added.
The outage was first noticed by users of Chase’s online platform, but by mid‑afternoon, reports of problems had spread to at least five other banks. Wells Fargo and Bank of America confirmed that some customers faced difficulties with account access and fund transfers, although both institutions maintained that their core systems remained intact. US Bank explicitly stated that its own infrastructure was not directly affected, yet it warned that customers attempting Zelle payments involving other banks could still encounter delays. Capital One and Truist similarly reported normal operations on their end, suggesting that the bottleneck originated primarily within Chase’s processing network.
Zelle, the popular instant‑payment service used by most major U.S. banks, also felt the impact of the bank outage. Owned by a consortium that includes Bank of America, Capital One, JPMorgan Chase, PNC Bank, Truist, US Bank and Wells Fargo, Zelle’s network was technically up and running, according to a statement from the company. However, because users access Zelle through their banks’ online portals, any disruption at those banks can hinder the ability to send or receive money, even if Zelle’s own servers are functional. This explains why some customers saw their peer‑to‑peer transfers stall despite the service’s claim of normal operation.
By roughly 2 p.m. Eastern time, outage‑tracking site Downdetector showed a peak in complaints, after which the volume of reports began to taper off. Later in the evening, at about 6:30 p.m. (23:30 GMT), Chase announced that transaction processing had returned to normal levels. NBC News corroborated that payments were posting again, although the bank cautioned that not every delayed transaction might have been fully resolved at that point. Customers were advised to monitor their accounts and expect possible residual lag in pending transfers.
The bank outage occurred in the wake of two other high‑profile technology failures in the United States. The previous Thursday, Microsoft suffered a widespread outage that knocked out Outlook and other Office services for millions of users. The following day, the Federal Aviation Administration experienced a ground‑stop after a technical fault disrupted air‑traffic communications. While investigators have linked each incident to distinct causes, a software bug for the banking issue, and malfunctioning equipment for the FAA problem, some experts argue that the string of events raises broader questions about the resilience of critical infrastructure.
Jody Westby, chief executive of the cybersecurity consultancy Global Cyber Risk, warned that “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 urged deeper investigations to determine whether any hidden connections exist among the recent disruptions. “My concern is that we are not diligently looking into these incidents and analysing them,” Westby said, emphasizing the need for a coordinated global effort to assess potential correlations.
As the day drew to a close, most banks reported that services were back online and that customers could resume normal banking activities. Nevertheless, the episode highlighted the interdependence of the U.S. financial system, where a flaw in one institution’s backend can cascade across the sector. JPMorgan Chase has not indicated any immediate plans for a system audit, but industry observers expect heightened scrutiny of legacy hardware and software as banks seek to prevent similar outages in the future.
















Join the conversation