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

Load Balancing components

This page provides a simplified overview of the three main components of the Cloudflare Load Balancing solution and how they relate to one another.

​​ Load balancers

For a hostname ( to resolve, the Domain Name System (DNS) must return an IP address, where the website or application is hosted (origin).

When you set up a load balancer, Cloudflare automatically creates an LB DNS record for the specified hostname. This means that, according to a priority order, instead of simply returning an origin IP address, the logic you introduced using the Cloudflare Load Balancing solution will be considered.

​​ 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 this is what best suits your use case.

For example, if you are only using Cloudflare to globally distribute traffic across regions (traffic steering), each pool could represent one region and, within each region, you could have one origin that represents the entry point to your data center.

​​ Monitors

Finally, monitors are the component you can use to guarantee only healthy pools are considered for traffic distribution.

When you configure a monitor and attach it to origins, the monitor will issue health monitor requests to your origins at regular intervals. This process makes it possible for your load balancer to intelligently handle traffic, considering which origins are actually available.