Deribit Halts Trading as It Probes Platform Problems
- Published
- Updated
Deribit reported a trading incident on Nov. 20 and said customers could still cancel open orders while it investigated platform problems. Trading later resumed after an outage that affected crypto perpetuals, stock-linked contracts, and cryptocurrency transfers.
Key claims & sources
What it means
Deribit is a crypto derivatives venue, so a trading interruption there affects a market used for perpetuals and stock-linked contracts as well as transfers. The Nov. 20 incident sits in the category of platform-wide operational problems rather than a product launch or policy change. For users, the immediate issue is whether they can enter or manage positions while the venue is investigating.
When an exchange can only offer order cancellation during an incident, traders lose the normal ability to adjust exposure the way they would on an operating venue. That shifts attention from strategy to basic access, especially for people using Deribit for leveraged derivatives and transfers. It also shows how much of crypto trading depends on continuous infrastructure rather than on the assets alone.
The case keeps the focus on operational resilience at a time when crypto venues are expected to handle multiple instruments at once, including derivatives and transfers. A short outage can interrupt trading, settlement, and portfolio management without touching the underlying tokens. That tension between always-on markets and fragile platform plumbing is central to how centralized exchanges present risk.
What is still unclear is the nature of the platform problem and whether all affected functions fully returned at the same time. The status updates here establish when trading was unavailable and when it later resumed, but they do not explain the technical issue behind the interruption. A fuller postmortem from Deribit would settle that gap.
Market reaction i
The total crypto market fell 1.4% in the 4 hours after the first headline, after falling 2.8% in the 2 hours before.
32 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | CALC · Key Leaked via Infrastructure incident | $26.9k |
| 2 days ago | Fluidkey incident | no figure in dollars |
| 3 days ago | RNT Lend · Admin key compromise incident | $954.7k |
| 3 days ago | K3 Capital · Smart contract vulnerability incident | $3.4M |
| 3 days ago | Gonka AI · Bridge Logic Flaw incident | $1.1M |
4345 incidents stored