DO Load Balancer limits

Posted December 19, 2019 3.4k views
Load BalancingDigitalOcean Managed Load Balancers


My service may keep connections (TCP) alive for a few minutes. I have read that there is a limit of 60 seconds and 10k connections. My questions are:

  • Will the TCP connections to my service be closed after 60 seconds?
  • What happens after my service is handling 10k connections? I.e.: what happens with the 10001 attempt to connect?

Thanks in advance

edited by bobbyiliev

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers
  • Keepalive doesn’t mean that the connection will get closed after 60 seconds, it means that the connection will get closed after 60 seconds of inactivity.

  • The 10001th connection will not be accepted - the user will get timed out.

Hi @arstoykov
Is the 10k concurrent user limit still in place?
We are developing a social network with a realtime chat and we need to be able to have many users connected using websockets.
When a new user connects to a domain pointing to the loadbalancer does every socket message go throw the loadbalancer and it counts as an active connection or does the user go directly to the droplet after the connection is established?

  • I think the limit still stands. Every connection stays on the load balancer, yes. It can be done the way you want it (go straight to the droplet), but not with DO’s load balancer. You’ll need a custom implementation for this.