Knight Capital’s $440 Million Software Failure

What Knight Capital Did

• In 2012, Knight Capital was a major Wall Street market maker, handling about $20 billion in trades daily and roughly 10% of U.S. stock trading.
• Its SMARS system split large orders into smaller ones and routed them across markets.
• The New York Stock Exchange introduced a new retail liquidity program, prompting Knight to update its trading software.

How the Failure Happened

• Engineers reused an old feature flag that had once activated Power Peg, a test function designed to buy aggressively without regard to price.
• Knight manually deployed the update to eight servers. One server did not receive it, leaving its outdated Power Peg code in place.
• When the feature flag was activated on August 1, 2012, seven servers handled trades correctly, but the eighth began executing Power Peg’s uncontrolled buying.
• Knight mistakenly rolled back the seven updated servers, leaving all eight running the faulty behavior.

The Damage

• In about 45 minutes, Knight made roughly 4 million trades across 154 stocks and accumulated a large unwanted position.
• One penny stock, Wizard Software Corporation, rose from $3 to $14 during the disruption.
• Knight lost more than $440 million; its stock fell 75% in two days.
• The company was acquired four months later, and its remaining operations were eventually absorbed by Virtu.

Key Lessons

• Retire unused code and feature flags instead of reusing them for unrelated changes.
• Use reliable, consistent deployment processes across every server.
• Prepare clear monitoring and recovery procedures for production failures.
• A single outdated system can undermine an otherwise correct deployment.

The video closes with a sponsor segment for HyperAgent, an AI tool pitched as helping open-source maintainers triage issues, reproduce bugs, and prepare draft fixes.