demo: load balancing → geo steering
same load balancer as /lb-failover. the
steering policy is geo with region-based pools. requests
from north america (WNAM / ENAM) go to pool-a. requests from anywhere
else go to pool-b. no failure required — this is per-request geographic
routing.
click to fetch. hop on a vpn to a different region for contrast.
# region_pools map
| WNAM (western north america) | → pool_a |
| ENAM (eastern north america) | → pool_a |
| WEU / EEU (europe) | → pool_b |
| OC (oceania) | → pool_b |
| SEAS / NEAS (asia) | → pool_b |
| NSAM / SSAM (south america) | → pool_b |
| ME / NAF / SAF (middle east + africa) | → pool_b |
# how to test the flip
- from a US ip (the button above) → expect
origin=a - connect to a vpn exit in the eu (or asia, etc.)
- refresh — same button, same url, now returns
origin=b - cloudflare picked the pool at the nearest edge based on where the request landed
# why this matters
- latency: send eu traffic to eu origins, us traffic to us origins
- data residency: keep eu user data at eu origins for gdpr
- capacity: overflow one region to another with weighted pools