The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Knight Capital lost more than $460 million after its automated stock-order router began sending millions of unintended orders on August 1, 2012. A reused software flag helped activate legacy Power Peg code, but the loss was not simply one bad flag: stale code, an untested change, a failed deployment, missed warning messages, and inadequate market-access safeguards combined to let the malfunction spread.
What happened at Knight Capital?
Knight Capital Americas’ SMARS system was an automated, high-speed router for equity orders. On August 1, 2012, while processing 212 customer orders, it malfunctioned and sent orders into the market for about 45 minutes. The U.S. Securities and Exchange Commission (SEC) said the episode produced more than 4 million executions across 154 stocks, involving more than 397 million shares. The SEC’s 2013 order describes the system failure and its scale.
As an Amazon Associate I earn from qualifying purchases.
The immediate technical trigger was a deployment for the New York Stock Exchange’s Retail Liquidity Program, scheduled to start that day. The failure exposed a deeper weakness: code Knight no longer intended to use was still reachable, and SMARS did not correctly account for executed shares as it generated child orders.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How did the old Power Peg code become active?
Discontinued, but still present
Knight had stopped using its Power Peg functionality in 2003, but left the code in SMARS. In 2005, it moved Power Peg’s cumulative-quantity tracking function earlier in the system’s 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 was reused for new functionality
In preparation for the Retail Liquidity Program, Knight changed SMARS and repurposed a flag formerly associated with Power Peg. The company intended to remove the legacy code, but the deletion did not succeed. Certain eligible orders then triggered the still-callable Power Peg path.
The flag was therefore a trigger, not a complete explanation. The code remained in production, a change affecting its behavior had gone untested, and deployment controls did not prevent the unintended path from becoming active.
Why did the router keep sending orders?
SMARS used parent orders and smaller child orders to route trading activity. After the code change, the cumulative-quantity function ran earlier than before. When the defective Power Peg path was invoked, the router 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.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallAs a result, orders continued to reach the market even as executions accumulated. The router’s behavior transformed a software defect into a rapidly growing trading position.
What controls failed beyond the feature flag?
The SEC found that Knight lacked market-access controls and procedures reasonably designed to manage the risks of its systems, including automated trading-system risks. Its findings describe problems with testing, software deployment, supervisory controls, warning messages, and safeguards for market access. The incident is best understood as a chain of failures rather than as a single coding mistake.
Warning messages did not prompt action
The SEC reported that 97 automated emails referencing the router and identifying an error arrived before the market opened. Knight did not act on them that day. The agency also cautioned that these messages were not designed as system alerts; they nevertheless offered an opportunity to identify and address the problem.
Market-access safeguards did not contain the malfunction
Controls intended to limit the risks of automated order routing did not stop the malfunction from producing large positions. In announcing the settlement, the SEC said broker-dealers must consider how each system component might fail and what safeguards can limit the damage. The SEC’s announcement characterized this as its first enforcement action under the market-access rule.
How large were the positions and losses?
The figures below describe different things and should not be treated as interchangeable. The SEC’s position values are exposure figures, while the loss figures reflect different accounting scopes.
| Measure | Amount and scope | Source |
|---|---|---|
| Trading activity | More than 4 million executions in 154 stocks, totaling more than 397 million shares over approximately 45 minutes | SEC, 2013 order |
| Net positions | Approximately $3.5 billion net long in 80 stocks and $3.15 billion net short in 74 stocks; these are position values, not losses | SEC, 2013 order |
| Incident loss | More than $460 million from unwanted positions, as rounded by the SEC | SEC, 2013 order and SEC, 2013 announcement |
| Pre-tax trading loss | $461.1 million, principally related to trading, reported by KCG Holdings for 2013 | KCG Holdings, 2013 Form 10-K, filed 2014 |
| Trading loss and later related costs | $468.1 million, including subsequent related legal and professional costs; not trading loss alone | KCG Holdings, 2013 Form 10-K, filed 2014 |
What happened after the incident?
On October 16, 2013, Knight Capital Americas agreed to pay $12 million to settle SEC charges that it violated Rule 15c3-5, the market-access rule. That settlement was separate from the trading loss. Knight consented to the SEC’s order without admitting or denying its findings, except as to the proceeding’s jurisdiction and subject matter.
In its 2013 annual report, KCG described measures taken after the failure: appointing a Chief Risk Officer, creating a board Risk Committee and a formal Operational Risk Management function, requiring additional review and supervisory approval for significant software installations, adding market-access controls and router shutdown capability, deploying application kill switches, and establishing an Emergency Response Center and Emergency Management Plan. These are measures the company reported, not evidence that any system is risk-free.
Why the incident is more than a “bad flag” story
The reused flag explains how an old code path was triggered. It does not explain why that path remained callable, why the code was not retested after a relevant change, why deployment checks failed to catch the problem, why warnings did not lead to action, or why safeguards did not contain the resulting orders. The Knight failure shows how a small configuration change can expose a much larger weakness when software lifecycle controls and market-access risk controls do not work together.
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.
