A Cloudflare Load Balancing pool represents a group of origin servers, each identified by their IP address or hostname. You can configure multiple pools, as well as failover priority (Pool A-> Pool B-> Pool C). If you're familiar with DNS terminology, think of a pool as a “record set,” except we only return addresses that are considered healthy. You can attach health checks to individual pools to tailor monitoring for collections of origin servers.
When working with pools, note the following:
When adding origin servers to a pool, you can identify the origin by hostname or IP address.
The order of pools in the load balancer determines the standard failover priority. When the number of healthy origins in a pool drops below the configured threshold, Load Balancing routes traffic to the next available pool.
By default, pools are ordered by date created. You can reorder them from the Load Balancing dashboard and via Cloudflare API (use the Update Pools command to set a new
Dynamic Steering uses Round Trip Time (RTT) profiles to determine pool priority. If there is no RTT data for a pool in a region or colocation center, Load Balancing will use pool order to determine failover priority.
Geo Steering directs traffic to pools based on the client’s region or point of presence. If there is no Geo Steering configuration for a region or pool, the load balancer will use pool order to determine failover priority.
Cloudflare Pool objects have the following properties:
|Name / type||Description / example||Constraints|
|check_regionsarraynull||A list of regions from which to run health checks. Null means every Cloudflare data center.|
|created_onstring (date-time)||Creation time||Read only|
|descriptionstring||A human-readable description of the pool|
|enabledboolean||Set to ||Default value: |
|idstring||API item identifier tag for the pool||Max. length: 32 bytesRead only|
|minimum_originsinteger||The minimum number of origins that must be healthy for this pool to serve traffic. If the number of healthy origins falls below this number, the pool will be marked unhealthy and the load balancer will failover to the next available pool.|
|modified_onstring (date-time)||Last modification time||Read only|
|monitorstring||The ID of the monitor to use for health checking origins within this pool||Max. length: 32 bytesRead only|
|namestring||A short name (tag) for the pool. Only alphanumeric characters, hyphens and underscores are allowed.|
|notification_emailstring||The email address to which health status notifications are sent. This can be an individual mailbox or a mailing list.|
|originsarray||The list of origins within this pool. Traffic directed at this pool is balanced across all currently healthy origins, provided the pool itself is healthy.|
Per origin Host header override
To balance traffic across multiple hosts, add
Host headers to individual origins within the same pool.
For example, you might have a pool with origins hosted in multiple AppEngine projects or Amazon S3 buckets. You also might want to set up specific failover origins within a pool.
Since these examples require specific hostnames per origin, your load balancer could not properly route traffic without a
Host header override.
Managing pools via the Cloudflare API
Pool endpoints are available in the Cloudflare API at both the user and account level, respectively:
|Pool Health Details|