A pool is a group of origin servers, with each origin identified by its IP address or hostname.
If you are familiar with DNS terminology, think of a pool as a “record set,” except Cloudflare only returns addresses that are considered healthy. You can attach health checks to individual pools for customized monitoring.
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.
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.
- Is a subdomain of a zone associated with this account
- Matches the origin address
- Publicly resolves to the origin address
The Cloudflare API supports the following commands for pools. Examples are given for user-level endpoint but apply to the account-level endpoint as well.