Tell customers before they tell you.
Status pages stay in sync with your monitors, on your own domain and brand. Post an update from the incident itself — subscribers get it by email.
Components that follow your monitors.
Group monitors into the components your customers recognise, like Dashboard, Public API or Checkout. Each component shows the worst state of its monitors, so the page changes when your service does, not when someone remembers to update it.
- Operational, degraded, partial outage, major outage and maintenance, in plain language
- Override a component by hand when you know more than the checks do
- Server-rendered pages that load fast, even when everyone is refreshing at once
The component shows its worst monitor’s state.
Write the update where you’re already working.
Post Investigating, Identified, Monitoring and Resolved updates straight from the incident, to one status page or several. The update lands on the incident timeline too, so the postmortem tells the same story your customers saw.
- Mark the affected components as you post
- Email subscribers with the same click, or post quietly
- Past incidents stay on the page as history
- Investigating
- Identified (selected)
- Monitoring
- Resolved
We’ve identified the cause of slower API responses and a fix is rolling out now. Checkout and the dashboard are working normally. Next update by 09:20 CDT.
A status page you don’t have to babysit.
-
Your own domain
Point a CNAME like
Starter and upstatus.acme.devatstatus.pulseback.io; HTTPS is set up for you. -
Your brand
Your name, logo, brand colour and a link to your support site. Remove “Powered by Pulseback” when you’re ready.
Remove branding: Team and up -
Scheduled maintenance
Announce planned work ahead of time. Alerts for the affected monitors are suppressed during the window.
-
Email subscribers
Visitors subscribe with double opt-in, and every update you post can email them. One-click unsubscribe on every message.
-
90 days at a glance
Uptime bars per component from confirmed outages, plus a history of past incidents and how long each took to resolve.
-
JSON for your app
The same status as JSON at
/api/public/status/<slug>, CORS-enabled, for an in-app banner or your own widget.
Status pages
Compare plans- Free
- 1
- Starter
- 1
- Team
- 3
- Business
- 10
- Enterprise
- Custom
Custom domains: Starter and up. Without one, pages live at status.pulseback.io/<your-page>.
Your status page is ready before your first incident.
Every plan includes one, free plan too. Add a component, link a monitor, and share the link.
Join the waitlist