Our primary block producer is with Google and our backup is with Azure. Each location will have 2 EOS nodes behind a network load balancers.
CLICK TO ENLARGEOur networking subnets will allow for speeds upto 16Gbps.
Our nodes will be situated behind a Network load balancer that will balance all networking requests between both nodes. The Network load balancer is a pass-through load balancer and makes no changes to any of the TCP packets.
The Google load balancer will also act as our DDOS protection. We have thoroughly tested the abilities of the Google load balancer to handle a DDOS attack.
Our servers will install security updates automatically.
We will employ an external security consultant to carry out bi-annual security audits on our infrastructure.
Our block producers will not allow any incoming connections. This ensures our Block Producers can stay hidden from the internet whilst still synching up to the blockhain and producing blocks.
The EOS processes on our servers will be monitored 24/7 and will include event handlers to automate the restarting of the process.
Further to checking that our EOS processes are running, we will also verify that our nodes & block producers are staying in sync with the blockchain.
We will also monitor the head_block numbers on upto 21 nodes and compare that number against our nodes and block producers to ensure we have not forked onto our own chain.
Any outage notifications that occur on our infrastructure will be captured by our monitoring solution and send over to VictorOps to alert the current on call engineer.
We have a rotating team of 3 engineers monitoring our infrastructure 24/7.
By leveraging our incident timeline we are able to record monitoring data, system actions, and human remediation. Our team can leverage these insights to drive continuous improvement.