status.yourcompany.com looks more trustworthy than something.statusprovider.com. The setup is usually simple. The failures are almost always DNS, caching, or putting the page on the same broken infrastructure.
The usual steps
- Create the status page in your provider (Tallwatch included) and note the hostname they give you.
- In DNS, add a
CNAMEfromstatusto that hostname. Some apex setups needALIAS/ANAMEinstead — follow your DNS host's docs. - Wait for propagation. Minutes to hours. Do not panic-edit every five minutes.
- Enable the custom domain / TLS in the status product so it serves a valid certificate for your name.
- Load
https://status.yourdomain.comin a private window and on phone cellular. - Link it from your app footer, docs, and support macros.
Mistakes that make you look offline
- Pointing at the wrong target — leftover CNAME from a previous vendor.
- Proxy orange-clouding in a way that breaks the provider's TLS flow (depends on CDN; follow their guidance).
- Announcing before TLS is ready — browsers will scare customers more than a vendor subdomain would.
- Hosting status on the app — when the app dies, so does the explanation. Use a separate host. More on that in why status pages need their own home.
After it works
Subscribe yourself by email. Trigger a test incident in a maintenance window. Confirm the component flips and the email arrives. Add the URL to your incident runbook so nobody pastes a random Notion link during the next outage.
Custom domains are not a vanity metric. They are how customers find you when Google is not the first place they look — and how you look like a team that planned for bad days.