Network

It would be great to have global load balancer so we can do direct traffic to nearest region where we have deployed our http/https service.

We should be able to add Alerts / Notifications for Health Checks similar to RAM and CPU Alerts

You should improve your load balancer to support higher session rates (especially with SSL). We would be happy to pay extra money (e.g. $40, $80, $160, etc.) to have load balancers with high performance. Currently this is a huge problem for us: we cannot scale. At the moment your load balancers are a bottleneck and cannot handle more than 1,000 requests / s (without keep alive and with SSL enabled). The same limit of 1,000 requests / s also applies to custom installations of HAProxy on DO... probably your hardware is not optimized for SSL and scaling the droplet / processes doesn't solve the issue.

Thank you for adding support for HTTP/2 for load balancers and adding Let's Encrypt for specific domains. Thats huge. If you can add wildcard certificate support, that would be amazing. Thank you!

Now the final specification of TLS 1.3 has been published and all major browsers support it, DO load balancers should support this protocol too. Work around would be to do the SSL offloading on your application servers, and with the recent proxy protocol this will work well, but it's easier to let the load balancers handle the SSL offloading.

The health check does not support HTTPS. The load balancer health check supports TCP ports and HTTP service but not HTTPS. In my case, all http traffic is denied or redirected with a 301 to HTTPS, so the load balancer always gets a 301 and assumes the server is okay even if the HTTPS request responds with a 500.

When using a TCP load balancer it would be still useful to know the the IP address the original address came from. HAProxy has a PROXY protocol which is sent to the downstream server with IP information when a new client connects before sending proxying any data.