导航|地址|刷新
FAQs

Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/load-balancing/llms.txt
Use this file to discover all available pages before exploring further.

Docs Directory API SDKs Changelog

Search

Log in

Load Balancing

/

Overview

Get started

Overview

Enable

Quickstart

Learning path ↗

Concepts

Load Balancing components

Traffic steering

Overview

Global traffic steering

Overview

Standard

Geo

Dynamic

Proximity

Least Outstanding Requests

Local traffic steering

Overview

Random

Hash

Least Outstanding Requests

How endpoints and pools become unhealthy

Proxy status

Session affinity

Adaptive routing

Load balancers

Overview

Manage load balancers

DNS records

Common configurations

Pools

Overview

Manage pools

Use Pages as an origin for Load Balancing

Monitors

Overview

Manage monitors

Monitor Groups

Private Network Load Balancing

Overview

Set up Private Network Load Balancing for Public traffic to Tunnel

Set up Private Network Load Balancing with Cloudflare WAN

Set up Private Network Load Balancing with Client-to-Tunnel

Additional configuration

Overview

Cloudflare Tunnel (published applications)

Spectrum

Perform planned maintenance

Load shedding

DNS persistence

Load Balancing with the China Network

Override HTTP Host headers

CNAME flattening for endpoints

Custom load balancing rules

Overview

Create custom rules

Expressions

Actions

Supported fields and operators

Integrate with PagerDuty

Additional DNS records

Reference

Migration guides

Migrate to new GraphQL nodes

Health monitor notifications

Analytics

Regions API

Limitations

Reference architecture ↗

Troubleshooting

Common error codes

FAQs

API reference ↗API

Changelog

Agent resources

Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Load Balancing llms.txt ↗

Load Balancing llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗

Home

/Load Balancing

/Troubleshooting

/FAQs

FAQs

Last updated May 21, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewOverviewWhy is my origin receiving so many health monitor requests? Multiple Health Monitor Regions Low intervals for health monitor requestsWhy is my endpoint or pool considered unhealthy?Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?What happens when a pool or endpoint becomes unhealthy?What is the difference between Load Balancing and Health Checks?Why do I see different numbers of requests in Load Balancing Analytics?I'm seeing a specific error code for my load balancer or monitor.Related resources

Overview

For more detailed information about Load Balancing — including how-to guides, tutorials, and other reference information — check out our product documentation.

Note

Are you trying to turn on Load Balancing? Enable Load Balancing ↗.

------

Why is my origin receiving so many health monitor requests?

This issue may be caused by a combination of two issues.

Multiple Health Monitor Regions

When you attach a monitor to a pool, you can specify the Health Monitor Regions that Cloudflare uses to monitor your endpoint health.

If you select multiple regions or choose All Data Centers (Enterprise Only), you may dramatically increase traffic to that pool and its associated endpoints. Each region sends individual health monitor requests from 3 data centers. Using All Data Centers sends individual health monitor requests from all existing Cloudflare data centers (and that number of data centers is growing all the time).

To reduce traffic, reduce the number of selected regions or choose an option besides All Data Centers.

Low intervals for health monitor requests

If you have a low interval for your health monitor requests, you may increase the traffic sent to your endpoints.

------

Why is my endpoint or pool considered unhealthy?

To learn more about how endpoints and pools become unhealthy, refer to Endpoint and pool health.

If you know that your endpoint is healthy but load balancing is reporting it as unhealthy, check the following settings on the monitor:

Perform a curl request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.

Ensure your firewall or web server does not block or rate limit our health monitors and accepts requests from Cloudflare IP addresses.

If you are looking for a specific value in the Response Body, make sure that value is relatively static and within the first 10 KB of the HTML page.

If your endpoint responds with a 301 or 302 status code, make sure Follow Redirects is selected.

Try increasing the Timeout value.

Review the Host Header for the health monitor.

If you are using Authenticated Origin Pulls (mTLS), Argo Smart Routing, Bring your own CA (mTLS), Dedicated CDN Egress IPs, or require HTTP/2 to Origin, make sure that you entered a zone value for Simulate Zone corresponding to the zone with these features configured.

------

Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?

You occasionally might see traffic routed away from a pool if a health monitor request fails from a specific data center (even if the endpoint is still healthy). That data center may direct a small number of requests to another pool that is considered healthy by that data center.

To learn more about how endpoints and pools become unhealthy, refer to Endpoint and pool health.

------

What happens when a pool or endpoint becomes unhealthy?

When a pool or endpoint becomes unhealthy, traffic may be rerouted to other healthy pools or endpoints based on your configuration. You might experience this behavior when using:

1 - Pools with All-Datacenters monitoring and the monitor fails in a specific data center. In this case, all traffic will be steered away from impacted endpoints in that datacenter until the monitor succeeds again. These instances are reflected in LB request analytics as steering away from an unhealthy endpoint or pool.

2 - Pools with FQDN endpoint addresses and the recursive DNS lookup fails in a specific data center. In this case, only requests for which the DNS request fails will be steered away from impacted endpoints. This could be sporadic, especially if upstream authoritative resolvers occasionally time out or fail, when the local DNS cache TTL expires and a remote lookup is required in the hot path. This also appears in LB request analytics as steering away from an unhealthy endpoint, and the resolved endpoint IP will be missing from the request log.

To avoid these scenarios:

1 - Do not use All-Datacenters monitoring.

2 - Use IP addresses for endpoint configurations. If that is not feasible, use domains for which Cloudflare is authoritative (primary or secondary).

To learn more about how endpoints and pools become unhealthy, refer to Endpoint and pool health.

------

What is the difference between Load Balancing and Health Checks?

Cloudflare Load Balancing helps monitor endpoints health and — based on that and other information — route incoming requests accordingly. Individual endpoints have monitors attached, which issue monitor requests at regular intervals.

Cloudflare Health Checks are identical to monitors within a load balancer, but only meant for probing server health (and not distributing traffic).

------

Why do I see different numbers of requests in Load Balancing Analytics?

You may see different numbers of requests when reviewing Load Balancing Analytics, especially when compared to other Cloudflare dashboards (Caching, etc.).

Load balancing requests are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds. This built-in caching is often the cause of an discrepancies.

------

I'm seeing a specific error code for my load balancer or monitor.

For a list of specific error codes and next steps, refer to Load Balancing Troubleshooting.

------

Related resources

Endpoint and pool health

Monitors

Load Balancing Analytics

PreviousCommon error codesNextChangelog

Was this helpful?

YesNo

Edit pageReport issue

On this page

Overview

Overview

Why is my origin receiving so many health monitor requests?

Multiple Health Monitor Regions

Low intervals for health monitor requests

Why is my endpoint or pool considered unhealthy?

Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?

What happens when a pool or endpoint becomes unhealthy?

What is the difference between Load Balancing and Health Checks?

Why do I see different numbers of requests in Load Balancing Analytics?

I'm seeing a specific error code for my load balancer or monitor.

Related resources

Edit pageReport issue

Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search

Company
AboutCareersInvestorsPressPress kitGlobal network

Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG

Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse

Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog

Developers
DocumentationLearning centerCommunity

Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform

Start BuildingLog In

© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices

Docs

------
导航页打开网址