A software bug in JPMorganChase's on-premise systems knocked out online banking for much of Monday, and because Chase holds more than 10 percent of all US deposits, the disruption reached well past its own customers. Downdetector logged about 4,500 Chase reports shortly after 1:30 p.m. Eastern and more than 20,000 by 2:22 p.m., Fortune reported as branches and third-party apps began reporting failures.

JPMorganChase spokesperson Pablo Rodriguez told Wired that the cause was “a software bug in on-premise hardware systems” and that there was “no evidence this is cyber-related.” He said the bank was not dealing with a systemic issue, and that other institutions were affected only to the extent that they were party to a transaction with Chase. Customers still had access to their accounts and funds, he said, though transactions were taking longer than usual.

Where the failure actually sat

The evidence points to a single node in the payment chain rather than a shared cloud dependency. Zelle said its own network was operating normally and that consumers reach it through their banks, which hold the funds. US Bank, Capital One, Bank of America, Mastercard and Visa all said their systems were running normally. Plaid, which connects bank accounts to budgeting and investing apps, said its network was fine but that it was seeing connection errors on Chase accounts, which is what a Chase-side authentication failure looks like from the outside.

That distinction matters for customers who spent the afternoon trying to work out whether their money was safe. Reports on Downdetector described ATMs and in-branch systems failing alongside the app, and some users opening the Chase app saw a message saying some services were unavailable. On the r/TalesFromYourBank subreddit, branch staff described being unable to serve clients, which suggests the problem sat in the systems that authorise a transaction rather than in the consumer-facing front end alone.

A bad week for infrastructure stories

The timing gave the outage a shape it may not deserve. Microsoft restored service on Saturday after a 24 hour outage took down Outlook and Teams, with executive vice president Charles Lamanna saying the cause was an update that began rolling out in July. Days earlier, a communications failure at the Federal Aviation Administration produced a nationwide ground stop, which the agency attributed to legacy equipment becoming unstable when data flooded its network at roughly 1,000 connection attempts every four to five seconds.

No bank has linked Monday's problems to either event, and the Chase statement rules out an external cause. But three unrelated failures in five days across aviation, cloud productivity and retail banking is the kind of sequence that pushes regulators toward disclosure rules, because each one was invisible to the public until customers started posting screenshots.

What Chase has done before

The bank has been here. In 2010 its online banking was down for more than a day, and chief executive Jamie Dimon apologised publicly, with the bank offering to refund late fees for customers who missed payments during the outage and called to ask. The scale is different now: mobile deposits and instant transfers mean a few hours of downtime hits far more transactions than a day did sixteen years ago, and Chase's deposit share makes its availability a question for the wider payment system rather than for one bank's reputation.

The open question is what the bug implies for the rest of the stack. On-premise hardware running core banking is exactly where institutions keep systems they cannot quickly replace, and a software fault there can outlast the incident window if the fix requires a maintenance cycle. The Microsoft outage showed how a single change can travel across courts, police and hospitals, and the FAA ground stop showed what happens when legacy equipment meets traffic it was never sized for. Neither is a bank, but the lesson transfers: the failure is usually boring, and the blast radius is set by how many other systems assume it will not happen.