Skip to content

Commit 8f76bd0

Browse files
maxvpthomasgauvin
authored andcommitted
Update index.mdx (#24078)
1 parent b9fbce2 commit 8f76bd0

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Cloudflare does not publish WARP egress IP ranges. WARP egress IPs are not docum
2121

2222
## Load balancing
2323

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.
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. This logic applies to both the default Cloudflare egress IPs and any dedicated egress IPs.
2525

2626
## Force IP version
2727

0 commit comments

Comments
 (0)