Cloud load balancer: VPS traffic distribution and health checks

Load balancer 1 with one node is $4.71 per month, load balancer 3 with three nodes $14.12 per month, and load balancer 5 with five nodes $23.54 per month. HTTP, HTTPS and TCP distribution, automatic health checks and free certificates are all included in the price, and target servers are billed separately at each VPS's price.

Load balancer 1 groups up to 10, load balancer 3 up to 50 and load balancer 5 up to 100. Start with two or three servers and load balancer 1, then move to a bigger type when you pass 10 servers, to scale while saving costs. Target servers are billed separately at each VPS's price.

A load balancer groups servers in the same region as targets. Connecting servers within the same city keeps the distance requests travel short, so responses are fast. If you serve users in several countries, a set of servers and a load balancer in each region is the right setup. With the same setup in each region, users get fast responses from servers in their nearby region.

The load balancer keeps checking each target server for responses on a set address or port. Servers that do not respond are temporarily taken off the list and receive no requests, and return automatically when they respond again. Even during server restarts or updates, users get healthy responses from other servers. Operators just look into the unresponsive server and put it back on the list.

Attach a free certificate to the load balancer and it handles encrypted connections with users while passing requests to the servers behind it. There is no need to install or renew certificates on each server, so no certificate work is needed when you add or change servers. Target servers focus only on handling requests, and encrypted connection management is done in one place.

Yes, choose TCP mode and non-web services are split too. Spread services that accept connections on set ports, such as game servers, chat servers and message relay servers, across several servers, with health checks working the same way. Set the port and users connect at a single load balancer address while connections are spread evenly across the target servers.

Target servers can be any of regular cloud VPS, high-performance NVMe VPS or dedicated CPU VPS. Keep servers with the same role on the same specs and operating system and requests are handled evenly. Create them with one-click apps to prepare several identically configured servers quickly. Choose from 12 operating systems.

Pay with 12 cryptocurrencies. When you create a server, pay the exact amount, and renew at the same price on each renewal date. Refunds go back to your account credit. Servers and load balancers can be managed together.

A load balancer renews each month when you pay the next invoice. If it is not paid by the end of the period it is suspended, and paying within 3 days brings it back. After 3 days it is deleted, so renew your load balancer, the entry point of your service, before the period ends.

Yes, grouping servers in the same region with a private network and putting a load balancer in front is the cleanest setup. The load balancer receives user connections, and connections between web servers and database servers run over internal addresses, keeping your server setup simple. The private network is free within the same region, so you can build this structure at no extra cost.