Date
July 19, 2024
Location
United States
Industry
Transportation
Access vector
Not applicable
OT targeting
Unknown
Primary peril
None
Impact duration
5 days

Delta Air Lines CrowdStrike outage, July 2024

DeNexusIncident analysis
Cover image for the incident analysis: Delta Air Lines CrowdStrike outage, July 2024

The incident path, stage by stage

Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.

Scroll sideways to see every stage.

    IT stagesOT stagesConfirmedPerilReportedImpliedUnknownNot in pathLink not established DeNexus analysis of public sources, as of October 22, 2026
    On this page

      Highlights

        What happened. On July 19, 2024, a faulty content update to CrowdStrike’s Falcon security software crashed Windows computers worldwide; Microsoft estimated that 8.5 million devices were affected[1][2]. Delta Air Lines cancelled about 7,000 flights over five days and puts its damages at at least $500 million[3].

        Why it matters. There was no attacker: the failure came from inside a trusted vendor’s update channel. The same defect hit other US airlines, but disruption lasted longer at Delta, whose crew-tracking tool could not keep up[4][5].

        About this analysis. This analysis sets out what is known, stage by stage. Delta’s lawsuit against CrowdStrike is still open, and the court order in it is described through press reports. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.

        Highlights

        • CrowdStrike’s root-cause analysis says the update’s template defined 21 input fields while the sensor supplied 20, causing an out-of-bounds memory read and a crash; testing had used a wildcard for the 21st input[1].
        • Delta’s CEO said the airline had to manually reset 40,000 servers, and that a crew-tracking tool used to pair pilots and flight attendants with flights was disrupted[5].
        • Delta reported a $380 million revenue impact and $170 million of non-fuel expense, partly offset by $50 million less fuel, and sued CrowdStrike, which says its contract limits liability to twice the fees paid[3][6][7].
        • The US Department of Transportation investigated Delta’s treatment of passengers and closed the probe without penalty[8].

        Attack flow

        • Updated: 2026-10-22
        • Intent: Accidental [confirmed | vendor software defect]
        • Threat actors: Not applicable [not in path | Accidental event, no attacker]
        • Access vector: Not applicable [not in path | No attacker, no intrusion]
        • IT impact: System Outage [confirmed | Windows hosts crashed]
        • OT targeting: Not classified [unknown | No attacker; targeting not assessed]
        • OT sophistication: Not applicable [not in path | Accidental event]
        • OT impact: Loss / Denial of Control [confirmed | of flight operations, no control system]
        • Perils: No Perils [confirmed | No physical event]
        • Financial losses: Business Interruption [confirmed | $500M+]; Cyber Incident Response [confirmed | 40,000 servers reset]; Cyber-Physical Incident Response [confirmed | DOT probe]; Reputation Damage [implied]

        What happened

        On July 19, CrowdStrike deployed two new IPC Template Instances to its Falcon sensor in a Rapid Response Content update, Channel File 291. The sensor runs with kernel-level access on Windows. Matching against the new instances read past the end of the sensor’s input array and crashed the system[1]. Microsoft estimated that 8.5 million Windows devices were affected[2].

        Delta was hit harder and for longer than many other US airlines[4]. CEO Ed Bastian said Delta was “by far the heaviest in the industry” in its use of CrowdStrike and Microsoft, that the airline had to reset 40,000 servers by hand, and that its crew-tracking tool, “a mission critical tool used to pair pilots and flight attendants with flights”, was disrupted[5]. Delta reported about 7,000 cancellations over five days[3]; United cancelled about 1,500 flights in the same outage[9]. Reuters reported 1.3 million Delta customers affected[6], CNBC reported more than 176,000 refund or reimbursement requests[10], and a DOT spokesperson reported more than 5,000 complaints about Delta in the first week[11].

        The DOT opened an investigation into Delta’s treatment of passengers on July 23, 2024[12]. On October 25, 2024, Delta sued CrowdStrike in Fulton County Superior Court, and CrowdStrike sued Delta the same day in federal court, asking for a declaration that their contract limits its liability[6][7]. In an order filed May 16, 2025, a Georgia judge let Delta’s gross-negligence and computer-trespass claims proceed[13]. The DOT decided around November 2025 to close its probe without penalty and announced the closure on June 15, 2026[8]. As of June 2026, both lawsuits were pending[9].

        Intent: accidental

        No attacker or malicious act is documented. The cause was a defect in CrowdStrike’s own update: the IPC Template Type defined 21 input parameter fields, but the sensor’s integration code supplied only 20 input values, and tests had used wildcard matching for the 21st, so the fault was not exposed[1]. CrowdStrike says this content is “separate and distinct from CrowdStrike’s on-sensor AI”[1]; the error was a mismatch in a written template, not a model’s output.

        Delta’s lawsuit uses the words “computer trespass”, but that is a legal claim about an authorized vendor’s update channel, not evidence of an intrusion[14].

        Threat actors: none

        There was no threat actor. The same defect crashed machines at organizations worldwide, not only at Delta[2]. No one has claimed an attack or been blamed for one, because none took place. The stage is marked Not applicable, and no actor is highlighted on the map.

        Access vector: none

        Nothing was breached. The faulty file arrived through CrowdStrike’s normal Rapid Response Content channel[1], which the vendor delivers outside the customer’s own patch process. Delta alleges that CrowdStrike “circumvented the very testing and certification processes it advertised”[15], and its computer-trespass claim rests on an alleged unauthorized backdoor[14]. Those are allegations in a pending lawsuit, not findings. The stage is marked Not applicable.

        IT impact: Windows machines crashed

        The defective channel file crashed Windows computers on every reboot until it was removed by hand[1]. At Delta, recovery meant manually resetting 40,000 servers, according to its CEO[5]. Machines were recovered in place, not replaced or rebuilt, and no data was accessed or taken: the failure affected availability only.

        A Microsoft spokesperson pointed to a 2009 undertaking to the European Commission, which gave security-software makers the same level of Windows access as Microsoft’s own security tools, as one reason the Windows kernel is less locked down than the kernel in current Apple Mac systems[16].

        OT targeting: not classified

        No aircraft or control system was implicated: Windows servers and workstations crashed[3][1]. The operational damage came through IT that the airline depends on, chiefly the crew-tracking tool[5]. Because there was no attacker, there was no targeting in the usual sense, and this stage is left unclassified. It is shown as unknown.

        OT sophistication: not applicable

        With no attacker and no control system affected, there is no OT technique to rate. The defect was a mismatch in a vendor’s content file, not adversary tradecraft[1]. The stage is marked Not applicable.

        OT impact: an airline that lost control of its operation

        What Delta lost was control of its own operation, not of any industrial control system. Its crew-tracking tool could not keep up, and the airline ran a degraded operation for five days[5][3]. A law-firm alert on the DOT closure counts more than 10,000 delays over those five days[17]. Peer airlines hit by the same defect recovered sooner: United cancelled about 1,500 flights, against Delta’s 7,000[9][3]. The map shows Loss / Denial of Control as confirmed in that operational sense. No aircraft system, baggage-system controller or ground-equipment controller is described as affected.

        Perils: no physical event

        There was no physical event. A faulty software update crashed Windows computers; nothing was damaged, released or set moving, and aircraft systems were not involved[1][3]. No fatality, injury or physical damage is documented.

        The point of failure sat inside a trusted vendor’s release process, beyond the reach of the airline’s own controls.

        Financial losses: what it cost

        Delta’s 8-K says its damages from the outage “total at least $500 million”. For the September quarter, it gives a revenue impact estimated at $380 million, “primarily driven by refunding customers for cancelled flights and providing customer compensation in the form of cash and SkyMiles”; $170 million of non-fuel expense, mainly customer expense reimbursements and crew-related costs; and fuel expense $50 million lower because of the cancellations[3]. Delta’s third-quarter results confirmed the $380 million and $170 million and put the hit at 45 cents per share[18]. The $500 million is net of the fuel saving[19]. Bastian gave the same figure: “Half a billion dollars in five days”[5].

        Loss evidence

        • Confirmed: Lost revenue, refunds and compensation; Contingent business interruption (a vendor’s defect); Network event response and recovery (servers reset by hand); Regulatory investigation (closed without penalty); Third-party societal impact (about 7,000 flights cancelled, 1.3 million customers affected)
        • Reported amounts: $500M Damages from the outage, stated as a floor, according to Delta’s 8-K[3]; $380M September-quarter revenue impact, mostly refunds and compensation, according to Delta[3][18]; $170M Non-fuel expense, mostly customer reimbursements and crew costs, according to Delta[3][18]; $50M Lower fuel expense from the cancellations, netted against the two costs, according to Delta[3]
        • Implied: Manual operations and workarounds; Customer retention spending (cash and SkyMiles compensation)
        • Not supported: Recovery from CrowdStrike (a claim, not a recovery); Ransom or extortion; Market valuation; Personal data breach response; Server, computer, network or embedded device replacement

        Nothing has been recovered. Delta sued for “over $500 million in out-of-pocket losses” plus lost profits, fees and punitive damages[6]. CrowdStrike says the 2022 contract limits liability to “two (2) times the value of the fees paid” and excludes consequential damages[7], and its counsel puts the worst case in the “single-digit millions”[13]. Passengers sued too: in May 2025 a federal judge let parts of a nine-plaintiff class action proceed[4]. Neither case has produced a figure.

        What this incident shows

        The same defect hit several airlines, and the one whose critical scheduling system had the weaker fallback had the longer, costlier outage: Delta cancelled about 7,000 flights over five days, United about 1,500[3][9]. Delta’s CEO named the disrupted crew-tracking tool as the bottleneck[5].

        The cause sat outside Delta’s network. A security vendor’s kernel-level content update, delivered through its own channel, crashed machines regardless of what Delta did[1]. Who pays is being tested in court. If the contractual limit CrowdStrike relies on holds, its exposure would be in the single-digit millions, according to its counsel, against Delta’s claim of more than $500 million[7][13][6].

        References

        1. CrowdStrike. “External Technical Root Cause Analysis -- Channel File 291.” 6 Aug. 2024. crowdstrike.com/wp-content/uploads/2024/08/Channel-File-291-Incident-Root-Cause-Analysis-08.06.2024.pdf
        2. “Microsoft says 8.5M Windows devices were affected by CrowdStrike outage.” TechCrunch, 20 July 2024. techcrunch.com/2024/07/20/microsoft-says-8-5m-windows-devices-were-affected-by-crowdstrike-outage/
        3. Delta Air Lines. Form 8-K (Item 7.01). U.S. Securities and Exchange Commission, 8 Aug. 2024. sec.gov/Archives/edgar/data/27904/000168316824005369/delta_8k.htm
        4. Reuters. “Delta must face passenger lawsuit over massive computer outage.” 7 May 2025, as carried by Business Insurance. businessinsurance.com/delta-must-face-passenger-lawsuit-over-massive-computer-outage/
        5. “Delta’s CEO says the CrowdStrike outage cost the airline $500 million in 5 days.” NPR, 31 July 2024. npr.org/2024/07/31/nx-s1-5058652/delta-crowdstrike-outage-500-million-dollars
        6. Reuters. “Delta sues CrowdStrike over software update that prompted mass flight disruptions.” 28 Oct. 2024, as carried by Business Insurance. businessinsurance.com/delta-sues-crowdstrike-over-software-update-that-prompted-mass-flight-disruptions/
        7. U.S. District Court for the Northern District of Georgia. “CrowdStrike, Inc. v. Delta Air Lines, Inc.” Complaint for declaratory judgment, No. 1:24-cv-04904, 25 Oct. 2024. storage.courtlistener.com/recap/gov.uscourts.gand.335602/gov.uscourts.gand.335602.1.0.pdf
        8. Shepardson, David (Reuters). “US closes probe into 2024 Delta Air Lines meltdown sparked by CrowdStrike outage.” GV Wire, 15 June 2026. gvwire.com/2026/06/15/us-closes-probe-into-2024-delta-air-lines-meltdown-sparked-by-crowdstrike-outage/
        9. “DOT drops investigation of Delta for CrowdStrike outage.” The Atlanta Journal-Constitution, June 2026. feeds.ajc.com/business/2026/06/dot-drops-investigation-of-delta-for-crowdstrike-outage/
        10. Bartlett, Katie (CNBC). “CrowdStrike shares plunge 11% to lowest level of the year on report that Delta may seek damages.” 29 July 2024, as carried by NBC Miami. nbcmiami.com/news/business/money-report/crowdstrike-shares-plunge-11-to-lowest-level-of-the-year-on-report-that-delta-may-seek-damages/3375953/
        11. Angel, Greg. “Thousands file complaints after Delta Airlines cancellation chaos.” Spectrum News, 25 July 2024. spectrumlocalnews.com/orlando/news/2024/07/25/delta-air-lines--dot--airline
        12. The Boston Globe. Report on the Department of Transportation investigation of Delta, 23 July 2024. bostonglobe.com/2024/07/23/business/delta-outage-dot-buttigieg-investigation
        13. “Judge allows Delta’s lawsuit against CrowdStrike to proceed with millions in damages on the line.” The Register, 21 May 2025. theregister.com/2025/05/21/judge_allows_deltas_lawsuit_against/
        14. “Judge Says Delta Can Sue Company Linked to 2024 Computer Outage.” AirlineGeeks, 21 May 2025. airlinegeeks.com/2025/05/21/judge-says-delta-can-sue-company-linked-to-2024-computer-outage/
        15. “Legal battle between Delta, CrowdStrike heats up with matching lawsuits over outage.” FOX 5 Atlanta, 29 Oct. 2024. fox5atlanta.com/news/delta-crowdstrike-lawsuits-tech-outage-canceled-flights
        16. Speed, Richard. Report on Microsoft’s EU explanation for Windows kernel access. The Register, 22 July 2024. theregister.com/2024/07/22/windows_crowdstrike_kernel_eu/
        17. Eckert Seamans. “DOT closes probe into Delta’s 2024 CrowdStrike-related meltdown.” Law-firm alert, 24 July 2026. eckertseamans.com/?p=26765
        18. Delta Air Lines. “Delta Air Lines Announces September Quarter 2024 Financial Results.” 10 Oct. 2024. ir.delta.com/news/news-details/2024/Delta-Air-Lines-Announces-September-Quarter-2024-Financial-Results/default.aspx
        19. Live and Let’s Fly. Report on Delta’s CrowdStrike lawsuit, 28 Oct. 2024. liveandletsfly.com/delta-crowdstrike-lawsuit/