Skip to content

Add recommendation for fallback egress IP configuration #26295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
Open

Add recommendation for fallback egress IP configuration #26295

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...t/docs/cloudflare-one/traffic-policies/egress-policies/dedicated-egress-ips.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,8 @@ To improve traffic resilience, assign your dedicated egress IPs to different Clo

When creating egress policies with dedicated egress IPs, set your secondary IPv4 address to either _Default Cloudflare egress_ or a Cloudflare location different from your primary IPv4 address. If the physical location of your primary IPv4 address is not available, traffic will be routed to either the location closest to the user (_Default Cloudflare egress_ option) or another location of your choice.

In the rare event your primary egress IPs location goes down, and there is no secondary back up IP configured in the egress rule, your traffic will be impacted. Cloudflare strongly recommends ensuring there is always a fallback egress IP configured on every egress policy.

### IP geolocation

:::note
Expand Down