Status pages

View as Markdown Open in ChatGPT Open in Claude

A status page is a public web page that tells your users and customers whether your services are working. It shows each component’s current state and 90 days of uptime, open incidents, scheduled maintenance, and the last 14 days of history. Anybody with the address can read it without signing in, and people can subscribe to updates. This page shows how to set one up and keep it accurate.

What the page shows

Section	Contents
Banner	The overall state, and when the page was last updated.
Active incidents	Each public open incident with its severity, status, affected components, summary, published updates, and published files.
Scheduled maintenance	Planned and running maintenance windows, with their times and components.
Components	Each component’s current state and, where turned on, a bar of the last 90 days and its uptime percentage.
Past 14 days	Incidents from the last 14 days, with their postmortems.
Get updates	The subscribe form.

The page also has an Atom feed, linked as Atom feed at the bottom. It updates itself every 60 seconds in a browser, and works without JavaScript.

Only incidents declared with Show this incident on the public status page appear, and only their published updates. Internal notes never appear.

Before you begin

Your plan must include the service desk: Enterprise or MSP. See Plans and limits.
To publish the page and remove subscribers, you need statuspage:manage. To add or change components, you need both statuspage:manage and incident:manage. To schedule maintenance, you need incident:manage. See Roles and permissions.
Email to subscribers is sent through your outgoing email provider. See Configure outgoing email.

Add components

Components are the parts of your service the page reports on. Name them the way your users would describe them.

Select Incidents > Components, then New component.
Enter a Name, such as “Customer portal”, and an optional Description.
Optional: enter a Group to list related components together, and a Sort order. Lower numbers appear first within the group.
Choose a Current status: Operational, Degraded, Partial outage, Major outage, or Under maintenance. An open incident overrides this while it runs, so set it by hand only for conditions no incident covers.
To show 90 days of uptime, select Show an uptime bar for this component.
Select Save component.

When more than one incident or window affects a component, the page shows the worst state. A real outage during planned maintenance shows as the outage.

Deleting a component removes its impact history, and with it any outage it recorded in the uptime figures.

Publish the page

Select Incidents > Status page.
Select Publish a status page.
In Address, enter the part of the address that names the page, such as contoso-status, or select Generate. It must be 8 to 64 lowercase letters, digits, and hyphens, starting with a letter or digit.
Optional: enter a Page title. Leave it blank to use your organization name.
Select Save settings.

Address customers use shows the path of the page, /status/<address>, on your Outpost address. Give that link to your users.

Manage subscribers

People subscribe on the status page itself, under Get updates. They can choose components to hear about, or leave them all clear to hear about everything.

By email. Outpost sends a confirmation link. Nothing else is sent until they confirm.
By Slack. They paste a Slack incoming webhook URL. It is confirmed straight away. If Slack later reports the webhook deleted, the subscription is removed.

Confirmed subscribers are sent a message when a public incident is declared, when a published update is posted, when it is resolved, and when a maintenance window is scheduled, starts, completes, or is canceled. Every email has a link to change preferences or unsubscribe.

To see or remove subscribers, select Incidents > Subscribers. Each shows Waiting to confirm, Confirmed, or Unsubscribed. To stop sending to someone, select Remove and confirm. They are not told, and can subscribe again from the page. You cannot add subscribers from the console.

Schedule maintenance

Announce planned work before it happens, so users know the service will be affected.

Select Incidents > Maintenance, then Schedule maintenance.
Enter a Title and What customers should expect.
Enter Starts and Ends in your local time. The page shows them to each reader in their own time zone.
Under Components affected, select the components the work touches.
To have the window start and finish on schedule, select Start and finish this window automatically. Leave it clear to start and finish it by hand.
Select Save window.

A window is Scheduled, In progress, Completed, or Canceled. To move one by hand, select Start now, Mark complete, or Cancel window in the list. While a window is in progress, its components show Under maintenance.

Estate status (MSP)

On the MSP plan, Estate status is for incidents and maintenance that affect every client at once, such as an outage of your own remote access service.

Declare estate incident opens an incident for your whole practice. Select This affects every client to merge it onto every client’s status page, marked Provider wide, and to send its updates to each client’s subscribers.
Estate components lists the parts every client depends on. Enter a name in Add a component and select Add, or select Delete on a row.
Estate maintenance lists maintenance windows that affect every client. Move one by hand with Start now, Mark complete, or Cancel window.
Your status page publishes a page under your own name at /status on your Outpost address. Select Publish your status page, enter a Page title, and select Save settings.
Client status pages lists each client’s page, whether it is published, and its address, so you can turn a client’s page on or off from one place.

Each client’s own page is set up inside that client, as described above.

Verify

Open the address from Address customers use in a private browser window. The page loads without asking you to sign in and lists your components.

If something goes wrong

Symptom	Cause	Fix
The address shows nothing	Publish a status page is off, the address was changed, or your plan does not include the service desk.	Turn the page on and check the address under Incidents > Status page. See Plans and limits.
An incident is missing from the page	It was not declared as public.	Declare public incidents with Show this incident on the public status page.
Email subscribers never confirm	The confirmation email was not delivered.	Test your outgoing email provider. See Configure outgoing email.

Next steps

Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either license.