A: No. All colocation customers must use exactly the same brand, type, and length of cable — no modifications or alternative cable configurations are permitted. Deribit provides all required cables as part of the colocation service. This policy ensures equal treatment for all customers and eliminates any possibility of one customer gaining a connectivity advantage over another.
Q: How many IP addresses are allocated for my colocation connection?
Registering and Logging In to the Testnet
To use the Deribit Testnet, you’ll need to create a separate testnet account at https://test.deribit.com. Testnet accounts are completely independent from production accounts—none of your settings, credentials, balances, or API keys are shared between the two environments.
Warning
Verification is not required on the testnet. Please do not upload any documents in the verification section, as this environment is intended for testing purposes only.
-
Registration: The registration process is the same as on the production enviroment. For detailed steps, see: How to register on Deribit
-
Login: After registering, log in at https://test.deribit.com using your testnet credentials. For help with login issues, refer to: Logging in to your Deribit Account
A: One IP address is provided by default for connecting to the HFT infrastructure. Connections are configured as an active/backup bond — active-active bonding is not supported.
-
Q: If there are multiple HFT nodes, do they all connect through the same network switch?
-
A: Yes. All colo connections terminate at the same switch, which is in the same rack as the colo server. The different HFT nodes are accessible via separate IP addresses, but the physical network termination point is the same switch for all customers.
-
Synthetic Funds: Users can freely generate test funds, which removes real-world risk and distorts realistic trading behavior. See Depositing test funds to your testnet account for more details.
-
Network and Infrastructure: The test environment is completely separate from the production infrastructure. This includes colocation, cross-connects, and latency-sensitive connections, which are not available or represented on testnet.
-
KYC and Identity Verification: KYC processes are not supported on the testnet environment.
-
Additional Coins: The testnet may offer trading pairs or assets not present on the production platform.
Note
While some new features may be tested on https://test.deribit.com which are not yet available on https://www.deribit.com, the bulk of components and API endpoints should function very similarly, if not identically.
Caution
The testnet environment may be taken offline at any time and without prior notice for maintenance, updates, or internal testing by Deribit’s technical team. Maintenance schedules and downtimes are not announced in advance for the testnet.
-
Rate Limits: Both the production and test environments use the same default Rate Limits
-
Latency and Infrastructure: Both environments are hosted in LD4 and follow similar network paths. While no formal latency comparison has been made, significant differences are not expected. See Server Infrastructure for more details.
Note
The testnet is accessed only via the public API—it does not provide access to the high-frequency trading (HFT) infrastructure available in production.
-
Hardware: The testnet runs on less powerful hardware than production, but due to significantly lower traffic, performance is typically sufficient for development and testing.