Field report W-33 / N6 · sheet /operations
Operations & RestructuringFiled from the territory
Chase Confirms Technical Issue Behind Nationwide Banking Disruptions
Chase says a technical issue, not a cyberattack, slowed transactions nationwide Monday, with thousands of outage reports hitting Chase, Bank of America, Wells Fargo and Zelle.
- Grid
- W-33 / N6
- Surveyed
- November 17, 2026
- Reading
- 4 min read
- Correspondent
- Priya Raman

Field notes
- Thousands of customer reports hit Chase and other major U.S. banks on Monday, per Downdetector.com
- Chase confirmed: 'This is a technical issue, not cyber-related'
- Bank of America, Chase, J.P. Morgan, U.S. Bank, Wells Fargo and Zelle were all flagged by users
- The disruption came within five days of a major Microsoft outage and aviation interruptions, with no established connection
- It remains unclear when all services will be fully restored
Thousands of U.S. bank customers lost reliable access to online and mobile banking Monday, with the heaviest volume of complaints aimed at Chase, according to outage-tracking site Downdetector.com. The bank confirmed a technical fault, not a cyberattack, and said restoration work was underway with no fixed timeline.
Bank of America, Chase, J.P. Morgan, U.S. Bank, Wells Fargo and Zelle (the peer-to-peer payment network owned jointly by major U.S. banks) were all flagged by users reporting problems. The bulk of the reports involved Chase, where customers at a branch in Durham, North Carolina, said transactions would not go through.
What actually broke?
By Chase's own account, the fault slowed payments rather than blocking accounts. In a statement, the bank said: "Due to a technical issue, some transactions are taking longer than usual to complete, but customers still have access to their accounts and funds. We are working to resolve this as quickly as possible. This is a technical issue, not cyber-related."
That distinction matters. A slowdown means money and account access remain intact; transfers simply lag. Some Chase customers confirmed they could still withdraw cash at ATMs even while other services misbehaved.
The failure mode, as described by customers, was inconsistent rather than total. Some transfers stalled. Some transactions failed outright. Others went through without a hitch.
What did customers experience?
At the Durham branch, the confusion was immediate and personal. "It's kind of weird. Everything's going at once," Chase customer Holly told WTVD.
Zuri Jimenez hit a different wall: she could not move money from her bank account into Apple Pay. "I have been trying to transfer money from my bank to Apple Pay," Jimenez said. "There's an issue with it."
Her workaround attempts failed. The transfer simply would not complete, and no error explanation arrived. That gap — a failed payment with no diagnosis — is what pushed customers from inconvenience into worry.
Why does this feel familiar?
The timing is the uncomfortable part. This banking disruption landed within five days of two other high-profile infrastructure failures:
- A major Microsoft outage that knocked services offline
- Aviation interruptions that disrupted airline operations
- Monday's multi-bank service failures
No connection between the three incidents has been established. Investigators and the banks themselves have drawn no link. Still, the cluster has done the damage clusters do: it has customers questioning how dependable the systems underpinning daily life really are.
What does it mean for infrastructure trust?
Jimenez voiced what many apparently felt. "I am a little bit concerned," she said. "The airlines, it was really shocking, to be honest ... it surprised me, I've never seen anything like that."
Her reaction tracks a pattern familiar from incident research: a single outage annoys people, but rapid sequences of outages across different sectors erode confidence. Payments sit near the top of that anxiety list, because a stalled bank transfer can cascade into missed bills, failed purchases and awkward personal obligations.
For the banks, the reputational exposure is asymmetric. Chase moved quickly to state the issue was technical, not a breach — language designed to prevent customers from assuming the worst. That phrasing signals the bank understood the risk: in the absence of information, customers often default to fears about hacking or stolen funds.
When will services return?
That remains the open question. Chase has not said when all services will be fully restored, and as of the latest reports, the situation was still unresolved. What is clear:
- Account access and funds remain available, per Chase's statement
- Some transactions are completing, just slowly
- ATMs dispensed cash for at least some affected customers
- The cause is technical, with no cyber component, according to the bank
For customers mid-transfer, the practical advice embedded in the bank's statement is patience: transactions are delayed, not lost. The bank says money is accessible, even if it is moving slower than anyone would like.
The broader test comes next. Three infrastructure stumbles in five days — cloud, aviation, banking — have put reliability questions in front of customers who rarely asked them before. How quickly Chase and its peers restore full service, and how transparently they explain what failed, will shape whether that concern fades by the weekend or lingers far longer.
via abc11.com (Source)
More from Priya Raman
Show full bio
Senior reporter covering technology and product news in corporate strategy and chief-executive leadership at CEO Frontier.
459 articles
Adjacent sheets
- Chase disruption slows bank transactions and some Zelle payments
- Chase, Bank of America and Wells Fargo Hit by Widespread Outages
- Chase Draws 4,000+ Reports in U.S. Banking Disruptions
- Thousands report Wells Fargo outage in second weekly disruption
- Chase complaints surge past 20,000 as bank outages spread