All Products
Search
Document Center

Server Load Balancer:What is Classic Load Balancer (CLB)?

Last Updated:May 28, 2026

Classic Load Balancer (CLB) distributes incoming traffic across multiple backend servers based on forwarding rules, increasing application availability and scalability.

Overview

CLB uses a virtual service address to pool backend servers within the same region and distributes client requests based on your forwarding rules.

CLB runs health checks on backend servers and automatically isolates unhealthy ones, eliminating single points of failure (SPOFs). CLB also provides DDoS mitigation.

Components

image
Grayed-out servers have failed health checks and do not receive traffic.

CLB consists of three components:

Component

Description

Instance

A running load balancing service that receives and distributes traffic to backend servers. Each CLB instance requires at least one listener and two backend servers.

Listener

Monitors client requests, forwards them to backend servers, and performs health checks.

Backend server

A compute resource that receives forwarded requests. CLB supports ECS, ECI, and ENI instances as backend servers, managed individually or in batches through vServer groups or primary/secondary server groups.

Benefits

  • High availability

    Fully redundant architecture with no single points of failure. Supports intra-city disaster recovery.

    Scales elastically with traffic to maintain availability during load fluctuations.

  • Scalability

    Add or remove backend servers at any time to match capacity with demand.

  • Cost-effectiveness

    Significantly reduces fixed costs compared with traditional hardware load balancers.

  • Security

    Integrated with Alibaba Cloud Security, CLB provides up to 5 Gbps of DDoS protection.

  • High concurrency

    Supports up to one million concurrent connections per instance.

Accessing CLB

You can access and manage CLB through the following methods: