Knight Capital
$440M
Software
Every financial disaster has a story.
Every story changed how the world builds money.
The Cost of Failure
Estimated value destroyed by major fintech failures
$440M
Software€1.9B
Governance$209B
Liquidity$81M
CyberHistory
The Collection
Patterns
Systems grow faster than understanding. Edge cases become landmines.
No circuit breakers. No feature flags. No way to stop the bleeding.
Code is only as safe as the deployment process and the people running it.
Speed over safety. Growth over controls. Until the day it isn’t.
Featured Artifact
08:00 AM
Engineers push new code for a NYSE retail liquidity program. One server is missed.
08:01 AM
A deprecated “Power Peg” flag is still active on one of eight servers.
09:30 AM
The dormant code awakens. Orders begin firing at extreme speed.
09:30 – 09:45
In 45 minutes the system sends millions of orders across 154 stocks.
10:15 AM
Knight Capital’s net capital is effectively wiped out. The firm is sold days later.
Mandatory ability to stop all automated trading instantly.
Strict lifecycle and validation for every configuration flag.
Never deploy to 100% of capacity at once.
Automated checks that every server received the correct code.
Featured Artifact
2020 – 2021
Tech and venture clients flood SVB with cash. The bank buys long-duration Treasuries and MBS while rates sit near zero.
2022
The Federal Reserve hikes aggressively. SVB’s bond portfolio suffers massive unrealized losses. Duration risk is no longer theoretical.
March 8, 2023
SVB announces a $1.8B realized loss on securities sales and a capital raise. Confidence begins to crack.
March 9
Social media amplifies fear. $42 billion in deposits try to leave in a single day — the fastest bank run in history.
March 10
The FDIC takes over. SVB becomes the second-largest bank failure in U.S. history.
Long-duration “safe” assets can destroy capital when rates move fast.
Heavy concentration of uninsured funds creates extreme run risk.
Bank runs now happen in hours, not days. Liquidity buffers must match.
Capital raises and loss disclosures need careful sequencing and clarity.
Architecture, sequence, and the invisible systems behind the failure.
One server still carried a legacy flag that had been disabled everywhere else. When market open arrived, that single process began generating orders without the intended risk controls.
FIX Message (simplified)
8=FIX.4.2 | 35=D | 49=KNIGHT | 56=NYSE
11=OrderID | 55=AAPL | 54=1 | 38=100000
40=1 | 59=0 | 10=xxx
→ Matching Engine
→ No pre-trade risk check (legacy path)
→ Immediate execution
→ Position explodes
New failures continue to teach us. The best engineers study the past.