Kedge runs workloads in eleven regions. Latency-aware routing sends each client to a nearby edge; autoscaled instances follow demand across compute regions.
The combined map shows the best measured round-trip time to any region. Select a region to see its reach, or hover a city for exact measurements.
regions
| code | location |
|---|---|
fsn |
Falkenstein, Germany |
hel |
Helsinki, Finland |
vin |
Vint Hill, Virginia, US |
hil |
Hillsboro, Oregon, US |
lax |
Los Angeles, California, US |
gru |
São Paulo, Brazil |
nrt |
Tokyo, Japan |
sin |
Singapore |
bom |
Mumbai, India |
syd |
Sydney, Australia |
cpt |
Cape Town, South Africa |
Static files serve at the edge. Dynamic requests cross the encrypted fleet mesh when the nearest warm instance is elsewhere. Stable members run in one region at a time and can move without changing identity.
map data
The map uses WonderNetwork city-to-city ping data. The combined layer colors each sampled city by its best measured round trip to a Kedge region. 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 for HTTPS, private networking, and CDN behavior.