Incident Database

The Most Expensive Tech Outages Ever

Updated June 2026 · 19 documented incidents with sourced cost estimates

Most Expensive (Sourced Estimates)

CrowdStrike Jul 2024

$5.4B+

Fortune 500 losses (Parametrix)

Meta Oct 2021

$100M+

Direct + $60B market cap loss

Change Healthcare 2024

$800M+

Reported by UnitedHealth

AWS us-east-1 Dec 2021

$150M+

7-hour networking outage

Toyota Feb 2022

$375M

Supplier cyberattack, 1-day halt

Delta (CrowdStrike cascade)

$500M

5 days of flight cancellations

Full Outage Database

IncidentDateDurationEst. CostCauseSource
CrowdStrike Falcon UpdateJul 2024~8 hours (recovery days-weeks)$5.4B+Faulty configuration updateParametrix 2024Details
Meta (Facebook) Global OutageOct 2021~6 hours$100M+ (+$60B mkt cap)BGP routing errorMeta disclosure
Delta Air Lines (CrowdStrike cascade)Jul 20245 days of cancellations$500M est.CrowdStrike-caused IT failureDelta disclosuresDetails
AWS us-east-1 OutageDec 2021~7 hours$150M+ est.Networking device issueAWS post-incidentDetails
AWS S3 us-east-1Feb 2017~4 hours$150M+ est.Operator error (too many servers removed)AWS post-incidentDetails
Cloudflare Nov 2025Nov 2025~3 hours (full restore ~6hr)$180-360M est.Oversized bot-management config file crashed proxiesCloudflare post-incident
AWS Oct 2025 (us-east-1)Oct 2025~15 hours$38-581M insured est.DynamoDB DNS race condition cascaded to EC2/LambdaAWS post-incident / CyberCubeDetails
AWS May 2026 (us-east-1 / use1-az4)May 2026~28 hours (single AZ)$25M+ est.Data-center cooling/thermal event shut down EC2/EBS hardwareAWS status / The RegisterDetails
TSB Bank MigrationApr 2018~2 weeks (partial)£330M + £48.65M fineFailed IT migrationFCA reports
GitHub Extended OutageOct 2018~24 hours (partial)$10M+ est.Database corruption cascadeGitHub post-incident
Fastly Global CDN OutageJun 2021~1 hour$100M+ est.Software bug triggered by customer configFastly post-incident
CenturyLink Network OutageAug 2020~5 hours$100M+ est.BGP routing announcement errorFCC reports
Google Cloud (IAM/Service Control)Jun 2025~3 hours (us-central1 ~7hr)$50M+ est.Invalid quota policy update crashed Service Control, broke IAMGoogle post-incidentDetails
Google Cloud Multi-regionJun 2019~4 hours$50M+ est.Configuration changeGoogle post-incident
Change Healthcare RansomwareFeb 2024Months$800M+ reportedRansomware (ALPHV/BlackCat)UnitedHealth disclosuresDetails
Robinhood (COVID volatility)Mar 2020Multiple days$70M fine + suitsInfrastructure overloadFINRA 2021Details
Azure Nov 2023 (Teams/M365)Nov 2023~8 hours$50M+ est.DNS change cascadeMicrosoft post-incidentDetails
JBS Foods RansomwareMay 2021~1 week$11M ransom + $100M+REvil ransomwareJBS disclosure
Toyota / Kojima IndustriesFeb 20221 day (14 plants)~$375M production lossSupplier cyberattackToyota disclosureDetails

Cost estimates are sourced from company disclosures, regulatory filings, and independent analyst research where available. Market cap figures reflect single-day movements and may not represent permanent losses. All figures in USD unless noted.

Cause Category Distribution

Among major publicly reported outages, software, configuration and cyber causes dominate the headline events. This skews differently from data center operator surveys: Uptime Institute's Annual Outage Analysis finds power the single most common cause of serious data center outages. The mix below is an illustrative ordering of the high-profile outages tracked on this page, not a survey statistic.

Configuration / Deploy Error30%
Software Bug22%
Cyberattack / Ransomware21%
Power / Infrastructure14%
Human Error9%
Third-party Dependency4%

Patterns in Major Outages

Single point of failure in widely-adopted software

CrowdStrike, Fastly, CenturyLink: when a change to a widely-deployed system is incorrect, the blast radius is massive. Monocultures of infrastructure dependency are the underlying cause.

Automated delivery amplifies the failure

Manual software updates catch issues before full deployment. Automated update pipelines (continuous delivery) push failures to 100% of systems simultaneously. CrowdStrike's channel file update bypassed staged deployment.

Recovery is always harder than expected

The CrowdStrike recovery required manual intervention on 8.5 million machines - there was no automated rollback because the sensor crashed before it could roll back. This is the hidden cost of outages: recovery engineering is rarely fully planned.

Supply chain dependencies are invisible risk

The Toyota/Kojima incident and the Delta/CrowdStrike cascade show that your outage risk extends to your suppliers and vendors. Third-party risk assessment is lagging behind actual dependency.

Frequently Asked

What is the most expensive tech outage in history?
The CrowdStrike July 2024 outage is the most expensive single IT outage in history, with Parametrix estimating $5.4 billion in Fortune 500 losses. Total economic impact including non-Fortune 500 businesses is estimated at $10 billion or more. 8.5 million Windows machines were affected globally.
What caused the CrowdStrike 2024 outage?
A faulty content configuration update (channel file 291) pushed to CrowdStrike Falcon security software caused Windows machines to crash into a boot loop (BSOD). The update contained a logic error causing a null pointer dereference in the Falcon kernel driver. Each affected device required manual recovery: booting into Safe Mode and deleting the faulty file.
What are the most expensive outages of 2025?
The two largest were the AWS us-east-1 outage on October 20, 2025 (a ~15-hour failure from a DynamoDB DNS race condition that cascaded across EC2, Lambda, and dozens of services; CyberCube estimated $38M-$581M in insured losses, with roughly 70,000 organizations affected) and the Cloudflare outage on November 18, 2025 (~3 hours of major disruption after a database permissions change produced an oversized bot-management config file that crashed proxy servers worldwide, affecting an estimated 2.4 billion users; revenue losses were estimated at $180M-$360M).

Updated 2026-04-27