Search
Money

Chase says transactions are back to normal after software bug slowed banking nationwide

A glitch in the bank's own hardware stalled deposits, transfers and Zelle payments for hours Monday, reaching customers at other banks.

The JPMorgan Chase Tower skyscraper in Houston, Texas, rises against a clear blue sky.
File photo. Photo: Jim Evans / Wikimedia Commons, CC BY-SA 4.0

Key Takeaways

  • Chase blamed a software bug in its on-premise hardware and said there was no sign of a cyberattack.
  • Delays reached customers at other banks and on Zelle when their transactions involved Chase.
  • Chase hasn't said how many of its roughly 94 million U.S. customer relationships were affected.

JPMorgan Chase said transactions were posting normally again by about 6:30 p.m. ET Monday. A software bug had slowed its consumer banking for much of the day, and the delays spread to customers of other banks and to Zelle users.

The bank traced the problem to a temporary software bug in its on-premise hardware systems and said it had found no sign of an attack. "There is no evidence it is cyber-related," a JPMorgan spokesperson said. All day, Chase said customers could still reach their accounts and money, only that some transactions were slower than usual.

Customers described a rougher day. Some reported trouble getting into their accounts and withdrawing cash. The problems hit transactions inside branches as well as online and in the app. A Chase customer in Texas told CBS News he could not deposit a check at a Dallas branch early Monday, and that a teller told another customer only that the "system was down."

Chase hasn't said how many accounts were affected. The bank has roughly 94 million customer relationships in the United States, about 5,000 branches and 15,000 ATMs. Even a small share of that base is a lot of people waiting on a paycheck deposit or a rent transfer.

How one bank's bug reached other banks

The first error reports appeared as early as 11:30 a.m. ET, and a person familiar with the matter said the outage began Monday morning. Complaints rose through the afternoon on Downdetector, which tracks user-submitted outage reports. As of 2 p.m. ET, nearly 4,800 users had reported problems with Chase, more than for any other bank. People said they couldn't see balances or complete transfers and wire transfers, and some saw an app message saying certain services weren't available.

Downdetector also showed spikes for Bank of America, U.S. Bank, Capital One, Truist, Wells Fargo and Zelle. Most of those banks said their own systems were fine. Bank of America said its systems had been operating normally all day, and Capital One said it had not been affected. PNC said it saw no direct impact and that the outside delays it was aware of appeared to be clearing. Truist said its services were working normally and it knew of no broad disruptions.

U.S. Bank said its systems were not directly affected, but its clients sending or receiving Zelle payments with another institution might see delays. Wells Fargo customers also ran into slowdowns, according to NBC News, and the bank did not provide a statement to that outlet. Citibank declined to comment to NBC News.

Chase's explanation was that other banks felt the slowdown only when they were on the other side of a transaction with Chase, and it called the problem not systemic. That's technically accurate. For someone at another bank whose Zelle payment to a friend at Chase sat in limbo, though, it was a distinction without much difference. Chase sits on one side of a huge share of everyday U.S. payments, so a bug confined to its own hardware can still show up across the system.

Zelle insisted it was not the source. "Zelle is not down. Zelle is operating as it should," the company said, adding that the trouble originated with Chase and that customers should contact their banks. Zelle has no separate accounts and holds no customer money. Banks and credit unions run the accounts behind it, and its network operator, Early Warning Services, is owned by banks including Chase, Bank of America, Capital One, PNC, Truist, U.S. Bank and Wells Fargo. That setup is why one large bank's problem can look like a Zelle outage to users who never deal with Chase directly.

Regulators contacted the large banks involved right away and quickly concluded the problem was contained and that service was already being restored, according to a person familiar with the situation. Another person familiar with the matter said the disruption was limited to retail banking and not tied to the rest of JPMorgan Chase's business.

A week of breakdowns with different causes

Monday's problems came at the end of a bad stretch for systems Americans rely on daily. Microsoft Outlook was down for about 48 hours last week, a failure the company attributed to a capacity upgrade and said was not a cyberattack, with service restored Saturday. On Friday, the Federal Aviation Administration ordered a nationwide ground stop lasting several hours. The stop was blamed on overloaded routers and on what U.S. officials described as a botched facilities upgrade. And Monday afternoon, United Airlines dealt with a widespread system outage that it said it had resolved by evening.

There is no evidence the incidents are connected. Mike Chapple, an IT and operations expert at the University of Notre Dame, said each one has its own reasonable explanation but that together they reveal "the complexity and fragility of the systems that we depend on every day." Karen Panetta, dean of graduate engineering at Tufts University, made a related point about scale: "Unfortunately, when one of these backbone providers has disruptions, the downstream effects are magnified."

That seems the most useful way to read the week. The common thread is concentration rather than a single villain or a coordinated attack. A few providers handle email, air traffic routing and consumer payments for enormous numbers of people, so routine maintenance or a single software defect can affect millions at once. Chase's case also shows that keeping critical systems on its own hardware, rather than with an outside cloud provider, offers no protection against a bad bug.

Chase's communication left room for improvement. Users began reporting errors late in the morning, and by early afternoon the bank had said that a technical bug, not a cyberattack, was behind the trouble. But its statements described only "some transactions" running slow, without saying which kinds. Early in the day, at least one branch teller could say only that the system was down. Customers at other banks whose payments stalled had even less to go on, since their own banks were reporting that everything was fine. Chase's statements were consistent and calm, but more specific guidance on which transactions were affected would have spared customers a lot of guessing.

What customers can do now

Anyone whose payment, deposit or transfer failed Monday should check that it went through now that Chase says transactions are posting normally. Kayne McGladrey, a security expert and senior member of the Institute of Electrical and Electronics Engineers, recommended keeping screenshots of failed transactions and error messages for any later disputes. She also said customers should ask their bank to reverse any fees the outage caused once service is restored.

During an outage, McGladrey said, other options can still work: "Try ATMs, cards, phone banking and branches, which often keep working when the app doesn't." Monday was a partial exception, since some of the trouble reached Chase branches, but in-person service did appear to recover by late afternoon. Several Manhattan branches were operating normally by then, according to NBC News.

The bigger risk now may be fraud. McGladrey warned that unsolicited emails about the outage could be phishing and said people should rely only on their bank's official channels. Craig Timm, senior director of anti-money laundering at ACAMS, an anti-financial-crime group, said consumers should "assume they will be targeted." He expects scammers to use fake bank alerts, phishing texts and emails, and social media posts offering help, all pushing people to act quickly to protect their money or restore access. A real bank glitch gives those messages a believable pretext, so for the next few days, any message about Monday's outage that asks for a login or a click deserves suspicion.

Sources

Vivian Clarke

Vivian Clarke covers retirement planning news, pension developments, and long term saving. Her work follows changes to retirement programs, savings rules, and the economic conditions affecting later life finances. She explains terminology, published figures, and the scope of policy announcements, helping readers understand the context behind developments in retirement income and future household costs.

View all stories