Round robin
Round RobinRequests cycle through servers in order: first to server 1, second to server 2, third to server 3, then repeat. The simplest choice for similarly sized servers.
ExampleSix consecutive requests
A Load Balancer provides one entry point for your service and distributes requests across multiple cloud servers.
Request routing
2 servers are healthy. Requests reach only these servers; unhealthy servers are excluded.
Select a server to see how routing responds.
Choose one of two methods when creating a load balancer. Every listener has its own protocol and port.
Requests cycle through servers in order: first to server 1, second to server 2, third to server 3, then repeat. The simplest choice for similarly sized servers.
ExampleSix consecutive requests
Each request goes to the server with the fewest active connections. This balances load better when requests take different amounts of time.
ExampleActive connections per server; the next request goes to server 2
Each listener defines the incoming protocol and port and the target server port. Web listeners can also enable automatic HTTPS redirects and TLS encryption.
808080443808054325432The load balancer checks target servers regularly. After repeated failures, it stops sending new requests to an unhealthy server while the others continue serving traffic.
A server's health check results
Everything happens from the project page.
The load balancer connects to one of your project's private networks.
Enter the listener type (HTTP, HTTPS or TCP) and ports, and choose one of the two balancing methods.
Select the cloud servers in your project that should receive requests.
Set check path, interval, timeout and failure threshold. You can edit servers and settings later.
The load balancer connects to a project private network, with your cloud servers behind it. Requests enter through one endpoint and are distributed across servers.
The main capabilities of Load balancer at a glance.
Choose the incoming protocol (HTTP, HTTPS or TCP) and port.
Select the servers that should receive requests.
Manage load balancer settings and status within your project.
Services commonly used alongside Load balancer.
An isolated internal network connecting each project's servers
Choose who can access your servers and from where
Virtual servers you create in the panel and pay for hourly
When every request reaches one server, increasing traffic puts it under pressure and adding another server becomes cumbersome.
Load balancer supports use cases such as Services with multiple servers, High-traffic websites, Decouple the entry point from servers. The right choice depends on your project's technical and operational requirements.
Read the product guide and estimate costs in the calculator, then create the service in your chosen project in the client panel.
Register, estimate costs before provisioning and pay hourly for the time you use the service.