Status pages
A status page shows your users which services are up, what is being fixed and 90 days of history. You can have as many as you need: one per product, or one per client.
On this page
Create and edit a page
No page is made for you, and adding a site never puts it on one. To make a page, go to Status pages and press Create status page (or New status page once you have one). Press Edit to open the editor; the preview beside it shows the page on a desktop or a phone as you type.

- Name and address
- The page lives at /status/your-name. Changing the address breaks links you already shared.
- Sites shown
- Tick the sites the page shows. A site is on one page at a time.
- Service groups
- Group services under headings, such as “Website” and “API”. Without groups, your site categories are used.
- Branding
- A tagline, your website, a logo (PNG, JPEG, WebP or SVG), a theme and a language.
- Announcement
- A banner at the top: a notice, maintenance or an incident.
Themes: Midnight, Slate, Graphite, Deep Ocean, Daylight and Sepia, or Match visitor, which follows the visitor’s light or dark setting. Languages: English, Українська, Deutsch, Polski and Español, or automatic. Your own texts are shown as you wrote them.
Owners and admins edit pages. A workspace keeps at least one.
Use your own domain
- 1.In the editor, open Your own domain, type the address, such as
status.example.com, and press Add domain. - 2.At your DNS provider, add the record the editor shows: a CNAME, or an A record for a bare domain. Remove any AAAA record on that name.
- 3.On Cloudflare, leave the proxy off (the grey cloud).
- 4.Press Check DNS, or leave it to us. When it reads Verified, the page is served there. The HTTPS certificate is issued on the first visit.
While the domain waits, we check its DNS again by ourselves: every 5 minutes for the first hour, then less often, for three days. The editor says when the next check is. When the record is found, the domain turns Verified and the owner and admins get an email. After three days the checks stop; pressing Check DNS starts them again. The /status/… address keeps working. For example.com/status, the editor’s On your site section has a redirect ready for Cloudflare, nginx, Apache, Vercel, Netlify, Next.js and WordPress.
Make a page private
Plan/Pro and up
Under Who can see it, switch on Private page and choose one or more ways in. Any one is enough:
- Password
- 8 to 128 characters. A new password signs out everyone who used the old one.
- Work email
- Visitors from the email domains you list get a 6-digit code by email.
- IP allowlist
- Addresses or ranges, IPv4 or IPv6. Add my address fills in yours.
A visitor stays signed in for 30 days. Members of your workspace always get in. Private pages are never indexed by search engines.
Subscribers
Visitors press Get updates, enter their email and confirm it from their inbox. Then they get an email:
- when a service on the page goes down and when it is back. If you pause its monitoring while it is down, they hear that monitoring is paused instead, since nothing checked that it is back;
- about maintenance: a day before it starts, when it starts and when it is done, and when it is changed, cancelled or ended early;
- when you post an incident report with Email subscribers ticked.
One outage gets one email when it starts and one when it ends. When a report is linked to the detected incident, whichever speaks first wins: an automatic outage email already sent leaves the report’s first update unemailed, and an automatic “resolved” its Resolved update. Email subscribers then starts unticked and says why; tick it to send anyway. A report emailed first holds back the automatic emails instead; if its email fails, or it was posted without one, the automatic email still goes out.
Emails are in the reader’s language and have a one-click unsubscribe. You can see and remove subscribers in the editor under Subscribers.
Incident reports and postmortems
An incident report is what you tell visitors about an outage, in your words. In the editor, under Incident reports:
- New report
- A title, a status (Investigating, Identified, Monitoring or Resolved), the impact on each service and a message.
- Post an update
- A new status and message on an open report.
- Postmortem
- A write-up of a resolved report in Markdown, shown in the page’s history. It is not emailed.
Draft with AI writes a first version for you. On an incident, Draft update with AI opens this form already linked to it. See Incidents. Edits to a report already published are not emailed.
In the postmortem editor, Draft with AI writes the whole postmortem from the report, its updates and the linked incident, in the page’s language, with gaps marked [[ ]] where the data cannot tell, such as the root cause. It cannot be published while a gap is left. On the incident, the same draft starts from Draft postmortem with AI. See Incidents.
White label
White label removes “Powered by Heedery” from a page, its sign-in and subscribe screens and its emails. The tab shows your page’s name and logo. Subscriber emails can come from your own domain, such as status@example.com. Only a white-label page can send from your domain. Starter has no white label; on Pro and Team you buy it for each page; Agency includes it on 5 pages and bills each page after those; Enterprise has it on every page.
It is bought per page. Only the owner can turn it on.
- Starter
- Not available on this plan
- Pro
- $49 a page per month
- Team
- $29 a page per month
- Agency
- 5 pages included, then $19 a page per month
- Enterprise
- Included in your contract
NoteA white-label page also drops the Heedery credit from the client reports built on it.
A status badge
Under On your site, the editor has A status badge for your footer: an image with the page’s current status, ready to paste.
The badge lives at /api/status/your-name/badge. Add ?type=uptime&days=30 for uptime over 7, 30 or 90 days. Private pages have no badge.
Still stuck? Write to us.