The 2012 trading glitch at Knight Capital refers to the technical failure that struck the American broker Knight Capital Americas LLC on August 1, 2012, costing more than $460 million in 45 minutes of trading. According to the Securities and Exchange Commission order published on October 16, 2013, a piece of code abandoned in 2003 was mistakenly reactivated on a single server, triggering the release of millions of unwanted orders into the market.
Dead code from 2003, never removed from the servers
Before 2012, Knight used an internal feature called Power Peg for certain order types. The firm stopped using it as early as 2003, as the SEC order states: “In 2003, Knight ceased using the Power Peg functionality”. The problem is that this code was never removed from the production servers. It remained there, dormant, for nine years.
In 2005, Knight moved a cumulative quantity counting function inside this very Power Peg code, without retesting its behavior in case it was ever triggered again. The SEC order underlines this: “Knight did not retest the Power Peg code after moving the cumulative quantity function to determine whether Power Peg would still function correctly if called”. This decision, harmless at the time, became the point of failure seven years later.
A software flag recycled on a single server
On August 1, 2012, Knight deployed a new order-routing code meant to replace the old system. The deployment was supposed to reach eight servers. On one of them, a technician failed to copy the new code, and no one noticed because there was no review process in place. The SEC order is explicit on this point: “Knight did not have a second technician review this deployment and no one at Knight realized that the Power Peg code had not been removed from the eighth server, nor the new RLP code added. Knight had no written procedures that required such a review”.
The new system reused an existing software flag to trigger the new code. On the seven servers correctly updated, everything worked as intended. But on the eighth, that same flag instead reactivated the old Power Peg code, still present since 2003. The SEC sums it up: “orders sent with the repurposed flag to the eighth server triggered the defective Power Peg code still present on that server”.
45 minutes of uncontrolled order flow
As soon as the market opened, Knight’s SMARS automated routing system began sending erroneous orders through this eighth server. The phenomenon continued for 45 minutes before being stopped. The figure given by the SEC is precise: “SMARS routed millions of orders into the market over a 45-minute period, and obtained over 4 million executions in 154 stocks for more than 397 million shares”.
By the end of this episode, Knight found itself holding massive, unwanted positions: a net long position of roughly $3.5 billion across 80 stocks, and a net short position of roughly $3.15 billion across 74 stocks. The SEC puts a number on the final loss: “Knight had assumed a net long position in 80 stocks of approximately $3.5 billion and a net short position in 74 stocks of approximately $3.15 billion. Ultimately, Knight lost over $460 million from these unwanted positions”.
A figure confirmed in the financial results
This amount is not just a regulatory estimate. In its third-quarter 2012 results, published through a document filed with the SEC, Knight Capital Group put a precise number on the accounting impact of the incident. The document reports “pre-tax losses of $461.1 million related to the technology issue that occurred on August 1, 2012 and subsequent related costs”. The firm thus confirmed, in its own books, a $461.1 million loss directly tied to this technical failure.
| Element | Value | Date |
|---|---|---|
| Duration of the incident | 45 minutes | August 1, 2012 |
| Executions completed | more than 4 million, across 397 million shares | August 1, 2012 |
| Net long position | approximately $3.5 billion | August 1, 2012 |
| Net short position | approximately $3.15 billion | August 1, 2012 |
| Announced accounting loss | $461.1 million pre-tax | third quarter 2012 |
What this account does not cover: the precise reactions of other market participants during those 45 minutes, or the details of the internal monitoring mechanisms that might have caught the anomaly sooner. The SEC order focuses on the technical chain of failure, not on a minute-by-minute market timeline. Other technical failures have marked the markets, such as the J-Com incident, where a reversed order cost Mizuho 40 billion yen.
Frequently asked questions
What exactly was the 2012 trading glitch at Knight Capital?
It was a technical failure on August 1, 2012, in which an automated order-routing system sent millions of unwanted orders into the market over 45 minutes, caused by old code mistakenly reactivated. The episode cost the firm more than $460 million.
Why was the Power Peg code reactivated in 2012 when it dated back to 2003?
Because it had never been removed from the production servers after being abandoned in 2003. During a new deployment in 2012, a reused software flag triggered this dormant code on just one of eight servers, the one where the new code had not been correctly installed.
How did the error go unnoticed before the deployment?
The SEC order states that no written procedure required a second technician to review the deployment. The absence of this cross-check meant the omission on the eighth server was only discovered after the erroneous orders had already been sent into the market.
What was the final cost for Knight Capital?
Knight Capital Group announced a pre-tax loss of $461.1 million related to this technical incident in its third-quarter 2012 results. This amount covers both the unwanted positions accumulated and the costs of unwinding them.