Skip to content
Komposite News
Markets · Technology · Capital
Thursday, September 10, 2026Global EditionGot a tip?
Banking

Chase blames a bug, and the outage rule counts bugs

JPMorgan Chase says Monday's disruption to consumer transactions came from a software bug in its own on-premise hardware, not a cyberattack. The 2021 federal rule on bank incident notices covers outages from any cause, and gives banks 36 hours.

Komposite News Staff
November 17, 20266 min read
A single-storey Chase bank branch with a white portico and the Chase sign above the door, an empty car park with accessible bays in frontWhisperToMe, CC0, via Wikimedia Commons
A Chase branch on Montrose Boulevard in Houston, Texas, with an empty car park in front, in a file photograph from 2022.Photograph via Wikimedia Commons

JPMorgan Chase blamed a software bug in its own on-premise hardware for Monday's disruption to consumer transactions, which customers first reported at about 11:30 EST and which the bank said had cleared by about 18:30 EST.

The largest US bank said in a statement reported by CNBC that it had experienced a "temporary issue related to a software bug in on-premise hardware systems", that customers could still reach their accounts and funds, and that there was "no evidence it is cyber-related". "This is not a systemic issue," a spokesperson said. Transactions with other banks were delayed only where Chase was a party, the bank said. It has not said how many customers were affected or which system failed.

By about 18:30 a spokesperson told NBC News: "Transactions are now posting normally." Zelle, the payments network operated by Early Warning Services, said: "Zelle is not down. Zelle is operating as it should." U.S. Bank said it was "not directly impacted", PNC was "not experiencing any direct impact" and Capital One "has not been impacted", NBC reported. Bank of America and Citigroup reported no problems with their own services, the Associated Press reported, and some Chase customers saw a message that services were unavailable.

Komposite's timeline from the reports linked in each row. The last row is our arithmetic, not a known filing: the rule's 36 hours run from the moment a bank determines that an incident qualifies, which may be later than the first customer report, and Chase has not said whether or when it made that determination.
Time (EST)What happenedHours after first reports
11:30 Mon 16 NovEarliest customer reports of errors, according to CNBC0
About 16:00Chase posts on X that it is working to resolve a temporary issue, NBC News reported4.5
16:41CNBC publishes the bank's statement blaming a software bug in on-premise hardware5.2
About 18:30A spokesperson says "Transactions are now posting normally"7.0
23:30 Tue 17 NovLatest time the OCC could receive notice if Chase had judged at 11:30 on Monday that the outage was a notification incident36.0

Does an outage that is not a cyberattack have to be reported?

It can be. The test in federal banking rules turns on the effect of an incident, not on whether anyone attacked the bank. The computer-security incident notification rule adopted in November 2021 by the Office of the Comptroller of the Currency, the Federal Reserve and the Federal Deposit Insurance Corporation, in force since April 2022, defines a computer-security incident as "an occurrence that results in actual harm to the confidentiality, integrity, or availability of an information system". The agencies wrote that such incidents "can result from destructive malware or malicious software (cyberattacks), as well as non-malicious failure of hardware and software, personnel errors, and other causes". When two commenters asked them to exclude non-malicious causes, they declined: "For clarity, the definition includes incidents from whatever cause."

An incident becomes reportable, a "notification incident", when it has materially disrupted or degraded, or is reasonably likely to, a bank's ability "to deliver banking products and services to a material portion of its customer base, in the ordinary course of business", or a business line or operations whose failure would threaten financial stability. The agencies listed examples. Two sit close to Monday's facts: "A failed system upgrade or change that results in widespread user outages for customers and banking organization employees", and attacks that "disrupt customer account access for an extended period of time (e.g., more than 4 hours)". Whether Chase's bug met the materiality test is a judgment for the bank and its supervisors; Chase's own statement that customers kept access to their funds would weigh in that judgment.

The deadline is short. A bank "must notify" its primary federal regulator "as soon as possible and no later than 36 hours after the banking organization determines that a notification incident has occurred". For JPMorgan Chase Bank, N.A., a national bank, that regulator is the OCC; the Fed's version of the rule covers bank holding companies such as JPMorgan Chase & Co. The notice can be an email or a phone call, and "No specific information is required in the notification other than that a notification incident has occurred." Notices are covered by the agencies' confidentiality rules, so if Chase filed one, the public is unlikely to see it.

Banks argued for longer when the rule was drafted. Several commenters asked for 72 hours, to match New York's financial regulator and the EU's data-protection law, and one asked for five business days for banks under $20bn in assets. The agencies kept 36: "The agencies continue to believe that 36 hours is the appropriate timeframe, given the simplicity of the notification requirement and the severity of incidents captured by the definition of 'notification incident.'" They added that the clock starts only once a bank has determined that an incident qualifies, which leaves the bank time to assess what happened.

Komposite's close reading of the final rule, 86 FR 66424, set against the bank's statements as reported by CNBC, NBC News and the AP. The rule's examples are illustrative; each bank decides case by case.
What the 2021 rule looks atWhat the rule saysWhat Chase has said in public
CauseIncidents count "from whatever cause", including non-malicious hardware and software failureA software bug in on-premise hardware; "no evidence it is cyber-related"
Effect on customersMaterial disruption to services for "a material portion of its customer base"Some transactions slower; customers kept access to accounts and funds; numbers affected not given
DurationOne example cites account access disrupted for "more than 4 hours"Reports ran from about 11:30 to about 18:30 EST
DeadlineNo later than 36 hours after the bank determines the incident qualifiesNot said whether or when it made that determination
Public disclosureNone required; notices fall under supervisory confidentiality rulesStatements to the press and on X

How big is the operation that slowed?

Very. JPMorgan Chase held $2.78tn of deposits at 30 September, according to its filings with the SEC, up 8.7 per cent in nine months by our arithmetic. Its spending on technology has grown faster than its other costs. In the first nine months of 2026 the bank's technology, communications and equipment expense was $9.46bn, up 16.5 per cent on a year earlier, while total noninterest expense rose 13.7 per cent.

From the income statement in JPMorgan Chase's 10-Q for the quarter to 30 September 2026 (XBRL rendering). Changes and shares are Komposite's arithmetic.
JPMorgan Chase, $ millionsQ3 2025Q3 2026Nine months 2025Nine months 2026Change, nine months
Technology, communications and equipment expense2,8393,3358,1219,463+16.5%
Total noninterest expense24,28127,29571,65781,461+13.7%
Technology as a share of noninterest expense11.7%12.2%11.3%11.6%

The phrase "on-premise" places the fault in hardware the bank runs itself, rather than with a cloud provider or an outside processor. Chase has not elaborated. Its only Form 8-K on Tuesday, filed with the SEC, concerned the succession of its chief financial officer: Bregje de Best will succeed Jeremy Barnum after the bank reports first-quarter 2027 results, and Barnum will become a vice chairman. It does not mention Monday's outage.

Why it matters

The rule was written for exactly this kind of week. When it was adopted, the agencies estimated about 150 notification incidents a year across the banks they supervise, a figure based on supervisory data and suspicious-activity reports for 2019 and 2020. It also requires vendors that run services for banks to warn their bank customers when a disruption lasts four hours or more. Monday's outage came four days after a Microsoft gateway failure that Microsoft also traced to a latent software defect, and three days after an air traffic control outage that grounded US flights for several hours, the AP noted.

Chase has said its systems are back to normal. What it has not said, how many customers were hit, whether fees or failed payments will be reversed, and whether it judged the outage reportable, is the next thing to watch. Komposite reported in October on JPMorgan's deposit token moving onto Ethereum, part of the same bank's effort to run more of its payments on new rails.

MORE ON THIS STORY