Skip to the article
Crypto Daybook

Markets, chains and policy news

Deribit reopens after second trading halt on Nov. 20

Deribit reopened trading at 21:30 UTC on Nov. 20 after a second halt, then lifted temporary order caps across all instruments by 22:31 UTC that evening.

Crypto Daybook Newsroom2 min read

Deribit reopens after second trading halt on Nov. 20

Deribit reopened trading at 21:30 UTC on Nov. 20 after a second halt that day, and removed temporary order caps from all instruments by 22:31 UTC. The restart restored access for traders, but the exchange did not state what caused the later interruption.

Deribit’s status page timeline records an earlier outage beginning at 16:17 UTC. Trading resumed at 16:36 UTC, but a new notice at 19:28 UTC said trading was unavailable again. At 19:38 UTC, the exchange said some users might be unable to trade derivatives.

The exchange later said trading was unavailable for maintenance. At 21:22 UTC, it announced a pre-open period at 21:25 and a planned restart at 21:30. Its next updates, at 21:31 and 21:33, said trading had resumed and that the platform was under monitoring.

The restart came with limits still in place. At 22:02 UTC, Deribit said the overall cap had been removed and Bitcoin and Ether were back to normal limits. Tier 2, Tier 3 and real-world asset (RWA) instruments remained capped at 10 orders per second, with a burst limit of 10; mass quotes were limited to 2.5 per second, with a burst limit of 10. These caps set how quickly users could send orders and quotes.

At 22:31 UTC, Deribit said it had removed the remaining caps and returned all instruments to normal limits. That update marked the end of the restrictions following the halt. The exchange’s notices did not explain what prompted the maintenance or how many customers were affected.

The earlier interruption had also affected a broad set of services. Crypto.news’ report on the first outage said Deribit listed its trading interface, several APIs and data feeds, and crypto transfers among affected components. The report noted that Deribit had not given recovery times for individual transfer routes. Its account was published before the later halt and restart.

Deribit had separately scheduled a deployment for 09:00 UTC that morning and said trading would pause briefly while API gateways restarted one at a time. The status page marked that work complete at 09:15 UTC. The exchange’s public updates do not connect that planned deployment to either later interruption, so the cause of the trading halts remains unclear.

References