In August 2012, a software conflict at Knight Capital Group caused its automated trading system to send erroneous orders for NYSE-listed stocks and build positions larger than intended. Knight reported a realized, pre-tax loss of about $440 million. The incident also disrupted trading in individual stocks, but that figure was Knight’s loss—not a stated loss to the market as a whole.
What happened in the Knight Capital trading glitch?
Knight Capital Group launched new trading software on the New York Stock Exchange in August 2012. The Commodity Futures Trading Commission (CFTC) later said the new software conflicted with existing code. Knight’s automated system then submitted erroneous proprietary orders in NYSE-listed securities and established larger positions than the firm intended. The CFTC’s account does not establish the more specific code-level cause or provide a full order-by-order technical postmortem. CFTC, 2013
Knight said it traded out of its erroneous positions. In a statement reproduced by SecurityWeek on August 3, 2012, the firm described the result as a “realized pre-tax loss of approximately $440 million.” It also said the loss had severely affected its capital base, while its broker-dealer subsidiaries remained compliant with net capital requirements. SecurityWeek, August 3, 2012
How much did the Knight Capital software glitch cost?
The reported loss to Knight Capital was approximately $440 million. Both Knight’s contemporaneous statement, as reproduced by SecurityWeek, and the CFTC’s later description give an approximate figure; Knight characterized it as realized and pre-tax. It should not be described as a $440 million market-wide loss: the sources report the firm’s loss and separately describe disruption to trading.
#1 Best Overall
How did the glitch affect stock trading?
The CFTC said price swings affected nearly 150 securities and volatility associated with the algorithm led to trading pauses in five stocks. These figures describe the scope of disruption in the regulator’s 2013 account; they do not mean all affected securities moved in the same direction or by the same amount. The CFTC release also relayed reports of an approximately 40-minute delay before intervention, but presents that timing as attributed reporting rather than a definitive agency finding. CFTC, 2013
Why did the software failure become a major risk?
The CFTC placed the incident in a wider discussion of automated-trading system vulnerabilities. A software malfunction can become a financial and market risk when a system continues to submit orders or accumulate positions faster than people can recognize and stop the problem. The regulator’s discussion identifies several possible vulnerabilities across automated trading—not all of them established as causes in Knight’s case:
- Algorithm design flaws or software interactions.
- Market conditions outside the system’s normal operating parameters.
- Risk controls that fail to limit orders, executions, or positions.
- Communication-network or connectivity problems.
- Inadequate human supervision.
For Knight, the CFTC specifically described a conflict between newly launched software and existing code, followed by erroneous orders and larger-than-intended positions. The account supports treating the event as a risk-control and oversight problem as well as a software malfunction, without claiming to establish every technical detail.
What safeguards does the CFTC discuss for automated trading?
The CFTC’s concept release describes or considers controls that can constrain activity, detect unusual behavior, and help staff respond. They are safeguards for managing risk, not a proven checklist that would certainly have prevented Knight’s loss.
| Where the safeguard operates | Examples discussed by the CFTC | What it is intended to address |
|---|---|---|
| Before or during order flow | Maximum order-size limits, message-rate limits, execution throttles, and controls on the accumulation of orders, executions, or positions over a short period. | Excessive order activity or positions building faster than intended. |
| Monitoring and response | Alerts, algorithm identification, and emergency order cancellation. | Making unusual activity identifiable and enabling a response, including cancellation of orders. |
| Preparation and oversight | Testing and written procedures for supervisors and support staff. | Checking system behavior and clarifying responsibilities for monitoring and intervention. |
The release also discusses testing algorithms and systems under relevant conditions. The point is to consider how controls behave in practice, rather than assume that a written limit or an alert alone will stop a failure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the incident means for investors
Knight Capital’s loss was a firm-level trading loss, not a direct charge to retail investors. The episode is relevant to investors because it shows how automated order flow can create rapid operational risk and disturb trading in specific securities. It does not, by itself, establish a particular effect on an individual investor’s portfolio, nor does it show that every automated trading system carries the same risk.
At an SEC roundtable, then-chair Mary Schapiro was quoted in the CFTC release as saying: “Events like these demonstrate the core infrastructure and technology issues that can be problematic in any market structure.” The remark underscores that trading technology and its controls matter beyond the firm operating a particular algorithm.
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.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
