⚠️Expected downtime: 15 - 30 minutes
Client impact: Maintenance 9 AM UTC - The system will be down for around 15 - 30 minutes. Client systems will not be able to communicate with Deribit during this time.
Equinix LD4 Cross-Connect Equalization
Deribit and Equinix are undertaking a project to equalize all existing cross-connects within the Equinix LD4 facility starting in June. This migration is designed to ensure fairness and equal access by providing a standardized connectivity architecture for all clients. By removing intermediate MMR and panel hops, we are harmonizing the physical path lengths across the facility to provide a level playing field for all participants.
What is changing?
-
Equalization: All existing cross-connects in Equinix LD4 will be equalized.
-
Migration Method: A-side and B-side connections will be migrated separately to minimize disruption.
-
New Architecture: The equalization removes intermediate MMR and panel hops on the Equinix side. The connection will utilize a set of spools and two patch panels within the Deribit infrastructure before terminating at Deribit's edge switches.
-
Cost: Deribit will bear all costs associated with this migration.
Required Action
-
No new LOA is required.
-
No action is required on the client side other than verifying the connection is operational after each migration window.
Timeline and Communication
-
Start Date: June 2026
-
We will assign a specific maintenance window for each of the connections and communicate it to the clients in advance.
Support
For any questions or scheduling concerns, please contact the colocation support team at colo-support@coinbase.com.
Breaking Change - MMP Configuration Time Limits
MMP configuration interval and frozen_time parameters are now capped at a maximum of 3,600 seconds (1 hour).
Warning
This change affects existing configurations. Existing configurations exceeding this limit will be automatically migrated to the maximum allowed value.
Instrument Creation Notification Channel
New public subscription channel instrument.creation.<kind>.<currency> delivers a single notification with full instrument data (same format as public/get_instruments) when an instrument is created. The notification fires once at creation time, regardless of the instrument's initial state.
Subscription examples:
|
Channel |
Description |
|---|---|
|
instrument.creation.any.any |
All instruments |
|
instrument.creation.future.BTC |
BTC futures only |
|
instrument.creation.option.any |
All options |
Main Account Trade Query Access
Main accounts are now permitted to call the following methods to retrieve subaccount trade data :
To retrieve trades for a specific subaccount, use the subaccount_id parameter.
Direct Access Status in Account Summary
is_direct_access_allowed field has been added to the response of private/get_account_summary.
Idempotent Subaccount Transfers
Optional nonce parameter has been added to private/withdraw and private/submit_transfer_between_subaccounts for idempotency. Duplicate requests carrying the same nonce will be rejected. The nonce is persisted on the transaction record and returned in the response.