JPMorgan Chase has resolved a “technical issue” that caused transactions to take longer than usual to complete for much of Monday.
A spokesperson for the nation’s largest bank confirmed to Bloomberg that transactions were processing normally by Monday evening, after JPMorgan customers reported an uptick in errors accessing the bank’s services.
The spike began roughly around 10 a.m. Eastern time Monday, according to Downdetector. Service disruption appeared to multiply around noon and reach a peak of nearly 4,700 reported errors at 2 p.m., the website indicated.
But disruption wasn’t contained to JPMorgan. Customers of Bank of America, Wells Fargo, U.S. Bank – and, to a lesser degree, PNC, Capital One and Truist – also reported errors, generally cresting between 2 and 3 p.m. Monday, according to Downdetector.
“JPMorganChase has experienced a temporary issue related to a software bug in on-premise hardware systems – there is no evidence this is cyber-related,” the bank posted on X at roughly 3 p.m. Monday. “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.”
One commonality among the seven biggest banks experiencing an uptick in service disruption Monday is that they’re all co-owners of Zelle, the peer-to-peer payment platform.
Zelle, which saw a disruption spike of its own Monday, noted it is “operating as it should.”
“Consumers use Zelle through participating banks and credit unions, which manage their accounts and hold their funds,” a Zelle spokesperson told The New York Post. “Zelle is not down.”
Roughly 53% of the errors reported by Chase users were related to account balances and transactions, Downdetector reported. About 20% reported issues with web logins. And 17% said they saw disruption with fund transfers and wires.
JPMorgan said other banks may have been impacted “only to the extent that they were a party to a transaction with us.”
Several other banks, meanwhile, made statements of their own Monday.
“Capital One has not experienced any issues impacting customers’ accounts or services and continues to operate normally at this time,” the bank wrote Monday in a post on X.
A U.S. Bank representative told CNBC the company was “not directly impacted” by the reported service disruptions.
“However, clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays,” the representative said.
A Bank of America spokesperson told CBS News its “systems have been operating normally [Monday].”
Bank customers are hardly alone in experiencing service disruptions on wide-ranging platforms. Microsoft users saw outages Thursday and Friday on the company’s Outlook, Teams and Copilot tools.
Overloaded routers prompted the Federal Aviation Administration on Friday to order a nationwide ground stop. Airline schedules were returning to normal by Sunday, the FAA said, though United Airlines said Monday it resolved a “widespread system outage” from earlier in the day.
“Our country has seen three very serious technology incidents over the past week,” Mike Chapple, a cybersecurity author and professor at the University of Notre Dame, said in a statement to CBS News. “When we dig into the details, each one has an explanation that makes sense on its own, but they all point to a common theme: the complexity and fragility of the systems that we depend on every day.”
Karen Panetta, a professor of computer science and mechanical engineering at Tufts University, warned that when one massive company suffers an outage, its interconnected partners can see follow-on effects.
“The larger companies have global reach that affords their customers flexibility and seamless integration with other businesses,” Panetta told CBS News. “Unfortunately, when one of these backbone providers has disruptions, the downstream effects are magnified.”
At one point during Monday’s disruption, some Chase customers reported receiving a message that “some services aren’t available. We’re working on them. Please try back later.”