Introduction
F5 Distributed Cloud Regional Edges (REs) form the backbone of F5’s globally distributed application delivery network. These F5-managed Points of Presence handle load balancing, Web Application Firewall (WAF) enforcement, bot protection, and API security for thousands of organizations worldwide.
While F5 Regional Edges are engineered for extreme resilience—with built-in redundancy, geographic distribution, and continuous monitoring—no infrastructure is entirely immune to disruption. A defense-in-depth strategy demands that organizations consider even low-probability scenarios.
This article explores how F5 Distributed Cloud Customer Edge (CE) nodes can serve as a fallback data path in the unlikely event of a Regional Edge outage, leveraging a capability that many organizations already have deployed but may not have considered for this purpose.
Understanding the RE and CE Data Paths
Regional Edge: The Default Path
In a typical F5 Distributed Cloud deployment, application traffic follows this path:
- Client resolves the application’s FQDN via DNS
- DNS returns an F5 Regional Edge Anycast IP address
- Internet BGP routing directs the client to the nearest RE advertising that IP
- The RE terminates the connection, applies load balancing and security policies
- The RE forwards traffic to origin servers (directly or via CE nodes)
The key mechanism here is IP Anycast. F5 Regional Edges advertise the same unicast IP address from multiple Points of Presence worldwide via BGP. When a client sends traffic to that IP, the internet’s BGP routing infrastructure naturally selects the shortest AS path—effectively directing the client to the geographically closest (or topologically nearest) RE.
This means the DNS itself does not perform geographic selection. Every client worldwide receives the same IP address in the DNS response. It is the underlying BGP routing on the internet that ensures each client reaches its nearest RE. This is a fundamental difference from GeoDNS-based approaches, where different IPs are returned depending on the client’s location.
Anycast routing typically delivers lower and more consistent latency than GeoDNS for several reasons:
- BGP routes on network topology, not geographic approximation. BGP is a path-vector protocol that selects routes based on AS path length, local preference, and policy attributes—not latency or congestion. However, in practice, routing to the topologically nearest PoP (fewest AS hops) generally correlates with reasonable latency, even if it is not optimized for it.
- GeoIP databases are approximations. GeoDNS relies on commercial GeoIP databases to map IP addresses to locations. These databases can be inaccurate or outdated. BGP doesn’t care about IP-to-location mapping; it routes based on actual network reachability.
- BGP adapts in real-time. If a link fails or a PoP goes offline, the BGP reconverges and traffic shifts to the next-best path automatically—often within seconds. GeoDNS is static until the DNS TTL expires. During that window, clients may continue hitting a degraded or unreachable endpoint.
Regional Edges operate as a fully managed SaaS infrastructure. Organizations benefit from F5’s global Anycast network without deploying or maintaining edge nodes themselves.
Customer Edge: The On-Premises Path
Customer Edge nodes, typically deployed in on-premises data centers or customer cloud environments, can provide the same load balancing and WAF capabilities as Regional Edges. This is a critical but often underappreciated architectural property of the F5 Distributed Cloud platform.
When a load balancer is configured in the F5 Distributed Cloud Console, it can be advertised on:
- Regional Edges only — the default for internet-facing applications
- Customer Edges only — common for internal applications
- Both Regional Edges and Customer Edges — the key to the fallback strategy described in this article
The Shared Configuration Principle
A single load balancer object in the F5 Distributed Cloud Console—with its full configuration including WAF policies, routes, rate limiting, and origin pools—can be advertised simultaneously on REs and CEs. There is no need to duplicate or maintain separate configurations.
| Aspect | Regional Edge | Customer Edge |
|---|---|---|
| Load Balancing | ✓ Same configuration | ✓ Same configuration |
| WAF / App Firewall | ✓ Same policies | ✓ Same policies |
| Routes and Rewrites | ✓ Same rules | ✓ Same rules |
| Origin Pool Selection | ✓ Same pools | ✓ Same pools |
| Bot Defense | ✓ | ✓ |
| API Protection | ✓ | ✓ |
| Managed by | F5 | Customer |
Key Insight: This configuration parity is the foundation of the fallback strategy. The same security posture is enforced regardless of whether traffic enters through a RE or a CE.
The Fallback Strategy: DNS-Based Traffic Switching
How It Works
The failover mechanism from Regional Edges to Customer Edges relies on a straightforward DNS change. Under normal operation, the application’s DNS record points to the RE-assigned IP addresses. In a fallback scenario, the DNS record is updated to point to the public IP addresses of the Customer Edge nodes.
Normal Operation:
app.example.com → RE Anycast IP (e.g., 5.x.x.x, same IP globally) → BGP routing directs client to nearest Regional Edge → RE applies LB + WAF policies → RE forwards to origin
Fallback Operation:
app.example.com → CE Public IP (e.g., 203.0.113.10, standard unicast) → Client connects directly to Customer Edge (no Anycast routing) → CE applies the SAME LB + WAF policies → CE forwards to origin
The application experience remains identical from the client’s perspective in terms of security and functionality. The same policies are enforced, the same load balancing decisions are made, and the same origins are reached. The trade-off is that clients lose the Anycast proximity benefit—all traffic converges on the CE location(s) rather than being distributed to the nearest PoP.
Prerequisites
Before this strategy can be activated, several elements must be in place:
-
The load balancer must be advertised on both REs and CEs. This is configured in the F5 Distributed Cloud Console under the load balancer’s VIP advertisement settings. The CE advertisement must be active before an incident—configuring it during an outage adds delay and risk.
The “Virtual Network“ type with value “ves-io-shared/public” is the equivalent of “Internet“ VIP advertisement.
-
CE nodes must have public IP reachability. The CE’s outside interface (or an NAT/firewall in front of it) must be reachable from the internet on the required ports (typically 443 and/or 80). This may require firewall rules, NAT configurations, or public IP assignments that should be validated in advance.
-
CE nodes must have sufficient capacity for degraded-mode operation. Under normal operation, REs handle the full internet-facing traffic load. CEs used as fallback must be sized to sustain this traffic temporarily—long enough to bridge a RE outage, not to replace RE infrastructure indefinitely. This includes compute resources (CPU, memory), network bandwidth at the CE site, and upstream internet connectivity.
-
DNS records must be prepared. The target CE IP addresses should be documented and ideally pre-staged in DNS management tooling so that the switchover can be executed rapidly.
Important: All prerequisites must be validated before an incident occurs. A fallback strategy that hasn’t been tested is not a fallback strategy.
Customer Edge: The On-Premises Path
Customer Edge nodes, typically deployed in on-premises data centers or customer cloud environments, can provide the same load balancing and WAF capabilities as Regional Edges. This is a critical but often underappreciated architectural property of the F5 Distributed Cloud platform.
When a load balancer is configured in the F5 Distributed Cloud Console, it can be advertised on:
-
Regional Edges only — the default for internet-facing applications

-
Customer Edges only — common for internal applications
-
Both Regional Edges and Customer Edges — the key to the fallback strategy described in this article
The Shared Configuration Principle
A single load balancer object in the F5 Distributed Cloud Console—with its full configuration including WAF policies, routes, rate limiting, and origin pools—can be advertised simultaneously on REs and CEs. There is no need to duplicate or maintain separate configurations.
| Aspect | Regional Edge | Customer Edge |
|---|---|---|
| Load Balancing | ✓ Same configuration | ✓ Same configuration |
| WAF / App Firewall | ✓ Same policies | ✓ Same policies |
| Routes and Rewrites | ✓ Same rules | ✓ Same rules |
| Origin Pool Selection | ✓ Same pools | ✓ Same pools |
| Bot Defense | ✓ | ✓ |
| API Protection | ✓ | ✓ |
| Managed by | F5 | Customer |
Key Insight: This configuration parity is the foundation of the fallback strategy. The same security posture is enforced regardless of whether traffic enters through a RE or a CE.
DNS TTL: The Critical Factor
Why TTL Matters
The speed of a DNS-based failover is fundamentally governed by the Time-To-Live (TTL) value set on the application’s DNS records. TTL determines how long DNS resolvers and clients cache a DNS response before querying again.
| TTL Value | Effective Switchover Time | Trade-off |
|---|---|---|
| 3600 (1 hour) | Up to 1 hour | Minimal DNS query load, slow failover |
| 300 (5 minutes) | Up to 5 minutes | Moderate query load, reasonable failover |
| 60 (1 minute) | Up to 1 minute | Higher query load, fast failover |
| 30 (30 seconds) | Up to 30 seconds | Significant query load, near-instant failover |
Critical: TTL must be set before an incident occurs. Lowering TTL during an outage has no effect on records already cached by resolvers worldwide. The old, higher TTL continues to govern those cached entries until they expire naturally.
Recommended Approach
For organizations that consider CE fullbacks as part of their resilience strategy:
- Proactive TTL reduction: Set DNS TTL to 60–300 seconds on records that may need failover. This should be steady-state TTL, not an emergency change.
- Pre-incident preparation: Ensure the DNS change procedure is documented, tested, and can be executed by on-call staff within minutes.
- Automated failover (advanced): Integrate health checks on RE endpoints with DNS automation (via API calls to your DNS provider) to trigger the switch automatically.
The TTL Reality Check
Even with low TTL values, some clients and intermediate resolvers do not strictly honor TTL:
- Stub resolvers on end-user devices may cache beyond the stated TTL
- Some enterprise DNS resolvers impose minimum TTL floors (commonly 30–60 seconds)
- Browser DNS caches may hold entries independently of the OS resolver
- Connection keep-alive means existing TCP/TLS sessions continue to the old IP even after DNS changes
Organizations should expect a gradual migration of traffic rather than an instantaneous cutover, even with aggressive TTL values. Plan for a transition window of several minutes during which traffic flows to both the old and new endpoints.
Operational Caveats and Considerations
Capacity Planning
Under normal operations, Regional Edges absorb the full internet-facing traffic load across F5’s globally distributed infrastructure. Switching to Customer Edges concentrates this traffic onto a much smaller set of nodes, typically in one or two locations.
| Factor | Regional Edges | Customer Edges (Fallback) |
|---|---|---|
| Geographic distribution | Global | Limited (customer sites) |
| Bandwidth | F5 backbone | Customer uplink |
| DDoS absorption | F5 scrubbing capacity | Customer/ISP capacity |
| Horizontal scale | Elastic | Fixed (pre-provisioned) |
Recommendation: Conduct periodic load testing against CE nodes to validate they can sustain the expected RE traffic volume for a limited duration. CE infrastructure does not need to match RE capacity long-term, but it must hold up long enough to bridge an outage window without service degradation.
DDoS Protection
F5 Regional Edges benefit from F5’s network-level DDoS mitigation infrastructure. When traffic is redirected to Customer Edge nodes, this protection layer is bypassed. The CE site’s internet uplink becomes the direct target for any volumetric attack.
Mitigation options:
- Ensure the CE site has upstream DDoS protection from the ISP or a dedicated scrubbing service
- Consider maintaining a DDoS-protected IP transit for CE public addresses
- If using BGP-routed DDoS protection, ensure CE public prefixes are covered
Failover Workflow
When a RE outage is confirmed and the decision to fail over is made, the procedure is:
Step 1: Update DNS Records
Change the application’s DNS A record (or AAAA for IPv6) from the RE IP addresses to the CE public IP addresses. If multiple CEs are available, configure multiple A records or use the BGP/ECMP architecture described in Part One of this series to distribute traffic across CEs behind a single public IP.
Step 2: Monitor the Transition
Observe traffic shifting to CEs as DNS caches expire. Expect a gradual ramp-up over a period aligned with your DNS TTL. Monitor CE resource utilization, error rates, and application response times.
Step 3: Restore Normal Operation
Once RE services are restored, reverse the DNS change to point back to RE IP addresses. Again, the transition back follows the same TTL-governed timeline. Validate that traffic has fully returned to the RE path before considering any CE-specific fallback infrastructure changes.
Conclusion
F5 Distributed Cloud Customer Edges provide a credible fallback path for the unlikely scenario of a Regional Edge outage. The platform’s ability to advertise a single load balancer—with identical configuration, WAF policies, and origin pools—on both REs and CEs is the enabling feature that makes this strategy viable without configuration duplication or drift.
The key success factors are preparation and proactive configuration:
- DNS TTL must be set low before an incident, not during one
- CE capacity must be sufficient to handle traffic load in a degraded mode—this is a temporary measure, not a long-term replacement for RE infrastructure
- The full failover procedure must be tested periodically to remain viable
- Operational caveats—latency, DDoS exposure, session interruption—must be understood and accepted as part of the failover trade-off
This approach does not replace the resilience built into F5’s Regional Edge infrastructure. Rather, it provides an additional layer of organizational confidence: even in a worst-case scenario, the application delivery path can be restored using infrastructure the organization already controls.



