Common load balancer configurations
Consider the following sections to understand how to achieve some commonly used load balancer configurations.
Active - Passive Failover
An active-passive failover sends traffic to the servers in your active pool until a failure threshold (configurable) is reached. At the point of failure, your load balancer then redirects traffic to the passive pool.
This setup ensures uninterrupted service and helps with planned outages, but it might lead to slower traffic overall.
To set up a load balancer with active-passive failover:
- Create a load balancer with two origin pools (
- In the list of origin pools, set the following order:
- For Traffic Steering, select .
With this setup, your load balancer will direct all traffic to
primary has fewer available origins than specified in its Health Threshold. Only then will your load balancer direct traffic to
In the event that all pools are marked down, Cloudflare uses the fallback pool, which is the option of last resort for successfully sending traffic to an origin. Since the fallback pool is a last resort, its health is not taken into account, and Cloudflare reports its status as No Health. You can select the fallback pool via the API or in the Cloudflare dashboard. For more on working with fallback pools, refer to .
Active - Active Failover
An active-active failover distributes traffic to servers in the same pool until the pool reaches its failure threshold (configurable). At the point of failure, your load balancer would then re-direct traffic to the fallback pool.
This setup speeds up overall requests, but is more vulnerable to planned or unplanned outages.
To set up a load balancer with active-active failover, either: