Checking live Galaxy status…
This page combines the public metrics feed with static routing knowledge so operators and visitors can see what is live, what is pending, and which surfaces are currently using fallback routes.
This page combines the public metrics feed with static routing knowledge so operators and visitors can see what is live, what is pending, and which surfaces are currently using fallback routes.
The banner below updates from the live metrics endpoint. If the endpoint is unavailable, the page falls back to a warm-check state instead of faking green.
These cards summarize the front-door product surfaces people actually touch today: identity, control, docs, and agent connection.
Signup, sign-in, password recovery, and hatch entry stay available through the working auth surface.
Operational dashboard and module surface remain reachable on the branded control route.
Documentation hub, architecture pages, and open-source explainers are publicly available.
Agent connection surface is live on the branded bot domain, with public product pages available now.
Duck Galaxy currently uses a mix of fully live branded apex domains and safe fallback routes while certificates finish propagating.
Visitors use the live auth route while certificate issuance completes.
Fallback → /auth.html
Mission Control resolves on the branded domain.
Primary → https://duckcontrol.com
Connector home is live on the bot domain.
Primary → https://spaceduck.bot
Framework home stays reachable through CloudFront while TLS finishes.
Fallback → /mighty-space-duck-home.html
Brand home is live on the public apex domain.
Primary → https://duckgalaxy.com
The page intentionally distinguishes between public health, pending certificate work, and known-safe fallback routing. It is meant to be honest, not cosmetically green.
GET https://czt9d57q83.execute-api.us-east-1.amazonaws.com/prod/beak/metrics
duckgalaxy-home.html and status.html share the same domain-state map
UI state: warn / error instead of fake-live