Set up a status page

Turn on the Status module, add services, report incidents, schedule maintenance, and manage email subscribers and the RSS feed for your public status page.

A public status page lets you report incidents, show uptime, and notify subscribers before customers have to ask. This article covers turning the status page on, services, incidents, maintenance, subscribers, and the RSS feed.

Turn on the status page

The status page is off by default, on Quackback Cloud and on self-hosted installs alike.

Go to Settings > General.
Turn on the Status module.
Your status page is published at /status on your portal domain.

Workspace-level options (general settings, visibility, and notifications) live in Settings > Status.

Manage it

Find incidents, maintenance, and services in Admin > Status:

Overview: the current state at a glance
Open incidents: anything active right now
Scheduled maintenance: upcoming windows
All incidents: full history
Services: the components your page reports on
Templates: reusable incident content
Subscribers: who is signed up for updates

Services

Add a service for each part of your product you want to report on, for example "API", "Dashboard", or "Email delivery". Group related services so the public page reads cleanly.

Each service has a status: operational, degraded performance, partial outage, major outage, or under maintenance. You can choose whether a service shows an uptime bar publicly.

Note: Status is not monitored automatically. Quackback does not ping your endpoints. A service's status changes when your team sets it, when an incident affects it, or when a script or monitoring tool updates it through the API. The uptime bar is calculated from that status history. See FAQ: Status page uptime is set manually.

Tip: Keep services at the level customers care about. "Database" means little to most visitors. "Dashboard" or "API" does.

Report an incident

Create an incident, set its impact, and pick the services it affects. Post updates as you learn more, moving the incident through Investigating, Identified, Monitoring, and Resolved. Each update appears on the incident's page in order, so subscribers and visitors can follow along.

Start from a template instead of writing from scratch. Save common scenarios (a known upstream outage, a routine restart) as templates from the incident composer.

Schedule maintenance

Maintenance has its own lifecycle: Scheduled, In progress, Verifying, and Completed. Set a start and end time in advance so the window shows on the status page before it begins.

Email subscribers

Visitors can subscribe to updates for the whole page or for specific services. Subscribing requires signing in to the portal. Admins can also add subscribers directly, import a list, and export the subscriber list.

To stop receiving emails, a subscriber signs in to the portal and turns off the subscription in the same panel they used to subscribe.

RSS and API

Every status page publishes an RSS feed of resolved incidents at /status/feed. To update services and incidents from scripts or monitoring tools, use the Status API.