Emergency Control Panel

How failover works

• Every Nexus mirror runs a HeartbeatGuard that pings /api/heartbeat every second.
• After 3 consecutive failures it fetches the live chain from this panel (/api/chain).
• It redirects the user to the first domain in the chain that responds and is not marked down here.
• nexus-social.pages.dev has a 302 redirect worker that reads this chain and always sends visitors to the current primary.

When a domain goes down

• Users are auto-redirected within ~3 seconds (3 heartbeat failures).
• You can also mark it down here manually — it will be skipped in the chain immediately.
• To change the primary, drag it to position #1 (or use the ↑ button) and make sure it is not marked down.

Re-deploying a mirror

If you actually need to push new code to a mirror, run node scripts/deploy-mirrors.js --only <name> from the social-platform repo. (Direct-upload Pages deployments can't be retried via the CF API.)

Access

This panel is available at nexus-emergency.pages.dev. Any Tier 5 head admin can log in (Admin1, Admin2). Sessions expire after 8 hours.