Status Pages
This page covers the full lifecycle of a status page: create it, add services, publish, post and resolve incidents, and manage who gets emailed.
For what a status page is and how service health is derived, see On-Call Overview → Status pages.
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 configure everything before anyone sees it.
Add your services
Add the components you want to show, for example API, Dashboard, and 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. Your incidents drive it (see below).
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 unpublish it.
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.
Add timeline updates
Add timeline updates to an incident as you learn more. Each update carries a new status and a message. The updates stack into a chronological thread that your users can follow. Moving the status to Monitoring, then Resolved, moves the incident through its lifecycle.
Resolve it
Set the status to Resolved. Autoheal stamps the resolved time and recalculates the affected services. The services return to Operational once no open incident affects them. Autoheal also 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, because only live activity notifies people.
Post an update
Use an update post for anything that isn't a lifecycle incident, such as 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. At this point, this is what end users see.
| 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.
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, for example status.yourcompany.com.
In the page's Settings → Custom domain (CNAME):
- Enter your subdomain and click Add.
- At your DNS provider, add the CNAME shown under "Point this CNAME to" so your domain points at Autoheal.
- Contact Autoheal support (support@autoheal.ai or on Slack). We issue the TLS certificate for your domain. We send you an ownership-validation record to add at your DNS provider. We also 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, and 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.
Show several pages on one address (index page)
If you run one status page per product, region or environment, an index page puts them all on one address, such as status.yourcompany.com. Visitors see each page's current status and open the one they care about. Each page keeps its own incidents and subscribers.
- On Status Pages, click New status page → Index page.
- Give it a title and a URL, then tick the status pages to list. You can list up to 50 pages from the same project.
- Click Create index page. On its Pages tab you can drag pages into a new order, add or remove them at any time. Each change saves at once.
- Make it public when it's ready. To serve it on your own domain, follow Use your own domain for the index page.
What visitors see:
- A banner that says how many of the listed pages are affected, or All systems operational. A page counts as affected when one of its services is down or it has an open incident.
- Active incidents: the open incidents across all listed pages, newest first, each with the page it's on and when it started. Up to three are shown per page, with a link to the page for the rest.
- One row per page with its title, description and current status. The status is the same one the page itself shows. Each row links to that page.
- Each row also lists the page's services and their statuses, the ones with problems first, so visitors can see what's wrong before opening it.
- Private pages you've listed stay hidden until you make them public.
An index page has no services, incidents or subscribers of its own. Visitors subscribe on each page they want updates from. An index can list only status pages, not other index pages.
Subscriptions
Visitors to a public status page can subscribe by email to be notified when you publish or update posts. Autoheal uses double opt-in so people only ever receive mail they explicitly asked for.
How a visitor subscribes
- On the public page, the visitor enters their email address and submits.
- Autoheal sends a confirmation email ("Confirm your subscription to <your page> status page") from
notifications@autoheal.ai, shown as "<Your Page> Status Page (Autoheal)". - The visitor clicks Confirm subscription. Only after this step are they subscribed. The confirmation link is valid for 72 hours. After that, they subscribe again to get a fresh link.
Until they confirm, no further email is sent. Re-submitting the same address within the confirmation window won't spam them, since it re-sends the same pending confirmation rather than a new one.
What subscribers receive
Once confirmed, a subscriber is emailed whenever you do one of these things:
- Publish a new incident.
- Post an update to an incident (including when you resolve it).
- Publish an update post.
Each notification includes the post title, the latest message, any affected services, and a link to the status page. Every message also includes a one-click Unsubscribe. It appears as a link in the email body and as the native "Unsubscribe" button that mail apps show (RFC 8058). As a result, it works everywhere.
Subscribers receive all of a page's updates. There is no per-service subscription at this time.
Unsubscribing
A subscriber can unsubscribe at any time using the link in any email or their mail app's built-in Unsubscribe button. Unsubscribing is immediate and they'll receive nothing further. If they later change their mind, they can subscribe again, which re-runs the confirmation step.
Adding subscribers as an admin
You can add a subscriber's email from the page's Subscribers view. They still receive the same confirmation email and must confirm before they get updates. This is because Autoheal never adds an unconfirmed address to your live send list.
Delivery & privacy notes
- Confirmed only. Notifications go only to addresses that completed double opt-in and haven't unsubscribed.
- Bounce/complaint protection. Addresses that hard-bounce, are flagged as spam complaints, or land on a suppression list are dropped from future sends to keep your sender reputation healthy.
- Subscriber email addresses are treated as personal data and are not exposed on the public page.