Status pages
A status page is a public URL that shows whether your services are up. You send people there during an incident instead of answering the same question repeatedly.
Setting one up#
Configure it under status page settings: choose a slug for the public URL, give the page a title, and pick which services appear on it.
The page is public by design — anyone with the link can see it, without an account. That is what makes it useful when your product is down.
What it shows#
- An overall state: all systems operational, partial outage, or major outage.
- The individual services you listed.
- Incidents you have posted, with resolved ones marked as such.
Posting an incident#
When something breaks, post an incident. A short, honest note beats silence: what is affected, what you know, when you will update next.
Update it as things change and mark it resolved when they are fixed. People forgive outages more readily than they forgive being left guessing.
A status page that runs on the same server as the thing that just went down will be down too, exactly when it is needed. If you can, point your status page's DNS at somewhere independent of the infrastructure it reports on.
What to list#
List what your users would notice — the app, the API, the things they interact with. Internal components they have never heard of add noise without telling them anything they can act on.
Raise a ticket and someone will pick it up. Sign in with the same account you use for the panel.
Raise a ticket