Incident — DOWN. 404 on every path, while the deployment itself is healthy.
Measured 2026-09-10
| what | value | reading |
|---|---|---|
| deployment URL | 302 | the passphrase gate, working correctly |
| strongroom-elections.vercel.app | 404 | |
| custom domain, every path | 404 | / /home /index.html /deck /pilot |
| DNS | 200 | correct CNAME to cname.vercel-dns.com — resolution is not the problem |
DNS resolves to Vercel and Vercel declines to route the hostname. That is the signature of the domain still being held by a different project. There is no "move" for a Vercel domain — it must be deleted from the project that holds it before it can be added to another, and adding it while it is held elsewhere fails quietly like this.
Why this is not a DNS problem
The distinction the grid below draws is the whole diagnosis. No DNS means the subdomain was never published — that is a choice, not a fault, and most of the corpus is in that state. 404 means the name resolves to Vercel and Vercel then declines to serve it.
Observed 2026-09-10 by HTTP GET on <name>.bornbetween2generals.com.
no DNS means never published — not a fault. 404 means published and broken, and there is exactly one.
The reading
DNS resolves to Vercel and Vercel declines to route the hostname. That is the signature of the domain still being held by a different project. There is no "move" for a Vercel domain — it must be deleted from the project that holds it before it can be added to another, and adding it while it is held elsewhere fails quietly like this.
Action: Confirm which project holds the hostname, remove it there, re-add here. Outward-facing — not done without a decision.
How this page works
A 64-second spoken walk-through of what is on this page and why it matters.