Home
CDN
Load balancers

Load balancers

Multiple servers. One address.

Spread requests across multiple servers – for websites and APIs over HTTP(S), or any service over TCP and UDP. If a server fails, the CDN removes it automatically and lets you know.

Create a load balancer See features

Free plan, forever
no credit card required
set up in minutes

with WebSockets: HTTP(S)
for custom protocols: TCP/UDP
check interval: 15 sec
servers per service: 10

Two kinds

For the web. And for everything else.

HTTP(S) load balancer

For APIs, apps and dynamic websites: an address like api.your-domain.com, HTTPS with a certificate, WebSockets and all CDN protection features – without caching, responses stay unchanged.

TCP/UDP load balancer

For databases, games, VoIP or custom protocols: a port between 30000 and 39999 on all edges, with your own name like db.your-domain.com.

For websites and game servers too

Every website and game server in the CDN can also have up to 10 servers – with the same distribution and checks.

Distribution

You decide who gets what. The CDN keeps watch.

Round robin

In turn, by weight – double the weight gets twice as many requests.

Least connections

To the server with the fewest open connections – good for requests of very different length.

Sticky per visitor

The same IP always lands on the same server – for shops and logins whose session lives on one server only.

Backup servers

Only step in when no active server responds.

Pause for updates

Pause a server, update it, reactivate it – visitors don’t notice a thing.

Automatic checks

If a server doesn’t respond, the request goes straight to the next one. On top, the nodes check every 15 seconds – if most report a failure, the CDN removes the server and notifies you.

Example

A database behind the CDN. In three steps.

1
Create the load balancer
Enter name, protocol and servers – the CDN assigns a port between 30000 and 39999, the same on every edge.
2
Set your own name
If the domain is in the CDN’s DNS, db.your-domain.com points to the edges automatically. Otherwise, a CNAME to the personal address.
3
Connect
Clients use your name and the port. Your server gets the real client address via the PROXY protocol.

Example: PostgreSQL

$ psql "host=db.your-domain.com port=31234 user=app"

# same port on every edge –
# failed servers are removed by the CDN

Create a load balancer

FAQ

Questions about load balancers? Answered briefly.

Detailed guides are in the help center.

What’s the difference between a website and an HTTP(S) load balancer?

A load balancer is a website without caching: every request goes to your servers and responses stay unchanged. Protection features, rules, statistics and multiple servers are available for both.

Does my server see the real client address?

With HTTP(S) in the X-Real-IP header. With TCP via the PROXY protocol – your service has to support it, e.g. HAProxy, Nginx or Minecraft proxies.

Are there limits?

Ports for sending email (25, 465, 587, 2525) aren’t possible. TCP connections may idle for 10 minutes, UDP sessions for 60 seconds.

Can I use devices at home as servers?

Yes. Two Raspberry Pis on different connections as a pool – if one fails, the other takes over. More on the devices page.

Get started

Protected in minutes. Start for free.

Free plan, forever · no credit card required · set up in minutes

Start for free All CDN features