Status Page
A status page is a public web page that shows whether a service and its components are working, lists current incidents and scheduled maintenance, and keeps a history of past uptime. Customers check it, or subscribe to it, instead of contacting support during an outage.
What is a status page?
A status page answers "is it down, or is it me?". It lists your components, such as the app, the API and email delivery, with the current state of each. During an incident it shows what is affected and posts updates as you learn more. Afterwards it keeps a history, so customers can see your track record.
What to put on it
Components customers recognise, not your internal architecture. Clear incident updates with a time and a next update. Scheduled maintenance announced in advance. A way to subscribe, by email or RSS, so customers don't have to keep checking.
Why support teams care
During an outage, every customer who can't find information writes to support. A current status page, linked from your help center and your app, turns hundreds of identical conversations into one page view each.
The status page in Quackback
Quackback's status page has components and component groups, incidents with updates and reusable templates, and scheduled maintenance that starts and completes on its own. It shows uptime history, takes email subscribers for the whole page or for single components, and publishes an RSS feed and a public API. Quackback doesn't monitor your services itself: you set status by hand or through the API from the monitoring you already run. On Enterprise, a status page can be private or show each customer segment only its own services.
Common questions
What is a status page?
A status page is a public page that shows whether a service and its components are working, with current incidents, scheduled maintenance and uptime history.
Does a status page reduce support tickets?
Yes, during incidents. Customers who can see that an outage is known and being worked on, or who are subscribed to updates, are much less likely to open a ticket about it.
Have another question? Talk to the team.