Chase, Bank of America and other US banks hit by outages on 16 November
Customers of several large US banks could not log in or move money on Monday, and Chase said the fault was a technical bug rather than a cyberattack.
By Mr Elite Published 6 min read
- Severity
- Medium
- Status
- Reported by outlets
- Sources
- 1
- Last checked
The short version
- CBS News reported outages at JPMorgan Chase, Bank of America, U.S. Bank, Wells Fargo, Capital One and Truist on Monday 16 November.
- Downdetector had nearly 4,800 reports about Chase alone by 2 p.m. Eastern Time, according to Security Affairs.
- A Chase spokesperson said the problem was a technical bug, not a cyber issue.
- Zelle said its network was running normally and pointed to possible problems at participating institutions.
- The available information does not link the outages to a cyberattack or to other recent technology failures.
What happened
Several major US banks suffered service disruptions on Monday 16 November, leaving customers unable to use online banking, check balances or complete transactions, Security Affairs reported. It drew on CBS News, which cited the outage tracker Downdetector.
CBS News named JPMorgan Chase, Bank of America, U.S. Bank, Wells Fargo, Capital One and Truist among the affected institutions. Reports began on Monday morning and rose through the day. By 2 p.m. Eastern Time, Downdetector had received nearly 4,800 reports about Chase, the highest of any bank.
Customers described trouble logging in, checking balances, transferring money and sending wires. Bank of America customers also reported ATM problems, and U.S. Bank users had trouble with online banking and its mobile app. Some Wells Fargo customers could not log in or see transaction details.
The effects reached physical branches. A Chase customer in Texas told CBS News he could not deposit a check at a Dallas branch because the bank's system was unavailable.
A Chase spokesperson said, according to CBS News, that the bank was dealing with a technical bug and not a cyber issue. The bank said some transactions were slower than usual, that customers could still reach their accounts and funds, and that it was working on a fix.
Customers also reported problems sending and receiving money through Zelle. The company said its network was operating normally and suggested the trouble lay with participating financial institutions.
Why it happened
No root cause has been published. The only explanation on record is the Chase spokesperson's statement, relayed by CBS News, that the issue was a technical bug and not a cyber issue.
The other banks named have not been reported as giving a cause. Security Affairs said the available information does not establish a link between the banking outages and any coordinated cyberattack, and it does not establish a link to the other incidents that week.
Microsoft attributed its 12 November outage to a technical problem rather than malicious activity, Security Affairs reported. That is a separate company and a separate incident.
How this kind of failure works
Large banks run on long chains of dependent systems: login services, core ledgers, payment networks, ATM switches and the mobile apps that sit on top. If one link in that chain fails or slows, every service that calls it can fail too, even when each bank's own software is working.
Picture a shopping centre where every shop takes card payments through one shared terminal network. If that network drops, each shop is open and stocked, yet none can sell. A bank outage can look much the same from the customer's side.
Zelle shows this pattern. It does not hold accounts or funds. Participating banks and credit unions do, and the network operator, Early Warning Services, is owned by several large banks, Security Affairs reported. A Zelle payment can therefore fail because of a problem at either end.
Software bugs, bad configuration changes and capacity problems cause many outages with no attacker involved. An attack such as a denial-of-service flood, which swamps a service with traffic, can produce the same symptoms. For that reason, banks and outside analysts usually rely on internal logs and later incident reviews, not the symptoms alone, to tell the two apart.
Who is affected
Customers of the named banks who tried to use online banking, mobile apps, ATMs, wires or Zelle on Monday could be affected. Reports varied by bank, and Security Affairs did not say how many customers were hit or how long each bank's problems lasted.
You can tell whether you were affected by checking for failed or delayed transfers, missing or pending deposits, and any Zelle payment that did not complete. Chase said customers could still reach their accounts and funds.
Nothing reported suggests stolen data or money, and no bank has said customer information was exposed. The practical effect described so far is delay and inconvenience, with some people unable to deposit a check or move money when they needed to.
How to defend against it
Tick each step as you check it. Your progress is saved on this device.
What to learn from this
The concept: Availability as a security property
Security is often described by three goals: keeping data confidential, keeping it accurate, and keeping services available. An outage with no attacker still fails the third goal, and the harm to customers can be the same.
The same logic applies to cloud providers, DNS services and payment networks. When many organisations depend on one shared service, a single fault spreads, which is why dependency mapping matters.
A service that cannot be reached has failed its users, whatever the cause, so plan for failure as well as attack.
Quick check
Sign in to earn 10 XP for a right answer
Why can a problem at one participating bank disrupt Zelle payments even if Zelle's own network is running normally?
Zelle does not hold accounts or funds. Participating institutions do, so a failure at either end of a payment can stop it.
Timeline
- 12 November Microsoft 365 suffers a widespread outage affecting Outlook and Teams; Microsoft cites a technical problem.
- 13 November An FAA communications failure triggers a nationwide ground stop; Workday also reports disruptions.
- 16 November, morning Customer reports of bank problems begin appearing on Downdetector.
- 16 November, 2 p.m. ET Downdetector has nearly 4,800 reports about Chase alone.
- 16 November A Chase spokesperson says the cause is a technical bug, not a cyber issue.
What is not known yet
- The root cause of the outages at each bank has not been published.
- It is not yet clear whether the banking problems share a cause or are separate failures.
- The total number of affected customers and the time of full restoration have not been reported.
- Whether the earlier Microsoft, FAA and Workday incidents are connected has not been established.
Questions people ask
Were the US bank outages on 16 November a cyberattack?
Chase's spokesperson said the problem was a technical bug and not a cyber issue, according to CBS News. Security Affairs said there was no evidence of a coordinated cyberattack. No other bank has published a cause, so the position may change.
Which banks were affected by the outages?
CBS News named JPMorgan Chase, Bank of America, U.S. Bank, Wells Fargo, Capital One and Truist. Chase drew the most Downdetector reports, nearly 4,800 by 2 p.m. Eastern Time. Zelle users also reported problems.
Was my money safe during the outage?
Chase said customers could still reach their accounts and funds, though some transactions ran slowly. No bank has reported lost money or exposed data. Check your transaction history, and contact your bank through official channels if something looks wrong.
Is the bank outage linked to the Microsoft and FAA failures?
Security Affairs said the available information does not establish a connection between the incidents. Microsoft blamed a technical problem for its 12 November outage. The FAA ground stop happened on 13 November and Workday had disruptions the same day.
Sources
- Security Affairs: U.S. Banks Struggle With Outages Amid Wider Technology Disruptions