Public status page
Publish service health, let visitors subscribe, and communicate during an incident.
What you will build
By the end of this tutorial you will have:
- A live public status page showing uptime for selected monitors
- Email subscriptions enabled so customers can follow incidents
API
Dashboard
Payments
Prerequisites: at least one monitor configured and working
Step 1: Create the status page
- In the sidebar, click Status Pages.
- Click + New Status Page.
- Name the page, for example
Acme Cloud Status.
The default URL is generated automatically from the page name with a short unique suffix (for example /status-page/acme-cloud-status-7c0f). You do not pick the slug yourself.
- Under Monitors, select the monitors that represent customer-facing services.
- Click Create and customise.
Your page is now live at the default platform URL shown at the top of the status page configuration.
Step 2: Verify the page
Open the status page URL in a new browser tab (no login required). You should see:
- Your page title and the overall status banner
- Each selected monitor listed with its current status
- Availability history and recent uptime for each included monitor
Step 3: Add a custom domain when enabled
Custom domains depend on the workspace's current Status capability and the platform's domain configuration. Follow Set a custom domain. That guide uses the DNS target returned by HowlOps instead of duplicating a value here.
Step 4: Enable email subscriptions
Email subscriptions let visitors receive automatic notifications when an incident opens or resolves.
- Open the status page configuration and find the page settings.
- Turn on the Subscribe (email + RSS) toggle.
- Save. A Subscribers section then lets you review confirmed and pending subscribers.
Visitors will now see a Subscribe to updates button on your status page. They enter their email, receive a double opt-in confirmation, and are subscribed.
Step 5: Communicate during an incident
When an incident is active on any of your monitored services, it appears automatically on the status page. To replace its generic label with a customer-visible message:
- Open Status pages → Configure and scroll to the Incidents section (step 7).
- Click Post public update on the incident, pick a phase, and write a message (e.g. "We are investigating elevated error rates in the EU West region.").
- Submit. The update appears on the status page immediately.
Post follow-up updates as the incident progresses. Each update is timestamped and shown in chronological order.
Step 6: Customise the page (optional)
Open Status Pages → Configuration and use the options shown for this workspace. Branding, custom CSS, and custom domains are capability-controlled, so the product is the source of truth for which controls are available. Current capability details and prices live on pricing.
What's next
- Tutorials: Set up Slack alerts: get notified in Slack when incidents open
- Getting started: First status page: quick reference for status page basics
- Concepts: Incidents: understand the incident lifecycle
Was this page helpful?