Geographic routing

Send each user to the region closest to them, by DNS geolocation, latency measurements or anycast. It cuts round-trip time and can keep data in the user's jurisdiction.

Where it shows up in real systems

  • DNS

    Managed DNS answers in about a millisecond thanks to resolver caches. Latency-based, geolocation and failover policies send users to the closest or healthiest region; a low TTL makes failover faster but increases queries.

    In production: Amazon Route 53, Cloudflare DNS, Azure DNS, Google Cloud DNS

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox