Back

Global Load Balancer

Send each visitor of your domain to the right region, by where they are, by the weight you set or by priority, and keep them away from servers whose health checks fail. Global Load Balancer has been in Alpha since November 19, 2026, and is free to use.

Status
Alpha
Category
Network & Security
Access
Early access
Release date

What is Global Load Balancer?

Global Load Balancer uses DNS to distribute your domain's traffic across your regions. The OVHcloud name servers host your zone, and each record of that zone carries a routing policy and, where it needs one, a health check.

The same name then answers each visitor with the region that suits them, and an entry whose health check fails leaves the answer until it is back. Your visitors connect straight to your servers: Global Load Balancer answers DNS queries and never carries their traffic.

How does it work?

  1. Open Global LB. In the OVHcloud Console, select Bare Metal Cloud, Hosted Private Cloud or Public Cloud, then open the DNS section and click Global LB, tagged Alpha.
  2. Create a zone. In the Public zones tab, click Create a Global Load Balancer zone and enter your domain name. The zone is created at once, with no order to place, and receives its name servers.
  3. Point your domain at the name servers:
    1. Your domain is registered at OVHcloud: on the zone page, click Use these servers for my domain.
    2. Your domain is registered elsewhere: at your registrar, replace the domain's name servers with the ones the zone shows.
    3. Testing on a domain in use? Create the zone for a subdomain, such as glb.example.com, then add one NS record per name server for that subdomain in your domain's zone. The rest of your domain keeps answering as before.
  4. Create the health checks, in the Health checks tab:
    1. Choose the protocol: HTTP or HTTPS, with or without a text check, TCP, ICMP or DNS.
    2. Enter the target: the public IP address or the host name of your server.
    3. Choose the test frequency, every 10 or 30 seconds, and the number of failed tests allowed in a row before the server is considered unavailable.
  5. Add the records. In your zone, choose the type, the subdomain and the targets, then the routing policy and, for each entry, its health check. You can also create a health check from the record form. Each change applies right away and reaches every name server within a minute.

The full procedure, with the limits that apply, is in the guide Get started in the Console.

Use cases

Fail over to another region

Keep your service up when a region goes down: the DNS answers with your standby region, with the Failover policy and a health check on the primary.

Serve each continent from its region

Send your visitors in Europe and in North America to the closest healthy region, with the Geolocation or Geoproximity policy.

Roll out a new version

Send 10% of your traffic to a new version, then raise the share step by step, or roll back in one change, with the Weighted policy.

What are the benefits for you?

  • Automatic failover. A server whose health check fails leaves the answer, and comes back when it recovers, without anyone editing the zone.
  • Six routing policies. Simple, weighted, failover, geolocation, multivalue and geoproximity, picked from a list for each group of records.
  • No proxy on the way. Your visitors connect straight to your servers: no extra hop, no TLS to terminate.
  • IPv4 and IPv6. Records carry IPv4 and IPv6 addresses, and health checks accept IPv4 and IPv6 targets.

What's next on the roadmap?

The Beta brings every OVHcloud region, observability features and a Terraform provider.

General Availability adds an SLA and published pricing.

Help shape Global Load Balancer

This Alpha is open to the first 100 customers. We're looking for feedback on real domains, real multi-region setups and real failovers before opening it more broadly. No SLA applies during the Alpha.

How to share your feedback?

Need some help?

Read the guides Get started in the Console, from creating the zone to adding the records, and Routing policies and health checks, to choose how each name answers.

Ready to try it?

Open Global LB in the DNS section of the Console, in Bare Metal Cloud, Hosted Private Cloud or Public Cloud.

Questions, answered.

No. Global Load Balancer is in Alpha, for testing and evaluation only: do not use it for production workloads. OVHcloud reserves the right to close the Alpha, or to suspend the service, at any time. During the Alpha, health checks run from a single location: a network problem between that location and your server can look like a server failure.

For now, the Alpha is limited to the first 100 customers, and OVHcloud will raise this limit progressively.

Yes, Global Load Balancer is free to use during the Alpha and the Beta. Pricing is published at General Availability.

No. As with any OVHcloud Labs product, no SLA applies while Global Load Balancer is in Alpha.

Any server with a public IP address or host name, at OVHcloud or elsewhere. A health check cannot reach a private address, and your firewall must let the checks in.

No. Your domain stays with its registrar: you create a zone for it, then point the domain at the name servers the zone receives.

Not yet. The Alpha is managed from the OVHcloud Console, and a Terraform provider is planned for the Beta.

Shape what ships next.

Join the User Experience Program to test upcoming products, get early alpha and beta access, and put your fingerprints on the roadmap.