Austin Rose
Lab/Multi-cloud failover

Multi-cloud failover

LiveUpdated 2026-04-26

Continuity planning made visible. Aviation has a Minimum Equipment List — the documented set of degraded-mode configurations a flight can still launch under. This site has one too: weighted multi-cloud routing that survives when one provider goes dark. Polling /origin.json every 5 seconds shows the LB rebalancing in real time.

Built for this
  • 5-second polling + per-origin latency sampling
  • 60-cell rolling visualization of the cloud split
  • Weighted-share computation surfaced live
Built on
  • Cloudflare Load Balancer
  • Cloudflare DNS
Live
AWS share
0%
GCP share
0%
Avg latency
0ms
Errors
0
Samples
0/60
TimeOriginRegionLatency
Topology
CloudflareDNS + weighted routinghealth checksAWS · us-west-2x-origin: aws-us-west-2• CloudFrontCDN• S3Static origin• ACMCertificateGCP · us-central1x-origin: gcp-us-central1• HTTPS Load BalancerCDN• Cloud StorageStatic origin• Managed CertCertificate50 %50 %Visitor → austinrose.me

Cloudflare DNS receives the request, chooses a pool (AWS or GCP) by weighted random with session_affinity: none, proxies to that pool's origin, and returns the response. Each origin stamps a distinct x-origin header at CDN layer so the footer (and this page) can see which cloud served the current view.