In early February, we released Elastic IP address support on our
ch-gva-2 zone. Today we are happy to announce that Elastic IPs are
available globally and can be attached to instances on the ch-dk-2
zone as well.
Elastic IP addresses are bound to a specific zone, and must be allocated on the zone which will bear them. To support geo-redundant scenarios, we encourage you to provision at least one Elastic IP address per zone and use DNS round-robin records through our DNS service.
Our existing documentation as well as our detailed guide on how to set-up automatic failover with HAproxy of course still apply.
Under the covers, our Elastic IP address functionality sits on top of our internal Software Defined Network stack which will be used to provide Private Network, IPv6, and Load Balancing features throughout this year.