Status page
Tell customers what's happening.Before they ask.
A hosted status page for component status, incidents, and maintenance. Subscribers get updates automatically, so your inbox gets quieter during an outage.
One page for uptime, incidents, and maintenance.
Component-level status
Model the parts of your product customers care about and set each one independently. The overall banner rolls up to the most severe active state, so the top of the page is always honest.
Incidents with a clear timeline
Open an incident, post updates as you investigate and recover, and resolve it. Each update is timestamped into a public timeline customers can follow without asking for a status check.
Scheduled maintenance
Announce maintenance windows ahead of time and mark components as under maintenance while work runs. Customers see planned work as planned, not as an unexplained outage.
Subscribers notified automatically
Customers subscribe once and get updates for every stage of an incident. You write the message; delivery to subscribers happens on its own, so the inbox stays calmer when it matters most.
Write the update once
During an incident, the page and your subscribers should hear the same thing at the same time. Post an update and it goes everywhere, with a timeline customers can follow on their own.
- Post the same update to the page and every subscriber
- Keep incident history as a public record
- Link an incident back to the conversations it affects
- Reuse update templates for faster first responses
FAQ
Frequently asked questions
What is the status page for?
A hosted page where you publish component status, active incidents, and scheduled maintenance. Customers check it before they contact you, which cuts duplicate tickets during an outage.
How do subscribers get notified?
Customers subscribe to the status page and receive updates when you open an incident, post progress, and mark it resolved. Updates go out automatically, so your team writes the message once.
Can I show status per component?
Yes. Define the components that matter to your customers — API, dashboard, webhooks — and set each one independently. The overall banner reflects the most severe active state.
Does it run on my own domain?
The status page runs on your domain with your branding, on Cloud or self-hosted. Incident history stays with you as a public record customers can reference.
Connected platform
Explore the rest of Quackback
One incident, one clear record
Give customers a status page they trust
Start with a 14-day Cloud trial and no card, or run the same platform on your own infrastructure.