Was the Chase Outage a Cyberattack? What We Know
JPMorgan Chase blamed Monday’s disruption on a software bug and said it was not cyber-related. Microsoft services and U.S. air traffic control also experienced outages days earlier, but reports have not established a connection between the incidents.
- Chase has not said what the bug affected or which component failed.
- Some transactions involving Chase were delayed. That does not mean other banks’ main services failed.
- The FAA disruption was tied to aging, overloaded equipment. Officials differed on whether newer additions played a role.
What happened at JPMorgan Chase?
Chase spokesman Joe Evangelisti described the disruption to The Associated Press as “a temporary issue related to a software bug in an on-premise hardware system” and said “it is not cyber-related.” The bank did not identify the software, equipment or service involved in its public comments cited in the reporting.
“On-premise” usually means technology hosted on an organization’s own infrastructure rather than in the cloud. The phrase does not say which component failed. And Chase’s explanation is the bank’s account, not a detailed, independent forensic finding.
The disruption also affected customers beyond Chase. AP reported that thousands of customers at several major banks and Zelle had trouble accessing accounts or completing transactions. Chase said the issue was limited to its own systems, while acknowledging that transactions with Chase could be delayed for customers at other institutions.
The distinction matters. A payment involving Chase can stall even when the other bank’s main services are working. Bank of America and Citigroup said their banking services were not affected. U.S. Bank said some Zelle payments involving another institution could be delayed, while Early Warning Services, which operates Zelle, said the network was fully operational.
Chase said it was working to restore services by the end of Monday. The available reporting does not say exactly how long the disruption lasted or whether the bank met that target.
How do the Microsoft and FAA outages fit in?
AP reported a major Microsoft outage on Thursday that affected Outlook, Teams and Copilot. The reporting available here does not specify its geographic scope, technical cause or exact duration.
On Friday, the Federal Aviation Administration issued a nationwide ground stop, a temporary order halting departures. The New York Times reported that nearly all departures were stopped for a time, although some international flights were allowed to leave. The disruption led to widespread delays and cancellations.
The Times reported that aging radar and telecommunications equipment, including old routers, became overloaded. Transportation Secretary Sean Duffy blamed antiquated equipment and rejected the claim that recent upgrades caused the failure. Markwayne Mullin said officials had seen “zero evidence” of a cyberattack, but suggested that technology added to the older system might have contributed to the overload. The review was still underway.
Those accounts do not provide a settled technical explanation. And a report that investigators had found no evidence of an attack at that point does not mean they had definitively ruled one out.
Were the outages connected?
Reports have not established a connection among the Chase, Microsoft and FAA incidents. Their close timing raises reasonable questions, but timing alone does not prove a shared cause, coordinated action or common vulnerability.
The incidents involved different systems and different reported problems: a software bug affecting a Chase system, an outage involving Microsoft services, and overloaded aviation communications equipment. Without technical evidence linking them, treating them as one event would turn coincidence into a conclusion.
The wider concern remains real. Banks, communications platforms and aviation systems rely on complex technology. Software defects or aging equipment can disrupt essential services without a cyberattack. When services fail, clear updates help people understand what is affected, what remains uncertain and what they should do. “Software bug” may be an accurate first explanation, but customers deserve more detail once the facts are available.
Key questions and answers
-
What caused the Chase disruption?
Chase attributed it to a temporary software bug in an on-premise hardware system. The bank has not released specific technical details.
-
Did Chase say it was a cyberattack?
No. Chase said the disruption was not cyber-related. The available reporting does not include an independent forensic account.
-
Did other banks’ systems fail?
Some customers had trouble accessing accounts or completing transactions, including payments involving Chase. That does not show that other banks’ own main services failed.
-
Were the Chase, Microsoft and FAA outages linked?
No link has been established. The incidents happened close together, but the available reporting does not point to a common cause.
The reported facts do not support calling the Chase disruption a cyberattack or connecting it to the Microsoft and FAA outages. The practical demand is straightforward: institutions should explain what failed, what customers may experience and what investigators are still looking into. Otherwise, people are left to fill the gaps with speculation.