Status page
A customer status page, run from the tool that pages you
Oncallz gives each organization a public status page: components with 90-day uptime, incident statements with updates, and email or Slack subscriptions. An alert can prepare a draft for you, but nothing reaches customers until a person reviews and publishes it.
Components and uptime
Group what customers depend on — API, checkout, dashboard — and show each one’s status with a day-by-day uptime bar. The headline always reflects the worst status present.
Drafts from alerts, published by people
A matching alert prepares a draft in plain customer language with the affected components filled in. Customers see nothing until an admin or team lead publishes it.
Subscribers and reports
Customers follow by email (with a confirmation link) or in a Slack channel. A published post-mortem statement appears under its incident on its own.
What is on the status page?
Your page lives at status.oncallz.com followed by a name you choose. At the top, a banner says All systems operational, Degraded performance, Partial outage or Major outage, taken from the worst component.
Below it come the components, grouped as you like, each with its current status and a bar per day for the last 90 days, plus overall uptime for 24 hours, 7 days, 30 days and 90 days.
Active statements show their updates in order, and an incident history lists past ones. You can add a support link and an intro, and the page carries your own title. It is off until an admin switches it on in the organization settings.
How do statements work?
A statement is what you tell customers about one incident. You write the headline and message, pick the affected components and their status, and post updates as things change:
- Investigating, Identified, Monitoring and Resolved — the usual progression, with an impact level.
- Per-component status — mark what is fixed as recovered and leave what is still affected; downtime up to the fix stays in uptime.
- Corrections — fix a typo or wording after the fact. Corrections are not sent to subscribers.
- Past outages — record one that happened before you had a page by choosing its dates; no notifications go out for it.
Can alerts write the statement for me?
Optionally. Choose the lowest alert severity that should prepare a draft — critical by default — or never. A matching alert creates a draft with a neutral headline and message, and the components that alert’s team or integration feeds.
The draft is invisible to customers. Someone reviews the wording and components, then publishes it, or dismisses it (dismissed drafts can be reopened). When the internal incident is resolved, the published statement is resolved with it.
Who can publish?
Speaking to customers is more sensitive than acknowledging an alert, so it is limited:
- Admins set up the page, define components and manage subscribers.
- Admins and team leads open statements, post updates and resolve them.
- Responders see the page and drafts’ existence in their own incidents, but cannot publish.
- Deleting a statement is for admins, and only meant for one posted by mistake; a real outage should be resolved, not deleted.
How do customers follow along?
The page has a subscribe box. Email subscribers confirm through a link first; Slack subscribers paste an incoming webhook URL for their channel.
Every new statement and update goes out to confirmed subscribers (you can switch notification off for a single update), every message links to unsubscribe, and nothing is sent while the page is off. Admins see and can remove subscribers from the console.
Post-mortem reports on the page
When a post-mortem’s public statement is published, it appears under the matching statement, or in the history on its own if there is none. It is one record, not a copy: take the report down and it leaves the page too. See the post-mortems page for how that statement is written.
Managing it from tools and assistants
The status page is part of the API and the MCP server. An assistant can read the status-page console, record historical outages with their actual start and end times, post updates and correct wording.
Publishing follows your role and the independent outage and detail visibility controls; subscriber notifications default to off through MCP.
And the internal wall board?
Separately, Oncallz still offers an internal, read-only status board for an office TV or operations room: open incidents with live counts by severity and who is on call right now.
It shows your real alert titles, team names and on-call names, so it is for your own people, optionally behind a shared password, and refreshes every 30 seconds.
Do not put that board in front of customers — use the status page above for that.
What it does not do yet
Be aware of the edges: the page is served from Oncallz’s status address, not a hostname of your own; there is no RSS feed; and scheduled maintenance announcements are not part of the page.
Frequently asked questions
Does the status page need a login?
No. Customers open it from its link and can subscribe without an account. Nothing on the page can be changed by visitors, and nothing from your internal incident records appears unless you write it into a statement or publish a post-mortem’s public statement.
Will an alert publish itself to my customers?
Never. At most an alert prepares a draft, and a person has to publish it. You can also turn drafting off entirely and write every statement by hand.
Can customers subscribe to updates?
Yes, by email or to a Slack channel. Email subscribers confirm through a link and every message includes an unsubscribe link. You decide per update whether to notify subscribers.
Can I use my own domain, like status.example.com?
Not yet. The page is served from Oncallz’s status address with a name you choose. A custom hostname is planned but not available today.
Who may post to the status page?
Admins and team leads. Admins also manage the page settings, components and subscribers. Ordinary responders cannot publish to customers.
Can I record an outage that happened before we set the page up?
Yes. Open a statement and choose when it started and ended. Past statements add to the history and the uptime bars, and they do not notify subscribers.
Is it included in the price?
Yes. The status page, subscriptions and public incident reports are part of the single Oncallz plan at $4 per user per month, billed quarterly. Customers who only read or subscribe to the page do not need an account, so they do not count as users.
Related
- Post-mortems Write blameless post-mortems with timelines and action items, and publish a customer-facing incident report with one click.
- On-call scheduling Build daily, weekly or custom on-call rotations with automatic handoffs and overrides, so every alert reaches whoever is on call right now.
- Microsoft Teams Post incident updates — triggered, acknowledged, escalated, resolved — to a team’s Microsoft Teams channel, alongside phone and SMS paging.
Ready when the pager goes off.
Create your workspace in minutes. Free to start, no credit card — $4 per user a month when you’re ready.