Loading
Preparing infrastructure view...
Traffic spread across instances, without running a balancer
A managed balancer in front of your instances, with health checks that take a sick backend out before your customers find it.
What it is
Load balancing, in plain terms
A managed balancer in front of your instances, with health checks that take a sick backend out before your customers find it.
Layer 4 and layer 7
TCP pass-through or HTTP routing with paths and hosts.
TLS termination
Certificates managed for you, or bring your own.
Health checks
Backends removed and returned automatically.
Traffic visibility
Requests, errors and latency in the portal.
How it works
Load balancing, in plain terms
- 01Traffic hits one addressRather than pointing users at a specific machine
- 02It is spread across serversSo no single one is overwhelmed
- 03Sick servers are removedAutomatically, before your users notice
- 04They come back when healthyAlso automatically, once checks pass again
In the field
Load balancing in the field
What this looks like once it is running, on our own footprint.
Detail
What is included
| Modes | TCP and HTTP/HTTPS. |
|---|---|
| TLS | Managed certificates with automatic renewal. |
| Session handling | Round robin, least connections, or sticky sessions. |
| Health checks | Interval, threshold and path configurable per pool. |
| Billing | Flat monthly per balancer, bandwidth included. |
Watch
Watch: load balancing in the portal
Watch
FILMFilm Load balancing walkthrough · 1:10
Support
Common questions
Is there a minimum term?↓
No. Billing is monthly and you can leave at the end of any month.
Can I move an existing workload across?↓
Yes, and we will help. Larger migrations are handled as a small piece of design work.
Where does the data sit?↓
In our Tier 4 facility, with residency evidence if your regulator asks.
Next step
Tell us what you are building and we will tell you what it needs.
An hour with our engineers, no charge. Bring a floor plan, a workload, or just the problem.