Failover control

Record set proof. Not signed in. Actions will be refused.

Break-glass sign in

Use this when the usual sign-in cannot be reached. Every use raises an alarm.

Readers are being served by the primary cloud

Nothing is forced. This edge is standing by.

Freshness of this edge

HEALTHY sequence=1786349227 primary=unreachable

Choosing between the primary cloud's regions

Not available from here right now. These controls act on the primary cloud, and this page could not reach it. That is expected if that cloud is the thing that is broken, and it is why the control above does not go through it.

What this page is and is not showing you

This page shows the force flag, which is what this edge publishes. It is not the same thing as where readers are actually being served from. The two can differ: a health check can be unreachable, a record can be misconfigured, or a change can still be moving through the domain name system. If it matters, load the public site yourself and check which copy answers.

Both controls take effect by changing one published object. Nothing here calls the primary cloud, so both work while that cloud is unreachable. Changing the record set back is bounded by the record time to live, so allow a minute or two before concluding that nothing happened.