Regional and policy routing
Design routing around your audience and workload instead of assuming one path fits every request.
Shape traffic around audience regions, origin health and business policies, so delivery paths can adapt to real requirements.
Consider visitor regions, origin health and routing policies together. For applications with multiple regions or service entrances, a clear routing strategy can reduce unnecessary detours.
Design routing around your audience and workload instead of assuming one path fits every request.
Use appropriate health checks and origin configuration to detect problems and plan failover.
Clarify multi-origin dependencies, failover conditions and rollback paths for controlled changes.
Map the relationship between domains, regions and origins.
Use configured health checks to understand service reachability.
Guide requests to an appropriate entrance using business routing policies.
Review failed requests and responses to refine your configuration.
Available features, coverage and service commitments depend on your enabled configuration and service agreement.
Start with your traffic and existing architecture, agree on the scope, then connect and validate in stages.
Start with your business goals. Build an acceleration and security plan with WAFGO.
Talk to our team