Status Pages
Overview
A status page is a public page showing the health of the services you choose, along with uptime history and any incidents you have published. It gives your users somewhere to look when something is wrong, instead of your inbox.
Every status page is published at:
https://status.pingniner.com/your-slugand can also be served from your own domain.
INFO
The number of status pages you can create depends on your plan — one on Free and Hobby, up to ten on Enterprise. See Plans & Limits.
What a status page shows
- Overall status — a single headline reflecting the worst state among your services.
- Each service, with its current status and a 90-day uptime bar.
- Incidents from the recent past.
- Updates you publish, either manually or automatically.
- Optionally, a subscribe form and a report an issue form.
Statuses come from the monitors behind each service, so a monitor in Down shows as down publicly. What counts as Down versus Degraded is decided by your triggers — worth checking before you make a page public.
Creating a status page
- Go to Status Pages and click New Status Page.
- Enter a Name. This is the title shown on the page.
- Enter a Slug — the URL segment after
status.pingniner.com/. It must be unique across all Pingniner status pages, and at most 64 characters. - Save.
Everything else is configured after creation, from the page's own tabs.
The status page tabs
| Tab | What it does |
|---|---|
| Overview | Current state, its public URL and custom domain, latest updates and reports |
| Updates | Publish and manage incident updates — see Services & Updates |
| Services | Choose which monitors appear and how they are labelled |
| Reports | Issues submitted by visitors — see Reports & Subscribers |
| Subscribers | People subscribed to email updates |
| Settings | Everything else: general, custom domain, text, branding |
Automatic updates
Under Settings → General, Auto updates publishes updates for you when a monitored service changes state. Turn it on and Pingniner posts an update when a service goes down and another when it recovers.
Auto updates on degraded services extends this to services that are degraded rather than fully down. Leave it off if you would rather only announce real outages.
The wording is fully customisable, including a {service} placeholder — see Appearance & Text.
TIP
Auto-updates are the difference between a status page that reflects reality and one that says "All systems operational" during an outage because nobody remembered to update it. Turn them on.
A service in a maintenance period will not have an outage published for it, so planned work does not appear as an incident.
Making the page useful
- Pick services your users care about, named the way they would name them. "API" and "Website", not "prod-lb-01".
- Keep the list short. A status page listing forty internal monitors is a dashboard, not a communication tool.
- Check your trigger impacts. A response-time trigger set too tight will show your service as degraded when it is fine.
- Publish an update even when auto-updates are on. Automatic updates say what; people want to know why and for how long.
Next steps
- Services & Updates — choosing monitors and publishing incidents
- Custom Domain — serving from
status.your-domain.com - Appearance & Text — branding, theme and every visible string
- Reports & Subscribers — visitor reports and email subscriptions