Status pages
A status page shows your customers whether your services are working, based on the same checks that alert your team. No manual updates are needed: when an incident opens, the page shows it; when the monitor recovers, the page returns to operational.
Create a page
- Create a status page and give it a name.
- Choose a slug. The page is published at
https://<slug>.status.asniher.com. - Select the monitors to display. Optionally give each one a display name (for example "API" instead of
api-prod-eu-healthz) and set their order.
Slugs use lowercase letters, numbers and hyphens, are 3 to 40 characters long, and must start and end with a letter or number. A few names such as www, api, status and admin are reserved.
What visitors see
- Overall status at the top, derived from the selected monitors.
- Each monitor with its current status and a 90-day uptime bar. Each bar is one day: green at 99.9% or higher, amber from 95% to 99.9%, red below 95%, and grey for days without data.
- Incident history with start time, duration and the root cause you recorded.
Monitor URLs, request headers and other configuration are never shown on the public page.
Root cause
Incidents open and close automatically. After an incident, add a short root-cause note in the dashboard (for example "Database failover took 4 minutes"). It appears in the incident history and in recovery alerts sent after it is set.
Limits by plan
| Free | Pro | Team | |
|---|---|---|---|
| Status pages | 1 | 3 | Unlimited |
| Custom domain | — | Yes | Yes |
| "Powered by Asniher" footer | Shown | Hidden | Hidden |
Next steps
- Serve the page from your own domain: Custom domains.
- Show live status in your README or website: Status badges.