weu.azure.regions.n8n.skakelaar.comchecking
https://weu.azure.regions.n8n.skakelaar.com/healthz—
n8n cloud platform candidate lab
Regional Resilience Control Room
A live, disposable proof that one workflow can survive region and cloud boundaries without hiding the operational trade-offs.
request served by aws/eu-central-1 via fra.aws.regions.n8n.skakelaar.com
fra.aws.regions.n8n.skakelaar.comchecking
https://fra.aws.regions.n8n.skakelaar.com/healthz—
How this request reached n8n
1 · Public DNSGlobal edge chooses a healthy origin.
→
2 · Regional LBCloud load balancer reaches the Istio gateway.
→
3 · IstioGateway and VirtualService enforce the public route.
→
4 · Service DNSn8n.n8n.svc.cluster.local
→
5 · n8nThis workflow renders the control room.
CoreDNS — inside Kubernetes
Pods query the cluster DNS Service. CoreDNS watches Kubernetes Services and EndpointSlices and resolves names such as n8n.n8n.svc.cluster.local. Namespace search domains come from the pod's resolver configuration.
ExternalDNS — outside Kubernetes
ExternalDNS watches annotated Services and reconciles public records into the regional Azure DNS or Route53 child zone. It does not answer pod DNS queries and it is not a reverse proxy.
Product-native readiness gate
Run a credential-free n8n policy workflow against the region serving this page.
Ready.