Network
Load Balancing review
Score: 6/10Reliable GSLB with a pricing model you have to reverse-engineer.
The breakdown explains the score. It is not an average. How to read these.
Last updated
Cloudflare’s load balancer handles global traffic steering, health checks, failover, and session affinity dependably. Geographic and latency-based steering work as advertised. Health checks from multiple regions give you a trustworthy view of each origin.
The billing is the biggest problem. It is genuinely hard to work out what you pay for: is it per HTTP request, per DNS query, per origin, per monitor? The pricing details are not in the docs at all. You find them on the dashboard, mid-purchase, which is not where pricing questions should get answered. Costs also creep up quickly as you add pools and monitors, in a way that feels disconnected from the rest of the platform.
The UI has not kept up either. Managing many pools across several load balancers gets tedious, and larger setups soon move to Terraform. The core product is solid. The way you buy and operate it needs a refresh.
Status page incidents
Published under Load Balancing and Monitoring, Health Checks, plus incidents whose title names it.
- Last 3 years
- 40
- 10 from the title
- Major or critical
- 3
- Median time open
- 1.6 h
- Since January 2019
- 73
Counts what Cloudflare published, not what broke: time open is how long the status entry stayed open, and nothing before January 2019 is tracked at all. Incidents Cloudflare tagged against nothing but named in the title are counted too. The caveats in full.