What runs on your machines
Where each type of load balancer runs, what the platform keeps, how a failed machine is replaced, and what was measured.
lb11, lb21, lb31
The load balancer is the infrastructure provider's, created in your region with its own IPv4 and IPv6. Deutsche Cloud creates it, registers targets and services at the provider, and deletes it. Health checks and failover inside it are the provider's. A change that the provider refuses is recorded as an event on the load balancer.
application and public dedicated: the region's shared fleet
A region's fleet is a pair of Deutsche Cloud machines running Deutsche Cloud's own proxy. One machine is
active and serves the fleet's shared addresses; the other stands by. The first application or
public dedicated load balancer of a region brings up its fleet (about two minutes). An application load balancer
is served on the shared addresses and told apart by host name; a public dedicated one has an
IPv4 of its own, which moves with the active machine, and an IPv6 from the fleet's range.
- Every machine of the fleet checks every target itself, the standby too.
- Failover. The standby asks to take the addresses over; the Deutsche Cloud control plane decides, and moves them only when its own probes find the active machine down. It does not move them again within 60 seconds of the last move, and a broken link between the two machines alone moves nothing. While the control plane is unreachable, no failover happens.
- A machine that stops reporting is replaced after 15 minutes, or at once when the provider says its machine is not running.
Private dedicated: your organization's pair in the VPC
A private dedicated load balancer runs on a pair of machines of your organization attached to the
VPC's network, never shared with another organization. Each machine holds one of the load
balancer's two VPC addresses, and both serve. Its name (hostname) answers the addresses of the
machines serving now. A VPC's pair holds at most 5 address pairs, shared by the private endpoints
of your databases and other services in that VPC.
What the platform keeps
- The configuration: services, targets, rules, and the web ACL's id.
- Certificates on
applicationanddedicated: the certificate, and its private key sealed under the KMS master key. Reading the load balancer returns each https service's certificate (certificatePem), never the key in the clear. Onlb11–lb31a certificate and its key are at the provider; Deutsche Cloud does not store an uploaded key. - On
applicationanddedicated: the access log (about 20 lines a second per load balancer, bursts up to 200, error lines kept first; kept 7 days; client addresses included) and each machine's counters, reported every 10 seconds.
On your organization's own hosts
When your organization's load balancers run on its own hosts, set up by an operator:
- Only
applicationcan be created; the other types are refused with409and the codeprovider_unsupported. - The load balancer runs on one fleet machine on those hosts, so TLS ends there. Its own name is
under the site's label:
<name>-<id8>.<site>.lb.apps.…. - Instance targets must run on the same hosts (
409otherwise); IP targets must be public. - There is one machine, so there is no failover: a machine that stops reporting is replaced after 3 minutes.
Measurements
Benchmarks of 2026-11-12, over the public path a customer's traffic takes:
application |
lb11 |
|
|---|---|---|
| Requests/s (HTTP keep-alive) | 20,000 sustained, 30,000 burst (enforced cap) | 22,400–23,300 (measured) |
| New TLS handshakes/s | 2,500 (enforced cap) | 2,400 (measured) |
| Concurrent connections | 10,000 (enforced cap) | 10,000 |