Market cap $2.04 T −7.05 % over 24 hours24h volume $147.89 BBTC dominance 57.5 %ETH 9.9 %Fear & Greed 12 Extreme fearCoins 21,332

Deribit stopped trading twice on Friday, for about two hours and 20 minutes in all, and has not said why

Deribit outage on 20 November: trading stopped at 16:17 and again at 19:28 UTC, back at 21:31. The Coinbase-owned exchange has published no cause.

8 min read

Abstract laptop with candlestick bars beside a warning sign and a bank building
Table of contents
  1. Deribit outage timeline: 19 minutes in the afternoon, two hours in the evening
  2. What was cut off, and what the status page does not show
  3. No cause, no word on liquidations or compensation
  4. The fourth stoppage in a month at the Coinbase-owned exchange
  5. How much sits on Deribit

Deribit, the crypto options exchange owned by Coinbase, stopped trading twice on Friday 20 November 2026 while the market was selling off. The first Deribit outage lasted about 19 minutes, from 16:17 to 16:36 UTC. The second ran for just over two hours, from 19:28 to 21:31 UTC, according to the incident log on Deribit’s status page. Deribit has given no cause for either.

The exchange files both stoppages under a single incident, titled “Platform Unavailable 20/11/2026” and rated “major”. It was opened at 16:17 UTC and closed at 22:31 UTC, six hours and 14 minutes later, once the last limits on order flow had been lifted. On Saturday 21 November at 05:53 UTC, the page carried no post-mortem.

Added together, the status page’s times give about 2 hours and 21 minutes without trading: 18 minutes in the afternoon, then 2 hours and 3 minutes in the evening. Counted from the earlier Telegram notices, the sum is close to two and a half hours. It happened on a day of heavy selling and forced liquidations across exchanges, the kind of day when holders of options and futures want to adjust their positions.

Deribit outage timeline: 19 minutes in the afternoon, two hours in the evening

Deribit posts its notices in two places, the status page and its Telegram notification channel. The wording is nearly always the same. The Telegram messages went out a few minutes earlier each time: 16:15 UTC for the first stoppage and 19:22 UTC for the second, against 16:17 and 19:28 on the status page.

The first notice read: “We are experiencing issues on the Deribit platform and trading is unavailable.” At 16:36 UTC the exchange said trading had resumed and moved the incident to monitoring.

Less than three hours later the same sentence came back. Ten minutes after it, at 19:38 UTC, the status page added a second message: “Some users may currently be unable to trade derivatives.” It ended with four words: “Your funds are safe.” That line appears on the status page only, not in the Telegram channel.

At 20:28 UTC on Telegram (20:29 on the status page) the vocabulary changed. “Trading on Deribit is unavailable for maintenance,” the exchange wrote, an hour into a stoppage it had first described as “issues”. A further note at 20:46 UTC said the team was still working through that maintenance. At 21:22 UTC Deribit announced a pre-open period at 21:25 and a restart at 21:30, and it confirmed the restart at 21:30 on Telegram and 21:31 on the status page.

StepTelegram channel (UTC)Status page (UTC)
First stoppage announced16:1516:17
Trading resumed16:3616:36
Second stoppage announced19:2219:28
“Some users may currently be unable to trade derivatives. Your funds are safe.”not posted19:38
Stoppage described as maintenance20:2820:29
Pre-open at 21:25 and restart at 21:30 announced21:2221:22
Trading resumed21:3021:31
Overall cap removed, BTC and ETH back to normal limits22:0122:02
Last caps removed, incident closed22:3022:31

Trading did not come back at full speed. Deribit reopened with caps on how fast customers could send orders. At 22:01 UTC it said the overall cap was gone and that bitcoin and ether instruments were back to normal limits, while instruments it calls Tier 2, Tier 3 and blockchain tokens that record a claim on an asset held off chain, such as Treasury bills, fund shares, loans or gold. A custodian keeps the asset, a transfer agent keeps the register, and the token is worth what that structure lets its holder claim.">RWA stayed limited to 10 orders and 2.5 mass quotes per second. Those were removed at 22:30 UTC. The notices do not define the tiers.

Abstract server rack beside an hourglass, a padlock and a calendar page
Deribit's status page shows trading unavailable from 16:17 to 16:36 UTC and from 19:28 to 21:31 UTC, then a restart with order caps.

What was cut off, and what the status page does not show

During the first stoppage the status page switched six services to “major outage”: the web trading interface (Direct Access UI), the REST API, the WebSocket feed and the three FIX services used by professional firms for orders, market data and drop copy. During the second, four of them were marked down. The FIX market data and drop-copy feeds were not.

The incident is attached to a much longer list of components: more than a hundred perpetual futures, from BTC and ETH to contracts on Nvidia, Tesla, gold and silver, plus network transfer routes for some forty tokens. crypto.news, which reported the first stoppage at 17:30 UTC on Friday, listed those markets and transfer routes as affected. In the status page’s own change log, though, no transfer route changes state at any point of the incident: each is recorded as operational before and after every update. Deribit has not said whether deposits and withdrawals were delayed.

What could customers do while trading was off? The Defiant reported during the first stoppage that Deribit’s trading screen said open orders could still be cancelled. Deribit’s notices for the two unplanned stoppages say nothing about it. The only written reference to a cancel-only mode on Friday concerns something else, a planned security patch at 09:00 UTC, when the Telegram channel said at 09:04 that the platform was back with orders that “can be cancelled only” and at 09:06 that trading had resumed.

Cancelling an order is not the same as closing a position. A trader who was long or short when the platform went down had no way to reduce that exposure on Deribit until it reopened.

No cause, no word on liquidations or compensation

Neither the status page nor the Telegram channel says what failed at 16:15, what failed again at 19:22, or why the second stoppage turned into maintenance. Deribit groups them in one incident but does not say they share an origin. It also does not say whether the morning security patch, which it had announced on Thursday as a fix for “a recently disclosed vulnerability”, played any part.

Nothing has been published either on accounts that were close to their margin limits. Deribit has not said whether its liquidation engine ran during the stoppages, at what prices positions were marked when trading reopened, or how many accounts were liquidated at the restart. Cryptopolitan, which covered the outage on Friday night, wrote that there is no documented evidence tying it to forced liquidations.

None of the notices mentions compensation or a claims procedure.

On funds, the only statement is the 19:38 UTC line, “Your funds are safe.” Cryptopolitan also reported that Deribit said no users had lost money.

Abstract magnifying glass over a document beside scales and a group of people
Deribit's notices give no cause and say nothing on liquidations or compensation.

The fourth stoppage in a month at the Coinbase-owned exchange

Friday was not isolated. Deribit’s status page lists three earlier incidents since 21 October in which, in its own words, the platform was “unavailable” or trading was “down”. Only one came with an explanation.

On 21 October the platform was unavailable from 14:23 to 14:33 UTC, “due to a networking issue” in Deribit’s words; the closing note said trading was open again. On 5 November, under an incident titled “Degraded Performance”, trading was down from 15:27 to 15:41 UTC and a group of smaller contracts was suspended again from 20:28 to 21:03 UTC. On Monday 16 November the platform was unavailable from 10:35 to 10:47 UTC, announced with the same sentence as on Friday. That was the day we reported that the $60,000 bitcoin put had become Deribit’s largest put position. None of the four incident pages carries a post-mortem.

The dates matter because of what outlets say now runs on Deribit. Positions and balances of Coinbase’s international derivatives exchange moved onto Deribit on 1 October, according to crypto.news and Cryptopolitan, both citing Coinbase’s own documentation. Deribit’s status page now sits on a coinbase.com address. And on Thursday 19 November, the day before the outage, Coinbase opened crypto options that run on Deribit’s infrastructure to eligible customers in selected markets outside the United States, according to crypto.news, which cited Coinbase’s announcement. The outlet says they settle in USDC and cover six assets.

If those reports are right, a stoppage at Deribit also reaches people who trade through Coinbase. Neither company has said how they were affected on Friday.

How much sits on Deribit

Deribit held $22.4 billion of bitcoin options open interest and $4.9 billion in ether options on 20 November, according to figures from The Block cited by Cryptopolitan in an article published that evening. Open interest is the value of contracts that are still open, so those are positions whose owners could not trade them on the venue for more than two hours on Friday.

Outsiders also see those positions later than they used to. Deribit was due to start publishing open interest with an eight-hour delay from 10 November, according to CryptoSlate, which cited the exchange’s release notice. Any reading of how positions changed around the two stoppages therefore arrives late.

Deribit’s status page has a post-mortem field for each incident. It is empty for 20 November and for the three before it. The cause, any liquidations at the 21:30 UTC restart and any compensation are what such a report would have to cover.

Sources

  1. Deribit status page, incident "Platform Unavailable 20/11/2026" status.deribit.coinbase.com
  2. Deribit notifications channel on Telegram, messages of 16 to 20 November 2026 t.me
  3. crypto.news, Deribit trading outage, 20 November 2026 crypto.news
  4. Cryptopolitan, Deribit outage and crypto derivatives concerns, 20 November 2026 cryptopolitan.com
  5. The Defiant, Deribit halts trading as it probes platform problems, 20 November 2026 thedefiant.io
  6. CryptoSlate, Deribit to delay open interest data by eight hours, 9 November 2026 cryptoslate.com

Leave a Reply

Your email address will not be published. Required fields are marked *