Networking · Load Balancer
One address, many servers.
Put a managed load balancer in front of your VPS fleet. It takes traffic on a public IPv4 address, checks your servers are healthy and spreads requests across them — from $52.27 per instance / month.
Managed load balancers.
Every location in the catalogue today.
One address for your service
A public IPv4 address that stays put while servers come and go.
Health-checked backends
A server that stops answering is taken out of rotation.
Choose how traffic spreads
Round robin, least connections, or source IP for sticky clients.
Any ports you need
Listen on the ports you choose and forward to each server’s own port.
Plans and locations
Each data center's own price per load balancer, billed hourly.
When to use a load balancer
Where one address in front of several servers pays off.
Scale a web app
Run the same app on several VPS and put one address in front.
Survive a server failure
Keep serving while one backend is rebooted, patched or replaced.
Zero-downtime deploys
Roll new versions out server by server behind a stable address.
APIs and microservices
Spread API traffic evenly with least-connections balancing.
Session-sticky apps
Keep each client on the same backend with source-IP balancing.
TCP services
Balance any TCP service, not only HTTP — databases, queues, game servers.
How it works
From order to live traffic in three steps.
Create the load balancer
Pick the data center and the balancing method.
Add your servers
Choose running VPS in the same data center and the port each listens on.
Point DNS at it
Send traffic to its public IPv4 address once it is ready.
Supported providers
1 provider in 1 country offers load balancers today, with more joining as the network grows.
-
Cloudscale
Frequently asked questions
What teams ask about load balancers.
Keep your service up when a server isn’t.
Put a load balancer in front of your servers and pay by the hour.