> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.co.in/docs/network-security/load-balancer/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.co.in/_mcp/server.

# Load Balancers

> Distribute traffic across multiple backends with L4 and L7 load balancers on IBEE Solutions — health checks, routing algorithms, and TLS termination.

An IBEE Solutions Load Balancer distributes incoming traffic across multiple backends so your application stays available when a single server fails or is overloaded. Each load balancer gets a stable endpoint (host and port) that you point your clients or DNS at; the load balancer forwards traffic to healthy backends only.

## Layers

Choose the layer when you create the load balancer:

| Layer                | Protocols            | Use for                                                                                                    |
| -------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------- |
| **L7** (application) | HTTP, HTTPS          | Web apps and APIs — path- and header-based routing, sticky sessions, TLS termination                       |
| **L4** (transport)   | TCP, TLS passthrough | Databases, message queues, custom TCP protocols, or end-to-end encryption where the backend terminates TLS |

## Capabilities

| Capability         | Details                                                                                                                                                         |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Backends           | Route to a `service`, an `ip`, or a `hostname` target — each with its own port and weight                                                                       |
| Routing algorithms | `round_robin`, `least_request`, `random`, `consistent_hash` ([Algorithms](/docs/network-security/load-balancer/algorithms))                                     |
| Health checks      | Active HTTP, HTTPS, or TCP checks with configurable thresholds ([Health checks](/docs/network-security/load-balancer/health-checks))                            |
| TLS                | Managed certificate termination on L7 HTTPS, or TLS passthrough on L4 ([SSL and TLS termination](/docs/network-security/load-balancer/ssl-and-tls-termination)) |
| Sticky sessions    | Header-based session affinity on L7                                                                                                                             |
| Retries            | Automatic retries on `5xx`, connection reset, and connect failure                                                                                               |
| L7 rules           | Priority-ordered path-prefix and header-match routing rules                                                                                                     |
| Proxy protocol     | Forward client connection metadata so compatible backends see the original client IP                                                                            |

## Endpoint

After creation, the load balancer's detail page shows its public endpoint — **Host**, **Listener port**, and the full **Public host** URL. Point your application or a DNS record at this endpoint.

## Manage load balancers

The portal does not support editing a load balancer after creation. To change backends, routing, health checks, or any other setting, delete the load balancer from the list and create a new one ([Create a load balancer](/docs/network-security/load-balancer/create-a-load-balancer#delete-a-load-balancer)).

## Related pages

* [Create a load balancer](/docs/network-security/load-balancer/create-a-load-balancer)
* [Attach VMs as backends](/docs/network-security/load-balancer/attach-vms)
* [Health checks](/docs/network-security/load-balancer/health-checks)
* [Firewalls](/docs/network-security/firewalls)

> Distribute traffic across multiple backends with L4 and L7 load balancers on IBEE Solutions — health checks, routing algorithms, and TLS termination.

## Docs

- [Create a load balancer](https://docs.ibee.co.in/docs/network-security/load-balancer/create-a-load-balancer.md): Create an L4 or L7 load balancer on IBEE Solutions — choose a protocol, add backends, set the routing algorithm, and configure health checks.
- [Algorithms](https://docs.ibee.co.in/docs/network-security/load-balancer/algorithms.md): Choose how an IBEE Solutions load balancer distributes requests — round robin, least request, random, or consistent hash — and when to combine them with weights and sticky sessions.
- [Health checks](https://docs.ibee.co.in/docs/network-security/load-balancer/health-checks.md): Configure active HTTP, HTTPS, or TCP health checks on an IBEE Solutions load balancer so traffic only reaches healthy backends.
- [SSL and TLS termination](https://docs.ibee.co.in/docs/network-security/load-balancer/ssl-and-tls-termination.md): Terminate HTTPS at an IBEE Solutions L7 load balancer with a managed certificate, or pass TLS through untouched on L4 for end-to-end encryption.
- [Attach VMs](https://docs.ibee.co.in/docs/network-security/load-balancer/attach-vms.md): Point an IBEE Solutions load balancer at your Cloud VMs or GPU VMs by adding them as IP or hostname backends.