Latency-aware routing sends each client to a nearby edge; autoscaled instances
follow demand across ten compute regions, plus an edge point of presence in
Los Angeles.

The combined map colors each sampled city by its best measured round-trip time
to any region. Select a region to see its reach, or hover a city for its
measurements.

(An interactive latency map is available at /docs/coverage.)

## regions

| code | location |
|---|---|
| `fsn` | Falkenstein, Germany |
| `hel` | Helsinki, Finland |
| `vin` | Vint Hill, Virginia, US |
| `hil` | Hillsboro, Oregon, US |
| `lax` | Los Angeles, California, US (edge only) |
| `gru` | São Paulo, Brazil |
| `nrt` | Tokyo, Japan |
| `sin` | Singapore |
| `bom` | Mumbai, India |
| `syd` | Sydney, Australia |
| `cpt` | Cape Town, South Africa |

## map data

The map uses WonderNetwork city-to-city ping data, with historical samples
filling links the current scrape misses. Color between sampled cities is
estimated and fades to “no data” where measurements are sparse. This is
network geography, not a live browser test or latency guarantee.

See [network & domains](/docs/network) for HTTPS, private networking, and CDN
behavior.