US basedUS hosted
Desks
$2 / month

Comment and reply across TML.

Start or manage membership

Most pulsed

Advertisement Sinscents Bad Intentions. Great Candles.

Latest from other desks

tml.the modern leap
Money / Personal Money

Chase Software Bug Slows Banks and Zelle Payments

A software bug in JPMorgan Chase's on-premise hardware slowed transactions at the country's largest bank on Monday, November 16, 2026, and the delays rippled into Bank of America, Wells Fargo, U.S. Bank, Capital One and Zelle payments that touched Chase. Chase says it isn't a cyberattack and isn't systemic, customers still have access to their accounts and funds, and the bank is working to have the issue resolved by the end of the day.

JPMorgan Chase headquarters at 270 Park Avenue in New York in May 2026 (archive). A software bug in the bank's on-premise hardware slowed transactions on November 16. Photo: Ajay Suresh, CC BY 4.0, via Wikimedia Commons.
Summary

One bank's bug became everybody's slow payment on Monday, because so much of the country's money moves through Chase. The bank says the fix lands by the end of the day — and that the money itself was never gone, just late.

Tap a passage. React to the part that matters.

The country's largest bank spent Monday telling customers their money was fine and their payments were just slow. JPMorgan Chase confirmed on November 16, 2026, that a software bug in its on-premise hardware systems was taking longer than usual to service some customers, after outage reports for Chase, Bank of America, Wells Fargo, U.S. Bank, Capital One and the Zelle payment network surged through the afternoon.

Chase's statement drew the boundary lines early. The problem is "a software bug in on-premise hardware systems — it is not cyber related," the bank said, and "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." A Justice Department official with direct knowledge of the matter separately told reporters there was no evidence of any attack.

The timeline shows one bank's failure, not five. Downdetector logged Chase first, at about 9:53 a.m. ET, and the other banks one to four hours later, as payments to and from Chase accounts backed up. Reports peaked at about 2 p.m. ET. Luke Kehoe, lead industry analyst at Downdetector's parent company Ookla, said Chase recorded its second-highest number of outage reports in a 15-minute period in at least a year early Monday afternoon.

Zelle and U.S. Bank both described the same mechanics from their side. Zelle said its network was operating as it should and that the delays started with Chase. U.S. Bank said its own systems weren't directly impacted, but clients sending or receiving Zelle payments with another institution could see transaction delays. In other words, the pipes were open — the water was stuck at one end of them.

Four office chairs in a rowFor businessesAmazon Business is Amazon’s purchasing store for companies, with business accounts and quantity ordering.Register with Amazon Business

What customers actually lost on Monday was time, not access. Chase said customers still have access to their accounts and funds, and that some transactions are simply taking longer than usual to complete. By late afternoon the pressure was easing: outage reports for Chase had fallen to less than half their peak by about 5 p.m. ET, though the bank hadn't yet announced an all-clear. Its stated target is to have the issue resolved by the end of the day.

The outage lands at the end of a week that has made a lot of Americans stare at error messages. A Microsoft 365 failure knocked out Outlook and Teams on November 12, and a faulty router during an FAA system upgrade grounded flights nationwide for four hours on November 13. There's no evidence the three failures are connected — each owner has named a separate, ordinary technical cause — but three unrelated breakdowns in five days is its own kind of story about how much daily life runs through a handful of systems.

The practical questions are the ones Chase hasn't answered yet. The bank hasn't said which hardware carried the bug, whether any transactions failed outright instead of completing late, or whether business customers who missed payment windows will be made whole. Those answers matter more than the outage itself, because the next software bug is a certainty. What customers learned Monday is that when it arrives at Chase, it doesn't stay at Chase.

The conversation

A little more perspective.

Reading is free. Verified members can comment and reply for $2 a month.

The conversation.

Loading comments…

Keep your curiosity going.

Some links here are affiliate links. If you buy through one, we might make a commission — it never changes what you pay. As an Amazon Associate I earn from qualifying purchases.