Deribit Index Failure Triggered a Bitcoin Perpetual-Swap Flash Crash

Deribit suffered a venue-specific bitcoin derivatives flash crash on October 31, 2019, after its BTC reference-index process malfunctioned at around 21:00 UTC. A contemporaneous report from The Block said the exchange’s flagship BTC perpetual swap fell about 15% and that Deribit locked the platform shortly after the move. The episode mattered beyond one abrupt candle: an erroneous benchmark had fed directly into an automated liquidation system, turning a data-quality failure into forced position closures.

This was not evidence that bitcoin’s global spot market had suddenly lost the same amount. It was evidence that a leveraged trading venue could manufacture its own extreme price event when the controls around a reference index failed.

A venue price broke from the wider market

CoinDesk’s November 1 account recorded Deribit futures prices falling from $9,150 to $7,720 before recovering above $9,000 within minutes. Using those quoted endpoints, the decline was about 15.6%, consistent with The Block’s rounded 15% figure. The measurement is a short, venue-specific futures-price window around 21:00 UTC; it is not a daily close, a volume-weighted global bitcoin price, or a claim that executable liquidity existed at every level of the move.

The same reporting placed a smaller Coinbase Pro BTC-USD spot move earlier in the evening, from $9,260 to $9,055 at 19:55 UTC. That comparison helps separate the Deribit dislocation from the broader market. It does not, by itself, prove which data input caused Deribit’s index to fail.

The Block reported on October 31 that Coinbase Pro was unavailable for roughly 75 minutes, from 20:00 UTC to 21:15 UTC, and that Coinbase was one of seven venues then used in Deribit’s BTC index. The report noted speculation connecting the outage to Deribit’s malfunction. Deribit had not publicly identified the offending constituent by the end of October 31, so attributing the crash to Coinbase alone would go beyond the event-day record.

Why the index error became a liquidation event

A derivatives exchange does not use a reference price merely for display. Its index and related mark-price machinery inform margin, profit-and-loss calculations and liquidations. If a bad venue input is admitted and an outlier filter fails, the reference can move even when the wider market has not. Leveraged long positions may then appear undercollateralized, and automated systems can close them before a human can intervene.

That sequence is the key institutional lesson from October 31. Crypto derivatives traded continuously across fragmented venues, while each platform controlled important parts of its own benchmark construction and failure handling. Multiple index constituents were intended to make the reference harder to manipulate, but redundancy only worked if stale or anomalous inputs were rejected correctly. The incident exposed model and operational risk alongside ordinary market risk.

Contemporaneous reporting said Deribit acknowledged a BTC index-calculation problem, blamed a failure to remove an incorrect outlier and promised to compensate affected clients. What remained uncertain on October 31 was the complete number of liquidations, the exact account-level losses and whether every affected order would be restored.

Confirmed on November 1

In a November 1 statement, Deribit’s founders said a software bug had prevented one outlier from being excluded, causing the flash crash and multiple invalid liquidations. The company said it restored affected accounts to their pre-crash equity levels and reimbursed more than 150 BTC, which it valued at $1.3 million. Those impact figures are Deribit’s own account, not an independent audit.

Deribit also said it chose compensation instead of rolling back trades because counterparties may have hedged elsewhere, and that it had fixed the index issue. That later confirmation strengthens the causal record, but it should not be confused with what market participants knew before October 31 ended.