Server Infrastructure
Deribit infrastructure is hosted in Equinix LD4 in Slough (UK). Traders can connect to our infrastructure in multiple ways:
You can still use www.deribit.com from the hosted servers. However, this traffic will be routed through the load balancer. You may consider using a direct connection as a better connectivity option.
The connection of the cross-connect will be done through BGP. Deribit will provide different /24 subnets from the 172.16.0.0/12 block to establish the connection to third parties. Details of the BGP peering will be provided once a cross-connect is requested.
IP & Ports:
-
www.deribit.com (load balancer)
-
443 - HTTPS
-
9881-FIX
-
9883-FIX SSL
Colo connection:
-
8020 - HTTP
-
8021 - API
-
8022 - WS
-
8025 - FIX
Hosting in the Client Rack
Clients can order a server for £250 + VAT (per rack unit) a month.
Service includes:
-
One hour of smart hands service for installation
-
Hosting
-
Energy consumption
-
50 Mbps ISP
-
Cross-Connect to Deribit
The patch will be done with a Twinax cable. These cables have the exact same length for all of our customers, and are rate limited to 1 Gbit. Deribit offers a primary and a secondary link. Therefore, two available ports are needed to cross-connect to our infrastructure. Patches to other destinations need to land directly into the client's server (no switch). Deribit will not procure clients' servers.
Clients are not able to add network equipment (e.g. firewall to terminate the internet handoff). This service requires the signing of a hosting agreement. Therefore, if interested, don't hesitate to get in touch with support@deribit.com for more information.
Server requirements:
-
2U Maximum
-
The server must be of proper 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 with 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 will not support LACP. The static IP addresses for both bonds/teams will be supplied by DRB Hosting
-
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
-
Network connectivity must be at the hot (back) side of the server
Cross Connects
For cross-connect, we recommend an LC-LC 10 Gb 9/125µm OS2 fibre connection. The cross-connect should be a 10-gigabit cross-connect. Deribit will use policing on its switch to have an effective speed of 1-gigabit. It is mandatory to have a secondary, redundant cross connection.
Cross connects from Deribit's perspective are free. Clients only need to pay the Equinix fees. If you would like to cross-connect, please get in touch with your Equinix manager to request the service, and please write at systems@deribit.com to receive the LOA (valid for both the primary/secondary connection).
FAQ
Q: What is the speed difference between the cross-connect and the hosted solution?
A: Cross-connect from the client rack links to the Equinix meet me room (MMR) and the Deribit matching engine. Therefore, the distance using the hosted solution to our platform is shorter as no MMR is involved.
Q: Is there any equalization/harmonization/normalization of the cross-connect and the hosted solution?
A: No, latency 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
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 are currently using open-source NTP to synchronize our production master to the pool. PTP is under development for production use and is expected to offer higher accuracy and precision, but there is no confirmed rollout date yet.
Q: Besides C13 power cables, do I need to provide any other cables or fibres?
A: No, all other cables and fibres required for colocation and cross-connect services are provided as part of the service.
Q: Will the cross connect from my server to my infrastructure also be 10 Gbit?
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.
Comments
0 comments
Article is closed for comments.