Managing your status page

This walks through the full lifecycle: create a page → add services → publish → post and resolve incidents → post updates.

1. Create a status page

Create a page and give it a title (e.g. Acme US) and an optional description. Each page gets its own public web address of the form your-page.status-pages.<your-domain>.

New pages start Private, so you can set everything up before anyone sees it.

2. Add your services

Add the components you want to show — for example API, Dashboard, Webhooks. For each service you can set:

• Name and an optional description.
• Visible — whether it appears on the public page.

Every service starts Operational. You won't set the live status by hand — it's driven by your incidents (see below).

3. Publish the page

When the page is ready, switch its visibility to Public. It's now live at its web address. Switch back to Private at any time to take it down.

Use your own domain (optional)

By default your page is served at your-page.status-pages.<your-domain>. You can also serve it on your own subdomain — e.g. status.yourcompany.com.

In the page's Settings → Custom domain (CNAME):

1. Enter your subdomain and click Add.
2. At your DNS provider, add the CNAME shown under "Point this CNAME to" so your domain points at Autoheal.
3. Contact Autoheal support (support@autoheal.ai or on Slack). We issue the TLS certificate for your domain, send you an ownership‑validation record to add at your DNS provider, and route your domain. Once that's done, your page is live on it.

Your default …status-pages.… address keeps working throughout the setup, and continues to work alongside your custom domain afterward.

What you can use:

• A subdomain you control, like status.yourcompany.com — not your root/apex domain (yourcompany.com), because a root domain can't be pointed with a CNAME.
• One custom domain per status page, and it must not already be in use by another page.
• Standard hostname characters (letters, digits, hyphens). It must be your own domain — not an Autoheal …status-pages.… address.

4. Post an incident

An incident is for something actively affecting your services. When you create one you provide:

• A title (e.g. Elevated API error rates).
• A status: Investigating, Identified, Monitoring, or Resolved.
• An opening message (markdown).
• The affected services and, for each, the impact (Degraded performance, Partial outage, Major outage, Under maintenance).

As soon as you post it, the affected services show the impact you chose, and the incident appears under Active incidents.

Post updates as it develops

Add timeline updates to an incident as you learn more. Each update carries a new status and a message, and they stack into a chronological thread your users can follow. Moving the status to Monitoring, then Resolved, walks the incident through its lifecycle.

Resolve it

Set the status to Resolved. Autoheal stamps the resolved time, recalculates the affected services (they return to Operational once no open incident affects them), and moves the incident from Active incidents into Recent updates.

Backfilling history? If you create an incident that's already resolved (to record something that happened earlier), subscribers are not emailed — only live activity notifies people.

5. Post an update (announcements & maintenance)

Use an update post for anything that isn't a lifecycle incident — a general announcement or a scheduled-maintenance notice. An update is a single, editable message with no status and no service impact. Edit it in place as plans change. Update posts always appear under Recent updates.

What shows where

Section	Contains
Active incidents	Incidents that aren't resolved yet, with their latest updates
Recent updates	Resolved incidents + update posts from the last 15 days, newest first

Older history remains available through the page's history view.

Next

See Subscriptions for how users sign up to be notified whenever you post or update.