← Back to the 100 Software Failures Timeline
Case Study #20 — Top 100 Software Failures

Knight Capital Group trading glitch

Knight Capital lost about $440 million in 45 minutes from erroneous stock trades, nearly bankrupting the firm and forcing an emergency rescue investment.

2012-08-01
When it happened
Finance
Sector
#20 of 100
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

Knight Capital lost about $440 million in 45 minutes from erroneous stock trades, nearly bankrupting the firm and forcing an emergency rescue investment.

Finance
Sector affected
2012-08-01
Date of the event
#20
Rank in the Top 100 Software Failures
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

Deployment of new trading software to production servers was incomplete: one server retained old, dormant test code that, when accidentally re-activated by a repurposed flag, triggered millions of unintended orders.

01Root Cause

Deployment of new trading software to production servers was...

What Happened

Deployment of new trading software to production servers was incomplete: one server retained old, dormant test code that, when accidentally re-activated by a repurposed flag, triggered millions of unintended orders.

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.