Edge to Region · Lambda Web Functions × Aurora DSQL
Live · polling every 2s
This request was served from
…
resolving
Round trip
–
DSQL query
–
Database peer
–
CloudFront POP
–

Which Region answered · last 60 requests

Origin picked by Route 53 latency DNS, resolved at the edge.

Regions · latency measured from your browser

Simulate an outage: that Region returns 503, its Route 53 health check fails within ~20s, and DNS stops sending traffic there. Outages expire on their own after 2 minutes.

Sign the wall

Written through the nearest Region into Aurora DSQL. Peered clusters in Ireland and Frankfurt keep one strongly consistent database, so every Region reads the same rows right away.

Messages

  • Loading…

How a request gets here

CloudFrontYour request lands on the nearest edge location, with TLS for the custom domain.
Lambda@Edge + Route 53The edge resolves a latency-routed CNAME. Unhealthy Regions drop out of the answer, so you fail over to the next-closest one.
Lambda Web FunctionA Hono server runs in a PerRegion endpoint in 4 Regions: no VPC, scale to zero, up to 64 concurrent requests per environment.
Aurora DSQLActive-active peers in eu-west-1 and eu-central-1, with a witness in eu-west-2, and IAM token auth instead of passwords.