Overview
Network planning with WAFGO follows the visitor's request path: where traffic enters, which content can be reused, how origin access recovers and how outcomes are measured.
Regional guidance supports planning and testing; it does not claim deployed nodes in every country. Confirm available locations, carrier paths and coverage for the intended deployment.
Coordinate the edge, routing and origin
Requests enter the delivery path, reusable public content is served from cache, and other requests reach the origin according to policy. Routing and health checks help manage path selection and failures.
Edge caching
Place suitable shared resources closer to visitors while keeping updates, permissions and cache keys consistent.
Path selection
Evaluate routes using observed network quality and workload characteristics rather than geography alone.
Origin connectivity
Review origin protocols, connection settings and recovery processes instead of checking only edge responses.
Evaluate more than a regional label
Experiences can vary across carriers, borders and mobile networks. Use samples that resemble the real audience and compare consistent resources and time windows.
| Audience region | Planning focus |
|---|---|
| Europe and North America | Country or coast distribution, origin distance and cold versus warm caching |
| Asia and Oceania | Cross-border paths, island and inland networks, and mobile clients |
| Latin America | Users beyond major cities, carrier variation and sustained downloads |
| Middle East and Africa | Country-specific reachability, path variation and cache behavior |
Build a repeatable delivery baseline
Observe first-byte time, request errors, transfer completion and origin traffic together. Node counts or a single average-latency figure cannot fully describe an application's experience.
- Group measurements by country, carrier and device, preserving comparable before-and-after samples.
- Separate cold and warm cache behavior and record payload sizes and origin processing time.
- Revisit the baseline after origin moves, hostname changes or shifts in audience.
Implementation & checks
- 01
Define the audience
Identify primary countries, carriers and devices.
- 02
Test representative resources
Test pages, small assets and large files separately.
- 03
Confirm delivery scope
Use the findings to agree on coverage, policies and operations.