CrowdStrike’s August 4, 2024 reply apologized for the July 19 Falcon outage but firmly rejected Delta’s allegations of gross negligence and willful misconduct. It said its testing and validation were adequate, described rapid offers of assistance, challenged Delta’s account of the recovery, and argued that the parties’ contract limited ordinary liability to the single-digit millions.
The timeline behind the dispute
- July 19, 2024: A CrowdStrike Falcon sensor content update triggered a Windows-related outage later identified in litigation as the Channel File 291 incident.
- July 29, 2024: Delta’s counsel, David Boies, sent a letter alleging gross negligence or willful misconduct. The letter said the update had not been adequately stress-tested and threatened litigation.
- August 4, 2024: Michael B. Carlinsky of Quinn Emanuel replied for CrowdStrike, combining an apology with a detailed rejection of Delta’s allegations.
- August 8, 2024: Delta disclosed the operational and financial impact in an SEC Form 8-K.
- October 25, 2024: CrowdStrike filed a federal declaratory-judgment complaint seeking enforcement of the contract’s liability limits and a ruling that it had not acted with gross negligence or willful misconduct.
What CrowdStrike said in its August 4 response
An apology, but not an admission of legal fault
The letter opened with an apology to Delta, its employees and its customers. Carlinsky wrote: “CrowdStrike reiterates its apology to Delta, its employees, and its customers.” The same letter, however, “strongly rejects” the accusations of gross negligence and willful misconduct. In other words, CrowdStrike acknowledged the harm caused by the outage without conceding the legal standards Delta was asserting.
Testing and validation
CrowdStrike said Delta’s claim that the update bypassed adequate testing was contradicted by CrowdStrike’s Preliminary Post Incident Review. Its position was that testing and validation had occurred, so the July 19 failure should not be characterized as a deliberate or recklessly indifferent release.
Offers of assistance
The response said CrowdStrike contacted Delta within hours of the incident. It also said CrowdStrike’s chief executive offered onsite assistance, but that Delta neither responded to nor needed those onsite resources, according to CrowdStrike’s account.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
The dispute over recovery
CrowdStrike argued that Delta’s public litigation threat presented a misleading account of responsibility for Delta’s information-technology decisions and recovery. The letter pointed to Delta’s own response process and infrastructure resiliency choices as reasons its operations took longer to normalize. That is CrowdStrike’s litigation position, not an independent finding about why the recovery lasted as long as it did.
Contract limits and preservation of evidence
The response asserted that any CrowdStrike liability was contractually capped at an amount in the single-digit millions. It also asked Delta to preserve relevant records in anticipation of litigation, signaling that the exchange had moved beyond a customer-service dispute into a formal legal controversy.
Rank #2
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- Comprehensive Coverage: This BookFactory log book includes essential fields such as post/shift, time of change, date, weather conditions, and a designated space for detailed notes. This ensures that all relevant information is captured and easily accessible.
- Sturdy Cover: The trans-lux cover protects the log book from wear and tear, ensuring its longevity and maintaining the integrity of your recorded data.
- Essential Security Tool: This log book is an indispensable tool for any organization that values security and accountability. It helps to prevent misunderstandings, improve communication, and ensure a smooth transition between shifts.
- Wire-O with Trans-lux cover, 100 Pages, Dimensions 8.5" x 11" - (Security-Pass-Down) Reorder SKU: LOG-100-7CW-PP(Security-Pass-Down)
What Delta alleged and how much it said it was seeking
Delta’s July 29 letter treated the release process as potentially grossly negligent or willful, rather than as an ordinary software failure. Delta’s August 8 SEC filing then described the business consequences and said it was pursuing at least $500 million from CrowdStrike and Microsoft.
| Item | Delta’s disclosed figure | Qualification |
|---|---|---|
| Flight cancellations | Approximately 7,000 | Over five days, according to Delta’s August 8, 2024 SEC filing |
| Total damages sought | At least $500 million | Delta’s claim against CrowdStrike and Microsoft; a company disclosure, not a court award |
| Estimated direct revenue impact | $380 million | Delta’s estimate in the same filing |
| Estimated non-fuel expense | $170 million | Delta’s estimate in the same filing |
Delta CEO Ed Bastian described the disruption as unacceptable and said customers and employees deserved better. The figures above were Delta’s estimates and claimed losses; they did not establish that CrowdStrike legally owed those amounts.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Mastering Microsoft Endpoint Manager: Deploy and manage Windows 10, Windows 11, and Windows 365 on both physical and cloud PCs
- ABIS BOOK
- Packt Publishing
Did CrowdStrike admit fault for the Delta outage?
It admitted the outage occurred and apologized for its effects, but the August 4 letter did not admit gross negligence, willful misconduct or an obligation to pay Delta’s claimed damages. CrowdStrike’s wording separated responsibility for the incident’s consequences from the legal question of whether its conduct met either heightened fault standard.
Why did CrowdStrike say Delta took longer to recover?
CrowdStrike’s explanation had two parts: it said it reached out within hours and offered executive-level, onsite help; and it said Delta’s own operational decisions, recovery procedures and IT resiliency affected the length of the disruption. The letter therefore framed the disagreement as not only a question of how the faulty content update was released, but also of how each company responded afterward. Delta’s letter and filing presented a different account, and the cited documents do not resolve the factual dispute.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the CrowdStrike–Delta contract said about damages
CrowdStrike’s later complaint quoted the June 30, 2022 Subscription Services Agreement. The provisions it cited create a substantial gap between Delta’s claimed losses and the amount CrowdStrike said could ordinarily be recovered.
| Provision | Effect described in the complaint |
|---|---|
| Section 9.1 | Each party’s liability cannot exceed two times the fees paid for the relevant subscription term. |
| Section 9.2 | Indirect, incidental, punitive and consequential damages are excluded, including lost revenues, profits and goodwill. |
| Section 9.3 | The limits do not apply to liability arising from gross negligence or willful misconduct. |
The August 4 letter characterized the resulting ordinary-liability ceiling as being in the single-digit millions, but the documents cited here do not state the subscription fees needed to calculate an exact dollar cap. The exception is central: if a court found gross negligence or willful misconduct, the contractual limits described above would not apply under Section 9.3.
Where the dispute stood procedurally
The August 4 letter was a response to a threatened claim, Delta’s August 8 filing was a public company disclosure and damage estimate, and CrowdStrike’s October 25 complaint was a pleading asking a federal court to enforce the contract and reject Delta’s heightened-fault theory. None of those documents is a final merits ruling, and the materials identified here do not establish a settlement or a final allocation of responsibility.
What the response means
CrowdStrike’s position was deliberately dual-track: it expressed regret for a serious outage while contesting the legal characterization of its conduct, the cause of Delta’s prolonged recovery and the scale of damages Delta sought. Delta’s disclosed losses and CrowdStrike’s proposed contractual cap could not both control without resolving the factual and contractual issues in litigation. The August 4 letter stated CrowdStrike’s defense; it did not decide the case.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
