The root cause is almost never exotic
A mistyped command, an unreviewed config push, a single untested server — nearly every incident here traces back to an ordinary change that skipped a safeguard, not a sophisticated attack.
Every calculator on this site models a hypothetical incident. These pages walk through seven real ones — what broke, how long it lasted, and the dollar figures companies disclosed afterward, each cited to its public source.
Each one links to its primary source — an SEC filing, an incident postmortem, or reporting that cites a company's own disclosed figure — not a rumor or a headline estimate alone.
The details differ, but the shape of the cost is remarkably consistent across industries and decades.
A mistyped command, an unreviewed config push, a single untested server — nearly every incident here traces back to an ordinary change that skipped a safeguard, not a sophisticated attack.
Knight Capital lost $440M in 45 minutes; Fastly's outage lasted about an hour with no disclosed loss at all. What you do, and to whom, matters more than the clock.
Direct revenue loss is usually the smallest, most citable slice. Compensation, fines, litigation, and reputational drag tend to arrive later and rarely get one clean headline figure.
Questions that come up when using real incidents to make a budget or reliability case.
Mode
Accent