Load Balancers
List Load Balancers
Load Balancer Details
Create Load Balancer
Update Load Balancer
Patch Load Balancer
Delete Load Balancer
ModelsExpand Collapse
type AdaptiveRouting struct{…}Controls features that modify the routing of requests to pools and origins in response to dynamic conditions, such as during the interval between active health monitoring requests. For example, zero-downtime failover occurs immediately when an origin becomes unavailable due to HTTP 521, 522, or 523 response codes. If there is another healthy origin in the same pool, the request is retried once against this alternate origin.
Controls features that modify the routing of requests to pools and origins in response to dynamic conditions, such as during the interval between active health monitoring requests. For example, zero-downtime failover occurs immediately when an origin becomes unavailable due to HTTP 521, 522, or 523 response codes. If there is another healthy origin in the same pool, the request is retried once against this alternate origin.
Extends zero-downtime failover of requests to healthy origins from alternate pools, when no healthy alternate exists in the same pool, according to the failover order defined by traffic and origin steering. When set false (the default) zero-downtime failover will only occur between origins within the same pool. See session_affinity_attributes for control over when sessions are broken or reassigned.
type CheckRegion stringWNAM: Western North America, ENAM: Eastern North America, WEU: Western Europe, EEU: Eastern Europe, NSAM: Northern South America, SSAM: Southern South America, OC: Oceania, ME: Middle East, NAF: North Africa, SAF: South Africa, SAS: Southern Asia, SEAS: South East Asia, NEAS: North East Asia, ALL_REGIONS: all regions (ENTERPRISE customers only).
WNAM: Western North America, ENAM: Eastern North America, WEU: Western Europe, EEU: Eastern Europe, NSAM: Northern South America, SSAM: Southern South America, OC: Oceania, ME: Middle East, NAF: North Africa, SAF: South Africa, SAS: Southern Asia, SEAS: South East Asia, NEAS: North East Asia, ALL_REGIONS: all regions (ENTERPRISE customers only).
type LoadBalancer struct{…}
Controls features that modify the routing of requests to pools and origins in response to dynamic conditions, such as during the interval between active health monitoring requests. For example, zero-downtime failover occurs immediately when an origin becomes unavailable due to HTTP 521, 522, or 523 response codes. If there is another healthy origin in the same pool, the request is retried once against this alternate origin.
A mapping of country codes to a list of pool IDs (ordered by their failover priority) for the given country. Any country not explicitly defined will fall back to using the corresponding region_pool mapping if it exists else to default_pools.
A list of pool IDs ordered by their failover priority. Pools defined here are used by default, or when region_pools are not configured for a given region.
Controls location-based steering for non-proxied requests. See steering_policy to learn how steering is affected.
The DNS hostname to associate with your Load Balancer. If this hostname already exists as a DNS record in Cloudflare's DNS, the Load Balancer will take precedence and the DNS record will not be used.
Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any PoPs not explicitly defined will fall back to using the corresponding country_pool, then region_pool mapping if it exists else to default_pools.
Configures pool weights.
steering_policy="random": A random pool is selected with probability proportional to pool weights.steering_policy="least_outstanding_requests": Use pool weights to scale each pool's outstanding requests.steering_policy="least_connections": Use pool weights to scale each pool's open connections.
A mapping of region codes to a list of pool IDs (ordered by their failover priority) for the given region. Any regions not explicitly defined will fall back to using default_pools.
BETA Field Not General Access: A list of rules for this load balancer to execute.
BETA Field Not General Access: A list of rules for this load balancer to execute.
The condition expressions to evaluate. If the condition evaluates to true, the overrides or fixed_response in this rule will be applied. An empty condition is always true. For more details on condition expressions, please see https://developers.cloudflare.com/load-balancing/understand-basics/load-balancing-rules/expressions.
Disable this specific rule. It will no longer be evaluated by this load balancer.
FixedResponse RulesFixedResponseoptionalA collection of fields used to directly respond to the eyeball instead of routing to a pool. If a fixed_response is supplied the rule will be marked as terminates.
A collection of fields used to directly respond to the eyeball instead of routing to a pool. If a fixed_response is supplied the rule will be marked as terminates.
Overrides RulesOverridesoptionalA collection of overrides to apply to the load balancer when this rule's condition is true. All fields are optional.
A collection of overrides to apply to the load balancer when this rule's condition is true. All fields are optional.
Controls features that modify the routing of requests to pools and origins in response to dynamic conditions, such as during the interval between active health monitoring requests. For example, zero-downtime failover occurs immediately when an origin becomes unavailable due to HTTP 521, 522, or 523 response codes. If there is another healthy origin in the same pool, the request is retried once against this alternate origin.
A mapping of country codes to a list of pool IDs (ordered by their failover priority) for the given country. Any country not explicitly defined will fall back to using the corresponding region_pool mapping if it exists else to default_pools.
A list of pool IDs ordered by their failover priority. Pools defined here are used by default, or when region_pools are not configured for a given region.
Controls location-based steering for non-proxied requests. See steering_policy to learn how steering is affected.
Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any PoPs not explicitly defined will fall back to using the corresponding country_pool, then region_pool mapping if it exists else to default_pools.
Configures pool weights.
steering_policy="random": A random pool is selected with probability proportional to pool weights.steering_policy="least_outstanding_requests": Use pool weights to scale each pool's outstanding requests.steering_policy="least_connections": Use pool weights to scale each pool's open connections.
A mapping of region codes to a list of pool IDs (ordered by their failover priority) for the given region. Any regions not explicitly defined will fall back to using default_pools.
Specifies the type of session affinity the load balancer should use unless specified as "none". The supported types are: - "cookie": On the first request to a proxied load balancer, a cookie is generated, encoding information of which origin the request will be forwarded to. Subsequent requests, by the same client to the same load balancer, will be sent to the origin server the cookie encodes, for the duration of the cookie and as long as the origin server remains healthy. If the cookie has expired or the origin server is unhealthy, then a new origin server is calculated and used. - "ip_cookie": Behaves the same as "cookie" except the initial origin selection is stable and based on the client's ip address. - "header": On the first request to a proxied load balancer, a session key based on the configured HTTP headers (see session_affinity_attributes.headers) is generated, encoding the request headers used for storing in the load balancer session state which origin the request will be forwarded to. Subsequent requests to the load balancer with the same headers will be sent to the same origin server, for the duration of the session and as long as the origin server remains healthy. If the session has been idle for the duration of session_affinity_ttl seconds or the origin server is unhealthy, then a new origin server is calculated and used. See headers in session_affinity_attributes for additional required configuration.
Time, in seconds, until a client's session expires after being created. Once the expiry time has been reached, subsequent requests may get sent to a different origin server. The accepted ranges per session_affinity policy are: - "cookie" / "ip_cookie": The current default of 23 hours will be used unless explicitly set. The accepted range of values is between [1800, 604800]. - "header": The current default of 1800 seconds will be used unless explicitly set. The accepted range of values is between [30, 3600]. Note: With session affinity by header, sessions only expire after they haven't been used for the number of seconds specified.
Steering Policy for this load balancer.
"off": Usedefault_pools."geo": Useregion_pools/country_pools/pop_pools. For non-proxied requests, the country forcountry_poolsis determined bylocation_strategy."random": Select a pool randomly."dynamic_latency": Use round trip time to select the closest pool in default_pools (requires pool health checks)."proximity": Use the pools' latitude and longitude to select the closest pool using the Cloudflare PoP location for proxied requests or the location determined bylocation_strategyfor non-proxied requests."least_outstanding_requests": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of outstanding requests. Pools with more pending requests are weighted proportionately less relative to others."least_connections": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of open connections. Pools with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections."": Will map to"geo"if you useregion_pools/country_pools/pop_poolsotherwise"off".
Specifies the type of session affinity the load balancer should use unless specified as "none". The supported types are: - "cookie": On the first request to a proxied load balancer, a cookie is generated, encoding information of which origin the request will be forwarded to. Subsequent requests, by the same client to the same load balancer, will be sent to the origin server the cookie encodes, for the duration of the cookie and as long as the origin server remains healthy. If the cookie has expired or the origin server is unhealthy, then a new origin server is calculated and used. - "ip_cookie": Behaves the same as "cookie" except the initial origin selection is stable and based on the client's ip address. - "header": On the first request to a proxied load balancer, a session key based on the configured HTTP headers (see session_affinity_attributes.headers) is generated, encoding the request headers used for storing in the load balancer session state which origin the request will be forwarded to. Subsequent requests to the load balancer with the same headers will be sent to the same origin server, for the duration of the session and as long as the origin server remains healthy. If the session has been idle for the duration of session_affinity_ttl seconds or the origin server is unhealthy, then a new origin server is calculated and used. See headers in session_affinity_attributes for additional required configuration.
Time, in seconds, until a client's session expires after being created. Once the expiry time has been reached, subsequent requests may get sent to a different origin server. The accepted ranges per session_affinity policy are: - "cookie" / "ip_cookie": The current default of 23 hours will be used unless explicitly set. The accepted range of values is between [1800, 604800]. - "header": The current default of 1800 seconds will be used unless explicitly set. The accepted range of values is between [30, 3600]. Note: With session affinity by header, sessions only expire after they haven't been used for the number of seconds specified.
Steering Policy for this load balancer.
"off": Usedefault_pools."geo": Useregion_pools/country_pools/pop_pools. For non-proxied requests, the country forcountry_poolsis determined bylocation_strategy."random": Select a pool randomly."dynamic_latency": Use round trip time to select the closest pool in default_pools (requires pool health checks)."proximity": Use the pools' latitude and longitude to select the closest pool using the Cloudflare PoP location for proxied requests or the location determined bylocation_strategyfor non-proxied requests."least_outstanding_requests": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of outstanding requests. Pools with more pending requests are weighted proportionately less relative to others."least_connections": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of open connections. Pools with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections."": Will map to"geo"if you useregion_pools/country_pools/pop_poolsotherwise"off".
type LoadShedding struct{…}Configures load shedding policies and percentages for the pool.
Configures load shedding policies and percentages for the pool.
The percent of traffic to shed from the pool, according to the default policy. Applies to new sessions and traffic without session affinity.
DefaultPolicy LoadSheddingDefaultPolicyoptionalThe default policy to use when load shedding. A random policy randomly sheds a given percent of requests. A hash policy computes a hash over the CF-Connecting-IP address and sheds all requests originating from a percent of IPs.
The default policy to use when load shedding. A random policy randomly sheds a given percent of requests. A hash policy computes a hash over the CF-Connecting-IP address and sheds all requests originating from a percent of IPs.
type LocationStrategy struct{…}Controls location-based steering for non-proxied requests. See steering_policy to learn how steering is affected.
Controls location-based steering for non-proxied requests. See steering_policy to learn how steering is affected.
Mode LocationStrategyModeoptionalDetermines the authoritative location when ECS is not preferred, does not exist in the request, or its GeoIP lookup is unsuccessful.
"pop": Use the Cloudflare PoP location."resolver_ip": Use the DNS resolver GeoIP location. If the GeoIP lookup is unsuccessful, use the Cloudflare PoP location.
Determines the authoritative location when ECS is not preferred, does not exist in the request, or its GeoIP lookup is unsuccessful.
"pop": Use the Cloudflare PoP location."resolver_ip": Use the DNS resolver GeoIP location. If the GeoIP lookup is unsuccessful, use the Cloudflare PoP location.
PreferECS LocationStrategyPreferECSoptionalWhether the EDNS Client Subnet (ECS) GeoIP should be preferred as the authoritative location.
"always": Always prefer ECS."never": Never prefer ECS."proximity": Prefer ECS only when steering_policy="proximity"."geo": Prefer ECS only when steering_policy="geo".
Whether the EDNS Client Subnet (ECS) GeoIP should be preferred as the authoritative location.
"always": Always prefer ECS."never": Never prefer ECS."proximity": Prefer ECS only whensteering_policy="proximity"."geo": Prefer ECS only whensteering_policy="geo".
type Origin struct{…}
The IP address (IPv4 or IPv6) of the origin, or its publicly addressable hostname. Hostnames entered here should resolve directly to the origin, and not be a hostname proxied by Cloudflare. To set an internal/reserved address, virtual_network_id must also be set.
This field shows up only if the origin is disabled. This field is set with the time the origin was disabled.
Whether to enable (the default) this origin within the pool. Disabled origins will not receive traffic and are excluded from health checks. The origin will only be disabled for the current pool.
The request header is used to pass additional information with an HTTP request. Currently supported header is 'Host'.
The port for upstream connections. A value of 0 means the default port for the protocol will be used.
The virtual network subnet ID the origin belongs in. Virtual network must also belong to the account.
The weight of this origin relative to other origins in the pool. Based on the configured weight the total traffic is distributed among origins within the pool.
origin_steering.policy="least_outstanding_requests": Use weight to scale the origin's outstanding requests.origin_steering.policy="least_connections": Use weight to scale the origin's open connections.
type OriginSteering struct{…}Configures origin steering for the pool. Controls how origins are selected for new sessions and traffic without session affinity.
Configures origin steering for the pool. Controls how origins are selected for new sessions and traffic without session affinity.
Policy OriginSteeringPolicyoptionalThe type of origin steering policy to use.
"random": Select an origin randomly."hash": Select an origin by computing a hash over the CF-Connecting-IP address."least_outstanding_requests": Select an origin by taking into consideration origin weights, as well as each origin's number of outstanding requests. Origins with more pending requests are weighted proportionately less relative to others."least_connections": Select an origin by taking into consideration origin weights, as well as each origin's number of open connections. Origins with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections.
The type of origin steering policy to use.
"random": Select an origin randomly."hash": Select an origin by computing a hash over the CF-Connecting-IP address."least_outstanding_requests": Select an origin by taking into consideration origin weights, as well as each origin's number of outstanding requests. Origins with more pending requests are weighted proportionately less relative to others."least_connections": Select an origin by taking into consideration origin weights, as well as each origin's number of open connections. Origins with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections.
type RandomSteering struct{…}Configures pool weights.
steering_policy="random": A random pool is selected with probability proportional to pool weights.steering_policy="least_outstanding_requests": Use pool weights to scale each pool's outstanding requests.steering_policy="least_connections": Use pool weights to scale each pool's open connections.
Configures pool weights.
steering_policy="random": A random pool is selected with probability proportional to pool weights.steering_policy="least_outstanding_requests": Use pool weights to scale each pool's outstanding requests.steering_policy="least_connections": Use pool weights to scale each pool's open connections.
type Rules struct{…}A rule object containing conditions and overrides for this load balancer to evaluate.
A rule object containing conditions and overrides for this load balancer to evaluate.
The condition expressions to evaluate. If the condition evaluates to true, the overrides or fixed_response in this rule will be applied. An empty condition is always true. For more details on condition expressions, please see https://developers.cloudflare.com/load-balancing/understand-basics/load-balancing-rules/expressions.
Disable this specific rule. It will no longer be evaluated by this load balancer.
FixedResponse RulesFixedResponseoptionalA collection of fields used to directly respond to the eyeball instead of routing to a pool. If a fixed_response is supplied the rule will be marked as terminates.
A collection of fields used to directly respond to the eyeball instead of routing to a pool. If a fixed_response is supplied the rule will be marked as terminates.
Overrides RulesOverridesoptionalA collection of overrides to apply to the load balancer when this rule's condition is true. All fields are optional.
A collection of overrides to apply to the load balancer when this rule's condition is true. All fields are optional.
Controls features that modify the routing of requests to pools and origins in response to dynamic conditions, such as during the interval between active health monitoring requests. For example, zero-downtime failover occurs immediately when an origin becomes unavailable due to HTTP 521, 522, or 523 response codes. If there is another healthy origin in the same pool, the request is retried once against this alternate origin.
A mapping of country codes to a list of pool IDs (ordered by their failover priority) for the given country. Any country not explicitly defined will fall back to using the corresponding region_pool mapping if it exists else to default_pools.
A list of pool IDs ordered by their failover priority. Pools defined here are used by default, or when region_pools are not configured for a given region.
Controls location-based steering for non-proxied requests. See steering_policy to learn how steering is affected.
Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any PoPs not explicitly defined will fall back to using the corresponding country_pool, then region_pool mapping if it exists else to default_pools.
Configures pool weights.
steering_policy="random": A random pool is selected with probability proportional to pool weights.steering_policy="least_outstanding_requests": Use pool weights to scale each pool's outstanding requests.steering_policy="least_connections": Use pool weights to scale each pool's open connections.
A mapping of region codes to a list of pool IDs (ordered by their failover priority) for the given region. Any regions not explicitly defined will fall back to using default_pools.
Specifies the type of session affinity the load balancer should use unless specified as "none". The supported types are: - "cookie": On the first request to a proxied load balancer, a cookie is generated, encoding information of which origin the request will be forwarded to. Subsequent requests, by the same client to the same load balancer, will be sent to the origin server the cookie encodes, for the duration of the cookie and as long as the origin server remains healthy. If the cookie has expired or the origin server is unhealthy, then a new origin server is calculated and used. - "ip_cookie": Behaves the same as "cookie" except the initial origin selection is stable and based on the client's ip address. - "header": On the first request to a proxied load balancer, a session key based on the configured HTTP headers (see session_affinity_attributes.headers) is generated, encoding the request headers used for storing in the load balancer session state which origin the request will be forwarded to. Subsequent requests to the load balancer with the same headers will be sent to the same origin server, for the duration of the session and as long as the origin server remains healthy. If the session has been idle for the duration of session_affinity_ttl seconds or the origin server is unhealthy, then a new origin server is calculated and used. See headers in session_affinity_attributes for additional required configuration.
Time, in seconds, until a client's session expires after being created. Once the expiry time has been reached, subsequent requests may get sent to a different origin server. The accepted ranges per session_affinity policy are: - "cookie" / "ip_cookie": The current default of 23 hours will be used unless explicitly set. The accepted range of values is between [1800, 604800]. - "header": The current default of 1800 seconds will be used unless explicitly set. The accepted range of values is between [30, 3600]. Note: With session affinity by header, sessions only expire after they haven't been used for the number of seconds specified.
Steering Policy for this load balancer.
"off": Usedefault_pools."geo": Useregion_pools/country_pools/pop_pools. For non-proxied requests, the country forcountry_poolsis determined bylocation_strategy."random": Select a pool randomly."dynamic_latency": Use round trip time to select the closest pool in default_pools (requires pool health checks)."proximity": Use the pools' latitude and longitude to select the closest pool using the Cloudflare PoP location for proxied requests or the location determined bylocation_strategyfor non-proxied requests."least_outstanding_requests": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of outstanding requests. Pools with more pending requests are weighted proportionately less relative to others."least_connections": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of open connections. Pools with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections."": Will map to"geo"if you useregion_pools/country_pools/pop_poolsotherwise"off".
type SessionAffinity stringSpecifies the type of session affinity the load balancer should use unless specified as "none". The supported types are: - "cookie": On the first request to a proxied load balancer, a cookie is generated, encoding information of which origin the request will be forwarded to. Subsequent requests, by the same client to the same load balancer, will be sent to the origin server the cookie encodes, for the duration of the cookie and as long as the origin server remains healthy. If the cookie has expired or the origin server is unhealthy, then a new origin server is calculated and used. - "ip_cookie": Behaves the same as "cookie" except the initial origin selection is stable and based on the client's ip address. - "header": On the first request to a proxied load balancer, a session key based on the configured HTTP headers (see session_affinity_attributes.headers) is generated, encoding the request headers used for storing in the load balancer session state which origin the request will be forwarded to. Subsequent requests to the load balancer with the same headers will be sent to the same origin server, for the duration of the session and as long as the origin server remains healthy. If the session has been idle for the duration of session_affinity_ttl seconds or the origin server is unhealthy, then a new origin server is calculated and used. See headers in session_affinity_attributes for additional required configuration.
Specifies the type of session affinity the load balancer should use unless specified as "none". The supported types are: - "cookie": On the first request to a proxied load balancer, a cookie is generated, encoding information of which origin the request will be forwarded to. Subsequent requests, by the same client to the same load balancer, will be sent to the origin server the cookie encodes, for the duration of the cookie and as long as the origin server remains healthy. If the cookie has expired or the origin server is unhealthy, then a new origin server is calculated and used. - "ip_cookie": Behaves the same as "cookie" except the initial origin selection is stable and based on the client's ip address. - "header": On the first request to a proxied load balancer, a session key based on the configured HTTP headers (see session_affinity_attributes.headers) is generated, encoding the request headers used for storing in the load balancer session state which origin the request will be forwarded to. Subsequent requests to the load balancer with the same headers will be sent to the same origin server, for the duration of the session and as long as the origin server remains healthy. If the session has been idle for the duration of session_affinity_ttl seconds or the origin server is unhealthy, then a new origin server is calculated and used. See headers in session_affinity_attributes for additional required configuration.
type SessionAffinityAttributes struct{…}Configures attributes for session affinity.
Configures attributes for session affinity.
Configures the drain duration in seconds. This field is only used when session affinity is enabled on the load balancer.
Configures the names of HTTP headers to base session affinity on when header session_affinity is enabled. At least one HTTP header name must be provided. To specify the exact cookies to be used, include an item in the following format: "cookie:<cookie-name-1>,<cookie-name-2>" (example) where everything after the colon is a comma-separated list of cookie names. Providing only "cookie" will result in all cookies being used. The default max number of HTTP header names that can be provided depends on your plan: 5 for Enterprise, 1 for all other plans.
When header session_affinity is enabled, this option can be used to specify how HTTP headers on load balancing requests will be used. The supported values are: - "true": Load balancing requests must contain all of the HTTP headers specified by the headers session affinity attribute, otherwise sessions aren't created. - "false": Load balancing requests must contain at least one of the HTTP headers specified by the headers session affinity attribute, otherwise sessions aren't created.
Samesite SessionAffinityAttributesSamesiteoptionalConfigures the SameSite attribute on session affinity cookie. Value "Auto" will be translated to "Lax" or "None" depending if Always Use HTTPS is enabled. Note: when using value "None", the secure attribute can not be set to "Never".
Configures the SameSite attribute on session affinity cookie. Value "Auto" will be translated to "Lax" or "None" depending if Always Use HTTPS is enabled. Note: when using value "None", the secure attribute can not be set to "Never".
Secure SessionAffinityAttributesSecureoptionalConfigures the Secure attribute on session affinity cookie. Value "Always" indicates the Secure attribute will be set in the Set-Cookie header, "Never" indicates the Secure attribute will not be set, and "Auto" will set the Secure attribute depending if Always Use HTTPS is enabled.
Configures the Secure attribute on session affinity cookie. Value "Always" indicates the Secure attribute will be set in the Set-Cookie header, "Never" indicates the Secure attribute will not be set, and "Auto" will set the Secure attribute depending if Always Use HTTPS is enabled.
ZeroDowntimeFailover SessionAffinityAttributesZeroDowntimeFailoveroptionalConfigures the zero-downtime failover between origins within a pool when session affinity is enabled. This feature is currently incompatible with Argo, Tiered Cache, and Bandwidth Alliance. The supported values are: - "none": No failover takes place for sessions pinned to the origin (default). - "temporary": Traffic will be sent to another other healthy origin until the originally pinned origin is available; note that this can potentially result in heavy origin flapping. - "sticky": The session affinity cookie is updated and subsequent requests are sent to the new origin. Note: Zero-downtime failover with sticky sessions is currently not supported for session affinity by header.
Configures the zero-downtime failover between origins within a pool when session affinity is enabled. This feature is currently incompatible with Argo, Tiered Cache, and Bandwidth Alliance. The supported values are: - "none": No failover takes place for sessions pinned to the origin (default). - "temporary": Traffic will be sent to another other healthy origin until the originally pinned origin is available; note that this can potentially result in heavy origin flapping. - "sticky": The session affinity cookie is updated and subsequent requests are sent to the new origin. Note: Zero-downtime failover with sticky sessions is currently not supported for session affinity by header.
type SteeringPolicy stringSteering Policy for this load balancer.
"off": Use default_pools."geo": Use region_pools/country_pools/pop_pools. For non-proxied requests, the country for country_pools is determined by location_strategy."random": Select a pool randomly."dynamic_latency": Use round trip time to select the closest pool in default_pools (requires pool health checks)."proximity": Use the pools' latitude and longitude to select the closest pool using the Cloudflare PoP location for proxied requests or the location determined by location_strategy for non-proxied requests."least_outstanding_requests": Select a pool by taking into consideration random_steering weights, as well as each pool's number of outstanding requests. Pools with more pending requests are weighted proportionately less relative to others."least_connections": Select a pool by taking into consideration random_steering weights, as well as each pool's number of open connections. Pools with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections."": Will map to "geo" if you use region_pools/country_pools/pop_pools otherwise "off".
Steering Policy for this load balancer.
"off": Usedefault_pools."geo": Useregion_pools/country_pools/pop_pools. For non-proxied requests, the country forcountry_poolsis determined bylocation_strategy."random": Select a pool randomly."dynamic_latency": Use round trip time to select the closest pool in default_pools (requires pool health checks)."proximity": Use the pools' latitude and longitude to select the closest pool using the Cloudflare PoP location for proxied requests or the location determined bylocation_strategyfor non-proxied requests."least_outstanding_requests": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of outstanding requests. Pools with more pending requests are weighted proportionately less relative to others."least_connections": Select a pool by taking into considerationrandom_steeringweights, as well as each pool's number of open connections. Pools with more open connections are weighted proportionately less relative to others. Supported for HTTP/1 and HTTP/2 connections."": Will map to"geo"if you useregion_pools/country_pools/pop_poolsotherwise"off".
Load BalancersMonitors
List Monitors
Monitor Details
Create Monitor
Update Monitor
Patch Monitor
Delete Monitor
ModelsExpand Collapse
type Monitor struct{…}
Do not validate the certificate when monitor use HTTPS. This parameter is currently only valid for HTTP and HTTPS monitors.
To be marked unhealthy the monitored origin must fail this healthcheck N consecutive times.
To be marked healthy the monitored origin must pass this healthcheck N consecutive times.
A case-insensitive sub-string to look for in the response body. If this string is not found, the origin will be marked as unhealthy. This parameter is only valid for HTTP and HTTPS monitors.
The expected HTTP response code or code range of the health check. This parameter is only valid for HTTP and HTTPS monitors.
Follow redirects if returned by the origin. This parameter is only valid for HTTP and HTTPS monitors.
The HTTP request headers to send in the health check. It is recommended you set a Host header by default. The User-Agent header cannot be overridden. This parameter is only valid for HTTP and HTTPS monitors.
The interval between each health check. Shorter intervals may improve failover time, but will increase load on the origins as we check from multiple locations.
The method to use for the health check. This defaults to 'GET' for HTTP/HTTPS based checks and 'connection_established' for TCP based health checks.
The endpoint path you want to conduct a health check against. This parameter is only valid for HTTP and HTTPS monitors.
The port number to connect to for the health check. Required for TCP, UDP, and SMTP checks. HTTP and HTTPS checks should only define the port when using a non-standard port (HTTP: default 80, HTTPS: default 443).
Assign this monitor to emulate the specified zone while probing. This parameter is only valid for HTTP and HTTPS monitors.
The number of retries to attempt in case of a timeout before marking the origin as unhealthy. Retries are attempted immediately.
Load BalancersMonitorsPreviews
Preview Monitor
Load BalancersMonitorsReferences
List Monitor References
Load BalancersMonitor Groups
List Monitor Groups
Monitor Group Details
Create Monitor Group
Update Monitor Group
Patch Monitor Group
Delete Monitor Group
Load BalancersPools
List Pools
Pool Details
Create Pool
Update Pool
Patch Pool
Delete Pool
Patch Pools
ModelsExpand Collapse
type Pool struct{…}
A list of regions from which to run health checks. Null means every Cloudflare data center.
A list of regions from which to run health checks. Null means every Cloudflare data center.
This field shows up only if the pool is disabled. This field is set with the time the pool was disabled at.
Whether to enable (the default) or disable this pool. Disabled pools will not receive traffic and are excluded from health checks. Disabling a pool will cause any load balancers using it to failover to the next pool (if any).
The latitude of the data center containing the origins used in this pool in decimal degrees. If this is set, longitude must also be set.
The longitude of the data center containing the origins used in this pool in decimal degrees. If this is set, latitude must also be set.
The minimum number of origins that must be healthy for this pool to serve traffic. If the number of healthy origins falls below this number, the pool will be marked unhealthy and will failover to the next available pool.
The ID of the Monitor to use for checking the health of origins within this pool.
The ID of the Monitor Group to use for checking the health of origins within this pool.
A short name (tag) for the pool. Only alphanumeric characters, hyphens, and underscores are allowed.
This field is now deprecated. It has been moved to Cloudflare's Centralized Notification service https://developers.cloudflare.com/fundamentals/notifications/. The email address to send health status notifications to. This can be an individual mailbox or a mailing list. Multiple emails can be supplied as a comma delimited list.
Configures origin steering for the pool. Controls how origins are selected for new sessions and traffic without session affinity.
The list of origins within this pool. Traffic directed at this pool is balanced across all currently healthy origins, provided the pool itself is healthy.
The list of origins within this pool. Traffic directed at this pool is balanced across all currently healthy origins, provided the pool itself is healthy.
The IP address (IPv4 or IPv6) of the origin, or its publicly addressable hostname. Hostnames entered here should resolve directly to the origin, and not be a hostname proxied by Cloudflare. To set an internal/reserved address, virtual_network_id must also be set.
This field shows up only if the origin is disabled. This field is set with the time the origin was disabled.
Whether to enable (the default) this origin within the pool. Disabled origins will not receive traffic and are excluded from health checks. The origin will only be disabled for the current pool.
The request header is used to pass additional information with an HTTP request. Currently supported header is 'Host'.
The port for upstream connections. A value of 0 means the default port for the protocol will be used.
The virtual network subnet ID the origin belongs in. Virtual network must also belong to the account.
The weight of this origin relative to other origins in the pool. Based on the configured weight the total traffic is distributed among origins within the pool.
origin_steering.policy="least_outstanding_requests": Use weight to scale the origin's outstanding requests.origin_steering.policy="least_connections": Use weight to scale the origin's open connections.