Load Balancing provides several traffic steering modes, which allow customers to optimize how load balancers route traffic. You can configure Traffic Steering from the Load Balancing dashboard, in either the Create a Load Balancer wizard or the Edit Load Balancer panel. You can also configure Traffic Steering via the Cloudflare API. Available steering options include standard failover (steering disabled), Dynamic Steering, and Geo Steering.
Standard failover directs traffic from unhealthy pools to the next healthy pool in the configuration.
Standard failover uses the pool order to determine failover priority (the failover order).
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.
To nominate a specific fallback pool via the Cloudflare API, use the Update Load Balancers command and set the
fallback_pool parameter. See Load Balancers for details.
If no monitors are attached to the load balancer, it will direct traffic to the primary pool exclusively.
Dynamic Steering uses health check data to identify the fastest pool for a given Cloudflare Region or point of presence.
Dynamic Steering creates Round Trip Time (RTT) profiles based on an exponential weighted moving average (EWMA) of RTT to determine the fastest pool. If there is no current RTT data for your pool in a region or colocation center, Cloudflare directs traffic to the pools in failover order.
When enabling Dynamic Steering the first time for a server pool, allow 10 minutes for the change to take effect while Cloudflare builds an RTT profile for that pool.
For TCP health checks, calculated latency may not reflect the true latency to the origin if you are terminating TCP at a cloud provider edge location.
The diagram below shows how Cloudflare would route traffic to the pool with the lowest EWMA among three regions: Eastern North America, Europe, and Australia. In this case, the ENAM pool is selected, because it has the lowest RTT.
Geo Steering directs traffic to pools based on the client’s region or PoP. Only domains on Enterprise plans can perform Geo Steering by PoP. Users specify the pools to which the load balancer should direct traffic for a given geographical region or PoP. You can assign multiple pools to the same region, and the load balancer will use them in failover order. If there is no configuration for a region or pool, the load balancer will use the default failover order.
Cloudflare has 13 geographic regions that span the world. The region of a client is determined by the region of the Cloudflare data center that answers the client’s DNS query. These regions are listed below, along with their region codes.
|WNAM||Western North America|
|ENAM||Eastern North America|
|NSAM||Northern South America|
|SSAM||Southern South America|