Banking · 18 November 2026
JPMorgan Chase Outage: Transaction Delays and Customer Access Issues Resolved
JPMorgan Chase has fixed a technical fault that delayed customer transactions and drove a sharp rise in Downdetector error reports, according to Banking Dive. Reports also rose among users of other large banks.
What happened
JPMorgan Chase has fixed a technical issue that delayed customer transactions and triggered a sharp rise in error reports on Downdetector, the outage-tracking service. Banking Dive reported that thousands of people had experienced access problems before the bank resolved the fault.
The reports were not confined to Chase. Downdetector error reports also rose among users of other large banks, so the disruption was visible beyond a single institution's customer base.
Why it matters
For a bank, payments and account access are the core service. When transactions stall, customers rarely separate the failure from the brand. They experience it as the bank being unavailable. Digital channels make that moment visible in real time, and public outage trackers turn one person's frustration into a shared, searchable signal that others can see.
The cross-bank element adds a further layer. When reports spike across several institutions at once, customers may suspect a shared dependency rather than a single provider's fault. That raises the cost of uncertainty for the whole category, not only for the institution that was affected.
The Renascence take
Most coverage of an outage stops at the word "resolved". The more useful question for experience leaders is what customers were told during the hours it lasted, and whether they could tell a stalled transaction from a lost one.
The real test of an outage is not the fix but the silence before it. Customers who receive no acknowledgement fill the gap with the worst assumption, and that is where trust erodes fastest. Operators should treat incident communication as a designed service, with a status message that appears within minutes, a clear statement of what is and is not affected, and a follow-up confirming that pending transactions have completed. Build that playbook before the next incident, because writing it mid-outage is already too late.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Banking
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


