Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Knight Capital’s trading system lost more than $460 million on August 1, 2012, after a deployment activated legacy code that kept routing stock orders even after customer orders had filled. A reused feature flag was the trigger, but the SEC also identified failures in testing, deployment, supervision, alert response, and market-access controls.
What failed at Knight Capital?
Knight’s SMARS was an automated, high-speed equity order router. On August 1, 2012, it malfunctioned while processing 212 customer orders. Over approximately 45 minutes, SMARS sent millions of orders, producing more than 4 million executions across 154 stocks and more than 397 million shares, according to the SEC’s 2013 order.
The router built unwanted positions: approximately $3.5 billion net long across 80 stocks and $3.15 billion net short across 74 stocks. Those figures describe the positions, not the loss. The SEC put the loss from the incident at more than $460 million.
How did the old Power Peg code become involved?
Discontinued, but still callable
Knight had stopped using its Power Peg functionality in 2003, but left its code in SMARS. In 2005, Knight moved Power Peg’s cumulative-quantity tracking function earlier in the code sequence. The SEC order says Knight did not retest whether Power Peg would still work correctly if called after that change.
#1 Best Overall
A flag repurposed for new functionality
Knight was preparing changes for the New York Stock Exchange’s Retail Liquidity Program, scheduled to start on August 1, 2012. The company repurposed a flag previously associated with Power Peg for the new program and intended to remove the old code. The legacy code was not successfully removed and remained callable. Certain eligible orders then activated the defective Power Peg path.
Why orders kept going
Because the cumulative-quantity function had been moved, SMARS repeatedly sent child orders without properly accounting for shares already executed. Other system components recognized that parent orders had filled, but that information was not communicated to SMARS. The result was not simply an incorrect flag value: old code, a changed sequence, and a failure to communicate filled quantities combined to produce repeated orders.
What controls failed beyond the flag?
The SEC found Knight lacked market-access controls and procedures reasonably designed to manage the risks of its systems, including automated trading-system risks. The order and the SEC’s announcement describe a broader breakdown involving software testing, deployment, supervision, warning messages, and safeguards for market access.
- Testing: The Power Peg path was not retested after its cumulative-quantity function was moved, and the deployment did not prevent the legacy path from being activated.
- Deployment: Changes intended for the new program went live while the old code remained callable.
- Detection: The SEC said Knight received 97 automated emails referencing the router and identifying an error before the market opened. They were not designed as system alerts, but the SEC viewed them as an opportunity to identify and correct the problem. Knight did not act on them that day.
- Market access: The firm’s controls did not adequately limit the risks created by its automated system once it began sending unintended orders.
The SEC’s release quoted Daniel M. Hawke, then chief of the Enforcement Division’s Market Abuse Unit: “Brokers and dealers must look at each component in each of their systems and ask themselves what would happen if the component malfunctions and what safety nets are in place to limit the harm it could cause.”
How much did Knight lose?
The figures refer to different measures and should not be treated as interchangeable.
| Measure | Amount and scope |
|---|---|
| SEC incident-loss figure | More than $460 million from unwanted positions, as described by the SEC in 2013. |
| KCG trading loss | $461.1 million pre-tax, principally related to trading, reported by KCG Holdings for 2013 in its 2013 Form 10-K. |
| KCG broader total | $468.1 million in trading losses plus subsequent related legal and professional costs, reported by KCG for 2013. This is not trading loss alone. |
| SEC settlement | $12 million, the settlement amount for the market-access-rule charges—not the trading loss. |
What happened after the incident?
On October 16, 2013, the SEC announced that Knight Capital Americas agreed to pay $12 million to settle charges that it violated the market-access rule, Rule 15c3-5. The SEC called it its first enforcement action under that rule. The order records that Knight consented without admitting or denying the findings, apart from jurisdiction and the subject matter of the proceedings.
KCG’s 2013 annual report described follow-up measures including appointing a Chief Risk Officer, establishing a board Risk Committee and a formal Operational Risk Management function, and requiring additional review and supervisory approval for significant software installations. The company also reported adding market-access controls and router shutdown capability, deploying application kill switches, and creating an Emergency Response Center and Emergency Management Plan. These are measures the company reported; they do not establish that any system is risk-free.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat the incident shows about feature flags and deployment safety
A feature flag can control whether software behavior is enabled, but changing what a flag means does not make old code disappear. In Knight’s case, the flag’s new role, the still-callable legacy feature, and the untested code-path change interacted with the router’s execution logic. The SEC’s findings make the incident a warning about the full deployment and market-access system—not just a cautionary tale about one flag.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
