Future 4 November 2026 4 MIN READ
Knight Capital: 45 Minutes, $460 Million
A forgotten code path on one of eight servers cost a trading firm $460 million in 45 minutes. What the SEC found about deployment and controls.
THE SHORT ANSWER
In 2012 a software update reached seven of Knight Capital's eight trading servers. The eighth still held old code that a reused flag switched back on. In about 45 minutes it sent millions of orders and the firm lost over $460 million. The SEC blamed missing controls and weak deployment.
On this page
An update that missed one server
In the summer of 2012 Knight Capital, a US broker-dealer, was getting ready for a new service on the New York Stock Exchange, the Retail Liquidity Program, which was due to start on 1 August. The firm needed new code in SMARS, its automated router, which takes a customer’s “parent” order and sends smaller “child” orders to the markets as liquidity allows.
According to the US Securities and Exchange Commission (SEC), the new code was rolled out in stages from 27 July across eight servers. One technician did not copy it to one of them. Nobody noticed: Knight had no second person reviewing deployments of SMARS and no written procedure that required one.
The code that was meant to be gone
The new code was supposed to replace an old function called Power Peg, which Knight had stopped using in 2003 but had left on its servers. The new code also reused the flag that used to switch Power Peg on. On the seven updated servers that flag now started the new service. On the eighth it woke up the old function.
There was a second problem inside the old function. In 2005 Knight had moved the part that counts how many shares of a parent order had already been executed, so the loop could stop once the order was filled. The SEC says Knight did not retest the old code after that change. On 1 August the eighth server therefore kept sending child orders without ever learning that the parent order was done.
Forty-five minutes
The SEC order puts the damage in numbers. Only 212 parent orders hit the faulty code, but SMARS sent millions of child orders in about 45 minutes. They produced more than 4 million executions in 154 stocks, for over 397 million shares. Knight ended up with a net long position of roughly $3.5 billion in 80 stocks and a net short position of roughly $3.15 billion in 74 others, and lost more than $460 million.
The trading also moved prices. In 75 of the stocks, Knight made up more than 20% of the volume and contributed to price moves of more than 5%. In 37 of them the price moved by more than 10%, with Knight at over 50% of the volume.
Warnings nobody read
The order lists several things that could have limited the damage.
- Early e-mails. From about 8:01 a.m., before the market opened, a Knight system sent 97 automated e-mails mentioning “Power Peg disabled”. They were not designed as alerts and staff did not normally read them.
- No brake. There was no control comparing orders leaving SMARS with orders that had entered it, and no way for the system to stop itself. A position limit of $2 million on the account that collected the executions was not linked to any automatic control.
- Monitoring by eye. The main risk tool showed positions after the fact and relied on people noticing.
- A bad fix. With no written incident procedure, engineers uninstalled the new code from the seven correct servers. The SEC says this made things worse, because those servers then also ran Power Peg.
What happened next
On 16 October 2013 the SEC announced a settlement, its first action under the market access rule adopted in 2010. Knight, without admitting or denying the findings, accepted a censure, a $12 million penalty and a review of its controls by an independent consultant. The SEC’s text gives the loss as “more than $460 million”.
Why it matters
Each step was ordinary: a missed copy, an old flag, a test skipped years earlier. What turned it into a $460 million event was speed with no brake.
Our take: automation needs a stop button that does not depend on a person noticing. The code was old, but the real failure was a router that could keep sending orders after its own work was finished.
Do you agree?
Take it to Chevlume: write your view, add your sources and let others answer. The closed alpha is by invitation.
Keep reading
Belgium 2003: The 4,096 Extra Votes
One candidate, 4,096 phantom votes and a bit flip. What the official report concluded, and what later retellings added about cosmic rays.
FUTURE / EXPLAINERWhat Quantum Computers Can and Cannot Do
Qubits, errors, advantage claims and the threat to encryption, with every result labelled as demonstrated, claimed by a company or projected.
SPACE / EXPLAINERWhy CubeSats Changed Access to Space
A standard 10 cm unit made small satellites cheap to build and launch. Where the idea came from, how NASA flies them and what still takes months.
Sources
- In the Matter of Knight Capital Americas LLC, Exchange Act Release No. 70694 · U.S. Securities and Exchange Commission · Accessed
- SEC Charges Knight Capital With Violations of Market Access Rule (2013-222) · U.S. Securities and Exchange Commission · Accessed
Published
Discuss on X