Segal Load Balancers
Distribute incoming traffic across healthy application backends with protocol-specific listeners.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Regional load balancers with listeners, pools and health checks. Protocol and TLS support follow the configured product.
- 1
Create the regional load balancer and listener
- 2
Register backends and configure health checks
- 3
Bind the application hostname and test failure behavior
Service architecture
- 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
Operating boundaries
- 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
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Public Cloud Load Balancer. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference