JPMorganChase software bug in on-premise hardware disrupts US banks and Zelle payments on Nov 16; no evidence of cyberattack
Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 2 fontes trouxeram em 17/11/2026 00:05; os links antigos trazem para cá.
Fontes: wired.com ↗ securityaffairs.com ↗
On Monday, 16 November 2026, customers of several large US financial institutions reported login failures, missing balances and failed transfers, wires and Zelle payments. Named as affected were JPMorganChase, Bank of America, Wells Fargo, Capital One, Truist and U.S. Bank (securityaffairs.com). JPMorganChase attributed the problem to a software bug in on-premise hardware systems and said there is no evidence it is cyber-related (wired.com). The bank also said it is not a "systemic issue" and that customers still have access to their accounts and funds (wired.com). Zelle said its network was operating normally and that payments to or from affected banks may be delayed (securityaffairs.com, wired.com). Neither source found evidence linking the outage to a coordinated attack, or to the same week's Microsoft 365 (12 Nov), FAA (13 Nov) or Workday (13 Nov) disruptions. No technical root cause beyond the bank's statement has been published, and the sources do not say whether service is fully restored.
Detalhes técnicos
- Reports began around 9:30 am ET and peaked around 2 pm ET (wired.com). By 2 p.m. ET, Downdetector had received nearly 4,800 reports about Chase alone (securityaffairs.com).
- The only stated cause is JPMorganChase's "software bug in on-premise hardware systems" (wired.com). One source describes it more generally as a technical bug rather than a cyber issue (securityaffairs.com).
- Other banks were affected only to the extent that they transacted with JPMorganChase (wired.com).
- Zelle, US Bank, Mastercard and Visa said their own systems were operating normally. Mastercard called its Downdetector listing "not correct" (wired.com).
- Downdetector relies on user reports, not official statements (wired.com).
- No IOCs, CVEs or threat actors have been reported by either source.
Remediação
No vendor or government remediation guidance has been issued. Securityaffairs.com recommends business continuity plans, dependency mapping, alternative communication channels, incident response procedures and clear customer communication. Wired.com offers no guidance.
Relatos divergentes
- Cause: securityaffairs.com cites a generic "technical bug" from a Chase spokesperson. Wired.com gives the more specific statement of a software bug in on-premise hardware, and it was published slightly later (21:45 UTC vs 21:38 UTC). Both agree there is no cyber evidence, and both rest on the bank's own statements rather than independent verification.
- Scope: securityaffairs.com lists U.S. Bank, Bank of America, Wells Fargo, Capital One and Truist as affected. Wired.com says U.S. Bank's own systems were operating normally and that other institutions were affected only through their dealings with JPMorganChase. It also cites the bank's claim that the issue is not systemic. Downdetector counts reflect user reports, not confirmed impact.
Linha do tempo
-
JPMorganChase software bug in on-premise hardware disrupts US banks and Zelle payments; no evidence of cyber cause
ler a análise desta fonte ocultar
On Monday, thousands of Downdetector reports described disruptions at many US financial institutions, including banks, credit unions, fintech apps and card companies. JPMorganChase attributed the problem to a software bug in on-premise hardware systems and said there is no evidence it is cyber-related. The bank said it is not a "systemic issue" and that customers still have access to their accounts and funds. Other banks were affected only to the extent that they transacted with JPMorganChase. Zelle, US Bank, Mastercard and Visa said their own systems were operating normally, although Zelle payments to or from affected banks may be delayed. The article notes that Downdetector relies on user reports, not official statements, and that Mastercard called its listing "not correct". The article also recalls a recent Microsoft 365 outage and an FAA ground stop, but it offers no evidence that these events are linked to the banking issue.
Technical Details
- Reports began around 9:30 am ET and peaked around 2 pm ET.
- The cause stated by JPMorganChase is a software bug in on-premise hardware. The article does not identify an attacker, a CVE or any IOCs.
-
Widespread U.S. bank outages on Nov 16 hit Chase, BofA, Wells Fargo and Zelle; Chase cites technical bug, not cyberattack
ler a análise desta fonte ocultar
On Monday, 16 November, several major U.S. banks suffered service disruptions. The affected institutions included JPMorgan Chase, Bank of America, U.S. Bank, Wells Fargo, Capital One and Truist. Customers could not log in, check balances, transfer money or complete wires, and Zelle payments were also affected. By 2 p.m. ET, Downdetector had received nearly 4,800 reports about Chase alone. A Chase spokesperson attributed the problem to a technical bug rather than a cyber issue. Zelle said its network was operating normally and pointed to possible problems at participating institutions. The article says no evidence links the outages to a coordinated cyberattack or to the Microsoft 365 (12 Nov), FAA (13 Nov) or Workday (13 Nov) disruptions of the same week. No independent research was performed, so this record relies on the article alone.
Technical Details
No root cause has been published. Chase described a technical bug. The article reports no IOCs, CVEs or threat actors.
Remediation
The article recommends business continuity plans, dependency mapping, alternative communication channels, incident response procedures and clear customer communication.