Perpetual futures (inverse and USDC-margined linear). The first notification per instrument is a full book (no prev_change_id); later ones are 100 ms batches of [new|change|delete, price, amount] with absolute amounts.
Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.
Open live books Replaywss://www.deribit.com/ws/api/v2https://www.deribit.com/api/v2/public/get_order_book?instrument_name={SYMBOL}&depth=100BTC-PERPETUAL{"jsonrpc":"2.0","id":1,"method":"public/subscribe","params":{"channels":["book.BTC-PERPETUAL.100ms","book.ETH-PERPETUAL.100ms",...]}}
Affected raw channels include book raw subscriptions (merged changes with an unbroken prev_change_id/change_id chain), quote.{instrument_name} (latest value only), trades.{kind}.{currency}.raw (trades batched together) and raw order channels (only the last order state in the window). A quiet channel still sends the next change immediately. Merged notifications could already occur under very high load. Clients that treat each notification as a complete update need no change, and should not rely on seeing every intermediate state. Our handler uses the 100ms book channel, not raw, so impact is likely limited.
Our handler: The change targets raw subscriptions, while our handler uses book.<instrument>.100ms, which is not listed as affected, though raw book change_id chaining is mentioned.
The new limit is shared across the listed ticker and order book methods. It comes on top of the default non-matching engine limit of 20 requests per second (burst 100), so each call counts against both. The page text does not list the methods (the list appears to be missing from the text), but get_order_book is likely among them. Clients should reduce polling, such as REST snapshot requests, and handle error 10028 with backoff. Deribit recommends subscribing to WebSocket channels instead of polling.
Our handler: Our REST snapshot uses public/get_order_book, which is likely among the order book methods covered by the new 5 req/s limit, though the source text does not name the methods.
This applies to all futures and options open interest regardless of how trades were executed, even when no trades were delayed. Affected: public/ticker, ticker.{instrument}.{interval}, get_book_summary_by_instrument/currency, public/get_order_book, get_order_book_by_instrument_id and incremental_ticker. Our handler uses get_order_book snapshots, so open_interest there is now 8 hours stale. Do not treat it as real time.
Our handler: The public/get_order_book REST snapshot we use returns open_interest, which is now delayed by 8 hours.
volume = volume_realtime + volume_delayed. Delayed volume covers Block RFQ trades executed 32 to 8 hours ago. Matching _usd and _notional breakdown fields were added to the stats object of ticker, book summary and get_order_book responses and incremental_ticker. No action is needed unless you compare volume with your own trade-based totals.
Our handler: The stats object in public/get_order_book snapshots gets new volume fields and volume semantics change.
Delayed trades are omitted from public trade history and from the trades.* and block_rfq.trades channels until published. Once published they keep their original timestamp and trade_seq, and are never applied to last_price or 24h high/low. Our handler uses only the order book channel, so it is not directly affected. Any trade-based logic should tolerate out-of-sequence trades.
Our handler: Concerns trades.* channels and trade queries, not book.<instrument>.100ms, though last_price in snapshots is unaffected by delayed trades.
Applies to public/get_tradingview_chart_data and chart.trades.{instrument}.{resolution}. Chart prices are unaffected, as before.
Our handler: Chart endpoints and channels are not used by our book handler.
Both bounds are inclusive and matched against the UTC date of each delivery. records_total reflects the filtered set.
Our handler: Delivery prices endpoint is not used by our handler.
Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.