导航|地址|刷新
Proxy status

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

/Concepts

/Proxy status

Proxy status

Last updated Apr 16, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewLayer 7 load balancing BenefitsDNS-only load balancing Benefits LimitationsLayer 4 load balancing

You can load balance your traffic at different levels of the networking stack, such as:

Layer 7 (HTTP/HTTPS) (most common)

DNS-only

Layer 4 (TCP)

------

Layer 7 load balancing

Layer 7 load balancers direct traffic to specific endpoints based on information present in each HTTP/HTTPS request (HTTP headers, URI, cookies, type of data, etc.).

When a client visits your application, Cloudflare directs their request to a healthy endpoint (determined by your traffic steering policy and endpoint weights).

Cloudflare performs layer 7 load balancing when traffic to your hostname is proxied through Cloudflare. In the Load Balancing dashboard, these load balancers are marked with an orange cloud.

Caution

Note that if a DNS-only (grey cloud) CNAME record points to a proxied load balancer, the IP returned for it would be endpoint IP and a HTTP request sent to it would not be proxied.

Benefits

In comparison to DNS-only load balancing, layer 7 load balancing:

Protects endpoints from DDoS attacks by hiding their IP addresses.

Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.

Integrates with other Cloudflare features such as caching, Workers, and the WAF.

Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.

Supports customized session affinity and endpoint drain.

More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.

Supports private IP addresses with Private Network Load Balancing.

------

DNS-only load balancing

DNS-only load balancers route traffic by returning specific IP addresses in response to a client's DNS query.

When a client visits your application, Cloudflare provides the address for a healthy endpoint (determined by your traffic steering policy and endpoint-level steering policy). However, Cloudflare relies on DNS resolvers respecting the short TTL to re-query Cloudflare's DNS for an updated list of healthy addresses. If a client has a cached DNS response, they will go to their previous destination, potentially ignoring your load balancer.

Cloudflare performs DNS-only load balancing when traffic to your hostname is not proxied through Cloudflare. In the Load Balancing dashboard, these load balancers are marked with a gray cloud.

Note

Note that if a load balancer endpoint is a proxied (orange-cloud) CNAME record on Cloudflare, the IP returned for it would be Cloudflare's and a HTTP request sent to it would be proxied accordingly.

Benefits

If your load balancer is attached to a hostname used for an MX or SRV record — and not an A, AAAA, or CNAME record — its proxy mode should be DNS-only.

Limitations

In comparison to proxied, layer 7 load balancing, DNS-only load balancing:

Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.

Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.

Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.

Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.

Does not support session affinity. Alternatively, you can use DNS persistence.

Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with latency-based steering.

Does not support Private Network Load Balancing.

------

Layer 4 load balancing

Layer 4 load balancers route traffic by forwarding traffic to certain ports or IP addresses.

Cloudflare currently only supports layer 4 load balancing as part of Cloudflare Spectrum.

Note

Since Spectrum operates at the TCP level, it does not have the information to support features like session affinity, custom rules, or caching.

PreviousHow endpoints and pools become unhealthyNextSession affinity

Was this helpful?

YesNo

Edit pageReport issue

On this page

Overview

Layer 7 load balancing

Benefits

DNS-only load balancing

Benefits

Limitations

Layer 4 load balancing

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

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