Segal Load Balancers

Distribute incoming traffic across healthy application backends with protocol-specific listeners.

The supported upstream service is Public Cloud Load Balancer. Segal supplies the branded application and support boundary; activation depends on the approved customer configuration and applicable provider terms.

Request and resource flow

1. Create the regional load balancer and listener.
2. Register backends and configure health checks.
3. Bind the application hostname and test failure behavior.

Configuration responsibilities

• Listeners, pools and health monitors are separate resources.
• TLS termination is configured for the selected protocol.
• Backend readiness determines whether a target should receive traffic.

Supported scope

Regional load balancers with listeners, pools and health checks. Protocol and TLS support follow the configured product.

• L4 and L7 behavior depend on the selected load-balancing product.
• A healthy TCP port does not establish application correctness.
• Session persistence and client-IP handling need explicit configuration.

Read your organization’s inventory

Open the Load Balancers workspace after signing in. The server resolves your active organization and its allowed OVHcloud resources. It does not accept a provider project ID from the browser.

The authenticated endpoint is GET /api/infrastructure/loadbalancers. Supply an allowed region where needed, and a zero-based page for inventory pagination. Each response reports the requested region and the next page when one exists. Project-wide inventories may contain resources from more than one region; an unreported resource region is not inferred from a seed catalog.

The endpoint uses the Segal browser session. Demonstration sk_segal_ keys do not grant production access. Provider credentials stay server-side. A missing connection returns an explicit error rather than sample resources.

Ordering and changes

New orders and configuration changes for this service are engineering-assisted. The workspace reads authorized provider inventory; it does not imply an automated purchase or provisioning workflow. Request a configuration review before committing to a plan.

Activation and service evidence

Follow provider setup before enabling live access. Demo resources, website imagery and documentation examples do not verify capacity, certification, latency or delivery. Confirm regional availability, contract scope, recovery ownership and final customer pricing before production use.

Read the product architecture. Upstream technical reference: Public Cloud Load Balancer (reviewed 24 October 2026).