Server racks with yellow network cabling illustrating shared trading infrastructure

Deribit Outage Exposes a Hidden Coinbase Hedging Bottleneck

• November 22, 2026 11:18 am • Comments

Two Deribit trading interruptions have exposed a weakness many Coinbase derivatives traders may not realize they share: changing the front end does not necessarily change the exchange underneath the order.

Bitcoin and Ether perpetual traders using Coinbase’s global derivatives products and customers trading directly through Deribit were relying on the same Deribit order book. When that venue stopped matching orders, switching between those two interfaces did not create an alternate route.

Deribit shows trading became unavailable twice on November 20—first at 16:17 UTC and again at 19:28 UTC. The affected components included BTC-PERP, ETH-PERP, the direct trading interface, FIX connections, REST and WebSocket services, market data and execution reporting.

The first interruption lasted about 19 minutes before trading resumed under monitoring. The second disruption was longer, with a pre-open announced for 21:25 UTC and the restart planned five minutes later.

Deribit reported trading live at 21:31 UTC. Bitcoin and Ether returned to normal limits at 22:02 UTC, while some lower-tier instruments and real-world-asset products remained rate-limited until the final caps were lifted at 22:31 UTC.

A scheduled deployment had completed at 09:15 UTC, hours before the failures. The status notices did not identify that deployment as the cause, so the timeline supports no stronger conclusion.

Hours before the interruptions, Deribit highlighted roughly $2.47 billion in Bitcoin and Ether options scheduled to expire that day. That figure shows the scale of positioning running through the venue when reliable execution matters most.

CryptoSlate explains why the Coinbase connection matters. Coinbase moved its eligible global perpetual contracts from the former International Exchange to Deribit in October.

Coinbase customers could keep placing orders in familiar Coinbase interfaces, but those orders were routed to Deribit for matching.

That arrangement can make access feel diversified while execution remains concentrated. A trader might see two brands, two websites and two account experiences, yet still face one order book and one outage domain.

The report said individual access depended on product eligibility and account setup, and the incident notices published no customer fill data. That means the public record shows the execution bottleneck clearly without establishing how many positions were delayed or how much slippage any trader experienced.

It also noted that Deribit routed spot orders through Coinbase Exchange, adding another layer to the relationship between the companies. The affected-services list included BTC-USDC and ETH-USDC, but it did not establish whether every customer could bypass those pairs through Coinbase’s spot venue during the disruption.

Coinbase said its U.S. derivatives business was unaffected. Eligible and funded institutional clients could potentially use U.S. futures to offset some price exposure while Deribit was unavailable.

But that did not solve every problem. Closing or resizing the original perpetual still required access to Deribit.

The contracts, margin setup and account eligibility also differ, so a separate U.S. futures venue is not the same as instant failover for every global perpetual position.

Deribit had recently promoted work on its matching-engine infrastructure, underscoring how central that machinery is to the venue’s operation.

The status timeline says a scheduled deployment finished earlier that morning, but the public notices do not establish that it caused the later interruptions. The venue restored trading, briefly imposed rate limits on some instruments, and then reported the remaining caps lifted by 22:31 UTC.

Interface redundancy and venue redundancy are different things. If two order screens ultimately depend on the same matching engine, the hedge is only as available as that shared engine.

Join the conversation!

We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.