Server Infrastructure
Location
Deribit infrastructure is hosted in Equinix LD4 in Slough (UK).
Connectivity options
Traders can connect to the Deribit infrastructure in multiple ways:
IPs and ports
When connecting from the internet or a partner:
-
www.deribit.com (load balanced)
ports:
-
443 - HTTPS
-
9881 - FIX
-
9883 - FIX SSL
When connecting from cross connects and colo connection:
-
Gateway 1: 193.58.254.1
-
Gateway 2: 193.58.254.2
-
Gateway 3: 193.58.254.3
You can only use one of these nodes at a time. Switching to a different HFT node will disconnect your sessions on the previous node. You can only switch after having been connected for at least one second.
Deribit recommends customers to implement a failover mechanism in such a way that if a gateway is down or not performing, your software automatically switches to one of the other gateways.
ports:
-
8020 - HTTP
-
8021 - API
-
8022 - WS
-
8025 - FIX
You can also use www.deribit.com but you will go through our load balancer and will likely have a higher latency than when going through the dedicated IP address.
Details about the connectivity options
Server colocation in the Client Racks
Clients can rent rackspace for £250 + VAT (per rack unit) per month.
Service includes:
-
One hour of smart hands service for installation
-
Hosting
-
Energy consumption
-
50 Mbps ISP
-
Cross-Connect to Deribit
Connecting a server in our colo facilities requires 5 ports:
-
1x UTP for ipmi/idrac/ilo/bmc connection to manage your hardware
-
2x SFP+ connection (10g) to the exchange
-
2x UTP connection to access the internet from your OS
The patch between your server and the exchange is done with 2 10g twinax cables (provided by Deribit). These cables have the exact same length for all of our other colo customers.
Deribit does not procure servers for clients. Clients are not able to add network equipment (e.g. firewall to terminate the internet handoff, switches between several servers, etc). This service requires the signing of a hosting agreement. Therefore, if interested, don't hesitate to get in touch with colo-support@coinbase.com for more information.
Server requirements:
-
2 rack units maximum
-
The server must be of enterprise datacenter quality (not self assembled, no loose parts, etc)
-
The server must be 19” rackmountable using sliding rackrails
-
The server needs to have a redundant PSU
-
Both PSUs must have c14 connectors
-
The server needs to have at least 1 IPMI or ILO port
-
The server needs to have at least 2x10 Gbit SFP+ ports
-
The server needs to have at least 2x1 Gbit RJ45 ports
-
Both the 2xRJ45 ports and 2xSFP+ ports need to be set up in an active-passive bond (or teaming in Windows). We do not support LACP. The static IP addresses for both bonds/teams will be supplied by DRB Hosting after the hosting agreement is signed.
-
Both the RJ45 and SFP+ ports that are being used to connect to our switches have to be labeled. The RJ45 ports for internet access have to be labeled as inet1 and inet2, the SFP+ ports have to be labeled as colo1 and colo2
-
The server needs to have a label with the Client's name
-
The IPMI interface has to be configured with a static IP address supplied by DRB Hosting
-
All network connectivity must be at the hot (back) side of the server
Cross Connects
For cross-connect, we support 10gbit single mode LR only (LC-LC 9/125µm OS2 fiber). Deribit uses 10gb LR transceivers, clients need to use the same on their end. We do not support other speeds than 10gb at this moment. It is mandatory to have a secondary, redundant cross connection.
The crossconnects must be placed using diverse paths through the datacenter. We have 2 demarcation points for the north (blue) and south (red) paths, which go through separate IDFs and MDFs (equivalent to meet-me-rooms (MMRs)) in LD4. It is not acceptable to have both crossconnects go through the same demarcation point because of redundancy reasons. Each of the 2 paths to the Deribit infrastructure lands on a different switch within the Deribit infrastructure. This prevents a single-point-of-failure (SPOF) and enables Deribit to perform maintenance on equipment without affecting your trading. Clients need to configure their BGP setup in such a way that link failures are handled automatically and do not affect your trading.
MMRs are rooms in datacenters where the datacenter connects customers together. These are off-limits to datacenter customers and Deribit has no access nor any control over them.
Cross connects from Deribit’s perspective are currently free. Clients only need to pay the Equinix fees for the setup and connection. If you would like to cross-connect, please get in touch with your Equinix manager to request the service, and please send an email to colo-support@coinbase.com to receive a LOA from us (valid for both the primary and secondary connections).
AWS
See details here: https://support.deribit.com/hc/en-us/articles/25944588342941-Deribit-AWS-Endpoint-Service-instruction
Internet
You can either use our app, our website or our public APIs (documented here: https://docs.deribit.com/#overview)
FAQ
Q: What is the speed difference between the cross-connect and the hosted solution?
A: A cross-connect is a fiber connection from the client equipment, goes via one of the Equinix MMRs and then goes to the Deribit infrastructure. Cross-connect paths can be between dozens and hundreds of meters. If your equipment is in a different building it can be kilometers long. Therefore, the distance to our platform using the colo option is (much) shorter as no MMR is involved. That provides a lower latency and fewer potential failure points.
Q: Is there any equalization/harmonization/normalization of the cross-connect and the hosted solution?
A: Not at this moment. The latency currently depends on the distance to the MMR.
Q: Can the hosted solution also have cross-connects to other locations within LD4?
A: Yes, but the patches to other destinations need to land directly into your server (no switch).
Q: What is the location of the Deribit Matching Engine in LD4?
A: LD4:01:00S14 – Equinix LD4, 2 Buckingham Avenue, Slough, SL1 4NB, UK. Do not send any equipment to this address without getting a unique shipment ID from Deribit first (this is unique per shipment)! Packages are likely to be refused if we have not notified the datacenter up front.
Q: Do I need to provide the SFPs for the colo connection?
A: No, you do not need to provide the SFPs for the trading connections colo1 and colo2 when using the colocation service. However, if you wish to cross connect your server to your own infrastructure, you will need to provide the SFP and ensure a port is available on your NIC.
Q: Are you using NTP or PTP to sync master servers to the pool?
A: We use Precision Time Protocol (PTP) to synchronize our machines. Customers can make use of our PTP service. More information can be found here: https://support.deribit.com/hc/en-us/articles/33768926419229-Precision-Time-Protocol-PTP
Q: Do I need to provide c13-14 power cables?
A: No, we provide these cables.
Q: If I arrange a cross connect from my colo hosted server to my infrastructure, will it also be 10Gbit?
A: This connection does not pass through our network, so the speed is your choice. Just make sure the SFPs are compatible on both ends and the connection is configured accordingly.