Skip to main content

Quant Analytics: from scratch to pro · Professional practice and failure case studies · Pro

Case study: Knight Capital, 1 August 2012

In 45 minutes a market maker's trading software sent millions of unintended orders and lost about $460 million. The SEC's order traces the loss to a deployment error, old code left on a server and missing controls. The case is the standard example of operational and model risk.

4 min read Reviewed Revision 1

In this lesson

  • Describe the sequence of the Knight Capital incident from the SEC's findings
  • Identify the operational controls whose absence turned a software fault into a large loss
  • Compute the rate of loss and of order flow during an incident to size a kill switch
  • Explain why this is a model-risk case without any bad forecast

Read first: Model risk and live monitoring, Orders, bid, ask and liquidity

Cumulative loss at a constant rate over the incident

0 100 200 300 400 500 01020304045 Minutes since the start
Loss (USD million). Computed from the total loss divided evenly over the minutes. Illustrative: the actual loss path was not constant, and the order does not report one.

Worked numbers

Each result is recomputed from the formula shown.

WhatFormulaResult
loss in millions of US dollars460$460 million
minutes of trading4545 minutes
loss per minuteloss_m / minutes10.2
shares in millions397397 million
loss per shareloss_m / shares_m1.16
shares per minute in millionsshares_m / minutes8.8
executions per second, using 4 million as a floor4000000 / (minutes * 60)1,481
executions per customer order, using 4 million as a floor4000000 / 21218,868

Check yourself

Roughly how fast was Knight losing money during the incident?

About $460 million over about 45 minutes is about $10.2 million a minute.

What does the loss per share say?

$460 million over more than 397 million shares is about $1.16 a share on average. Each unintended share was cheap; the volume was the problem.

Name two controls that could have limited the loss.

A limit on gross position or order count that blocks orders automatically (a kill switch), and a check comparing orders leaving the router with those entered. A second-person review of the deployment would also have caught the missing update.

Why is this a model-risk case without a bad forecast?

SR 11-7 counts a model used outside its intended design as model risk. Old code ran on live orders under a repurposed flag, so the software did something it was never meant to do.

What should be monitored in real time besides profit and loss?

Order count, order rate, position size, fill ratio and message errors. These move before profit and loss does.

Key terms

Model riskEffective challengeLiquidity

Checked facts

Every figure below carries how it was checked: Primary checked (read in the cited primary, official, academic or data source), Two sources agree, or Approximate (an order of magnitude only).

Sources

Informational content. Not investment advice.