Skip to content
Research essay

The switch stays at the top

When a platform fails, the bill travels down to the people built on it. The control does not travel with it, and the platform decides where the line between them runs.

· 4 min read

Before July 2024, a company running CrowdStrike's Falcon security software could decide which version of the program its computers ran.1 It could keep its fleet on the latest release, or one or two versions behind, and in CrowdStrike's own words customers had "complete control over the deployment of the sensor."1 A second stream of updates came from CrowdStrike's cloud: "Rapid Response Content", configuration data that tells the sensor what to look for.1 That stream arrived on CrowdStrike's schedule.1 On 19 July at 04:09 UTC it carried a file that crashed Windows.1

The control a customer is given is real, and it stops where the platform says it stops. A customer can do everything right inside its own boundary and still be hit through the part the platform kept. Then the cost of the failure moves down, layer by layer, to whoever is closest to the damage, and the switch that caused it stays where it was.

A new type of detection template expected 21 input fields; the code that fed it supplied 20; a bug in the validator let the bad file through, and the sensor read past the end of its data inside the Windows kernel.2 The file was reverted at 05:27 UTC, 78 minutes later.1 Microsoft estimated that 8.5 million Windows devices were affected, less than one percent of all Windows machines.3

For the sensor itself, the company ran automated tests, internal use, early adopters and then general release, with customers choosing which version each part of their fleet ran.1 It described the content stream as configuration, "not code or a kernel driver", there to keep the sensor current with a rapidly evolving threat landscape without changes to kernel code.2 Under that label it travelled outside the customer's gates. The distinction was the company's to draw, and it decided what each customer's careful update policy actually governed.

The costs that followed were estimated, not audited, and they point one way. The insurer Parametrix put the direct loss to US Fortune 500 companies alone at about $5.4 billion.4 Brokers and modellers expected the vast majority of the damage to go uninsured.4 Delta's chief executive put the airline's own cost at $500 million.4 Delta cancelled about 7,000 flights.5

CrowdStrike's side of the ledger was smaller. It expected to give customers about $60 million of incentives in the second half of its fiscal year, and cut its revenue forecast accordingly.6 After a court ruling in May 2025, CrowdStrike's outside counsel said he expected the worst case to be damages capped under its contract with Delta, in the single-digit millions of dollars.5 That ruling, by a Georgia judge, had cut some of Delta's fraud claims and let the rest of its case go forward.5 As of January 2026 the case was still going on, with no trial date set.7

The shape is a common one. Amazon's published compute agreement, to take one example, commits to 99.99% availability in a region and, if it falls short, offers a credit of 10%, 30% or 100% of that month's bill for the affected service.8 The credit goes against future payments and does not entitle the customer to "any refund or other payment".8 Unless the customer's wider agreement says otherwise, the credit is its "sole and exclusive" remedy.8 The platform's exposure is measured in what it charged, and the customer's loss is measured in what it does. The party best placed to prevent a bad update is the one that writes it, and that is the party the terms protect.

The cost does not stop at the first customer. Passengers stranded by Delta's cancellations sued Delta, and a federal judge let parts of their class action proceed, including claims over refunds.5 Passengers who sued CrowdStrike directly lost in June 2025, when a federal judge in Texas held their claims preempted by the Airline Deregulation Act because the harm was tied to airline services.9 Each layer answers to the layer beneath it, under its own contract, and none of them can reach the switch.

Some of the bill was probably Delta's own. American and United were back to near-normal within three days; Delta took five, and on each of the first three days it cancelled more than 1,000 flights while its rivals cancelled a few hundred.5 CrowdStrike and Microsoft both said Delta turned down or ignored offers of help, which Delta disputed.5 That is a fair reason to doubt that every dollar of Delta's $500 million is CrowdStrike's. It does not change who held the switch.

Besides better testing and a canary rollout, CrowdStrike's repairs included a change to the platform so that "customers can choose where and when Rapid Response Content updates are deployed."2 The fix moved part of the switch to the people who had been paying for it. Any business built on someone else's platform can ask for the same thing before a failure: a list of every kind of change the vendor can make, and which of them the business is allowed to hold back.

Delta's lawsuit claims something stronger: that it had configured its systems to refuse automatic updates and the content arrived anyway.10 CrowdStrike answers that its 2022 agreement with Delta gave it the access it needed to provide the service.10 The judge, reading the pleadings in the light most favourable to Delta, reasoned that an update delivered against a customer's opt-out may be considered unauthorized, and let Delta's computer trespass claims proceed.10 That is an allegation, and if it is proved it changes the case from a customer who did not control a channel to a customer whose control was overridden.

Europe has rewritten product liability around this point. A directive adopted in October 2024 makes software a product, and says a product stays within its manufacturer's control for as long as the manufacturer can supply updates.11 Liability to an injured person cannot be limited by contract.11 Its protection is for natural persons, though: damage to property used only for professional purposes, and the loss of professional data, are outside it, and it covers products placed on the market after 9 December 2026.11 The law now follows the switch for a private user's laptop, and leaves an airline to its contract.

Sources

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11

About this piece

Kind
Research essay. An argument grounded in published research.
Evidence
Moderate
Research
Standard, 11 sources
Made
My idea. AI researched and wrote it, and an AI model checked each sourced claim against its source before I published it here.
Updated
Nov 21, 2026

How this was made →Write to me about it →

platformsaccountabilitygovernance