Skip to content

Commit 9c3d3b2

Browse files
authored
Add load balancing section (#21385)
1 parent 541b434 commit 9c3d3b2

File tree

1 file changed

+4
-1
lines changed
  • src/content/docs/cloudflare-one/policies/gateway/egress-policies

1 file changed

+4
-1
lines changed

src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ sidebar:
88
import { Render } from "~/components";
99

1010
:::note
11-
1211
Only available on Enterprise plans.
1312
:::
1413

@@ -20,6 +19,10 @@ Cloudflare does not publish WARP egress IP ranges. WARP egress IPs are not docum
2019

2120
<Render file="gateway/terraform-precedence-warning" product="cloudflare-one" />
2221

22+
## Load balancing
23+
24+
Gateway traffic that does not match an egress policy will egress from the closest Cloudflare data center with a default Gateway egress IP. If there are two data centers of equal distance from the user, Gateway will split the traffic between the two data centers, and the load balancer will retain the same user selection and egress IP regardless of data center.
25+
2326
## Force IP version
2427

2528
To control whether only IPv4 or IPv6 is used to egress, ensure you are [filtering DNS traffic](/cloudflare-one/policies/gateway/initial-setup/dns/), then create a DNS policy to [block AAAA or A records](/cloudflare-one/policies/gateway/dns-policies/common-policies/#control-ip-version).

0 commit comments

Comments
 (0)