Standard
Standard steering policies include Off - Failover and Random.
These are the only steering policies available to non-Enterprise customers who have not purchased Traffic steering.
Failover steering uses the pool order to determine failover priority (the failover order).
Failover directs traffic from unhealthy pools — determined by health monitors and the Health Threshold — to the next healthy pool in the configuration. Customers commonly use this option to set up active - passive failover.
If all pools are marked unhealthy, Load Balancing will direct traffic to the fallback pool. The default fallback pool is the last pool listed in the Load Balancing configuration.
If no monitors are attached to the load balancer, it will direct traffic to the primary pool exclusively.
In an active/standby setup, with two origin pools:
- Traffic always routes to Pool 1 (the primary pool) unless it becomes unhealthy.
- If Pool 1 is marked unhealthy, traffic shifts to Pool 2 (the standby pool).
- Once Pool 1 becomes healthy again, traffic automatically shifts back to Pool 1, assuming no session affinity or other settings require subsequent requests to stay at Pool 2.
This behavior is known as failback and ensures traffic resumes normal routing when the primary pool recovers.
Choose Random to route traffic to a healthy pool at random. Customers can use this option to set up active - active failover (also known as round robin), where traffic is split equally between multiple pools.
Similar to setting Weights to direct the amount of traffic going to each endpoint, customers can also set Weights on pools via the API's random_steering object to determine the percentage of traffic sent to each pool.