Get help 24/7
Cloudflare's Load Balancing automatically reduces latency by directing visitors to infrastructure closest to them: European customers are sent to the London datacenter, Australian customers to the Sydney datacenter etc. Cloudflare Global Load Balancing runs on Cloudflare’s global Anycast network and ensures that origin requests for dynamic content are sourced from origins that are either closest to the user or meet specific weighted requirements.
Cloudflare’s Global Load Balancing runs across Cloudflare’s entire network and supports any protocol: from HTTP(S) to TCP and UDP based services via DNS or Spectrum. This minimizes friction between any existing services deployed with other cloud providers.
Cloudflare Load Balancing includes active availability monitoring that checks the health of servers from Cloudflare’s datacenters around the globe. Through periodic HTTP/HTTPS requests, monitoring can be configured for specific URLs with customizable intervals, timeouts, and status codes. Availability monitoring checks the health of origin servers as often as every 15 seconds, with reporting via email notifications and a REST API. Seconds after an origin server is marked as unhealthy, multi-region failover intelligently routes traffic to the next available server.
Cloudflare Load Balancing is powered by Cloudflare's DDoS-resilient DNS, one of the fastest DNS providers globally. When used alongside Cloudflare's reverse proxy, Cloudflare DNS changes propagate orders of magnitude faster than public DNS services since Cloudflare can avoid waiting for public time-to-lives (TTLs) to expire.
Session Affinity, often referred to as sticky sessions, directs all end-user requests of a session to a specific origin. Cloudflare’s Load Balancer maintains session affinity by setting a cookie with the initial response to the client. Session Affinity can be enabled through a simple configuration change in the Load Balancing application of Cloudflare’s dashboard.
Shopping carts within e-commerce stores benefit from session affinity. If an end-user adds an item to their cart, subsequent requests during the same session require the end-user to be directed to the same origin server to see the item in their cart, which can be achieved through Session Affinity.
Load Balancing event logs allow for the review and filtering of status changes of your Load Balancing origins and pools.
Cloudflare Load Balancing can be used across multiple cloud providers infrastructure to mitigate the impact of disruptions caused by a single provider or server.
Customers select a primary provider to direct all traffic to. Once a failure is detected, Cloudflare Load Balancing automatically routes traffic to backup providers or regions. For example, if a customer experiences outages or intermittent network connectivity in AWS, Google Cloud, Microsoft Azure, or even the customer's own infrastructure, Cloudflare Load Balancing automatically fails over to healthy providers or servers.
Configurable health check monitor frequencies
Fast failover (X seconds)
Session affinity (sticky sessions)
Detailed event logs of origin servers & pools
Works with Argo Smart Routing
Local and global load balancing
Health status notifications through email and REST API
Support for HTTP/S traffic
Geo-routing to origin infrastructure
Avoid DNS propagation delays
Includes DDoS protection
Fastest managed DNS globally
Integrated content delivery network (CDN)
FQDN origin resolution
Support for layer 4 traffic with Spectrum
Cloudflare Load Balancing