Cloudflare Docs
Load Balancing
Load Balancing
Edit this page on GitHub
Set theme to dark (⇧+D)

Origin pools

Within Cloudflare, pools represent your origin servers and how they are organized. As such, a pool can be a group of several origin servers, or you could also have only one origin server per pool.

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 monitors to individual pools for customized monitoring.

​​ Properties

For an up-to-date list of pool properties, refer to Pool properties in our API documentation.

​​ Create pools

For step-by-step guidance, refer to Create pools.

​​ Per origin Host header override

When your application needs specialized routing (CNAME setup or custom hosts like Heroku), change the Host header used in health monitor requests. For more details, refer to Override HTTP Host headers.

​​ API commands

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.

Create PoolPOSTaccounts/:account_id/load_balancers/pools
Delete PoolDELETEaccounts/:account_id/load_balancers/pools/:id
List PoolsGETaccounts/:account_id/load_balancers/pools
Pool DetailsGETaccounts/:account_id/load_balancers/pools/:id
Pool Health DetailsGETaccount/:account_id/load_balancers/pools/:id/health
Overwrite specific propertiesPATCHaccounts/:account_id/load_balancers/pools/:id
Overwrite existing poolPUTaccounts/:account_id/load_balancers/pools/:id
Preview PoolPOSTaccount/:account_id/load_balancers/pools/:id/preview
List Pool ReferencesGETaccounts/:account_id/load_balancers/pools/:id/references