Status pages overview
Create a public status page, add monitors as components, group them into sections, and show live status, 90-day uptime bars, incidents and maintenance.
A status page shows your customers the live state of your services, their uptime over the past 90 days, ongoing and past incidents, and upcoming maintenance. It updates itself from your monitors: when SutramX confirms an outage, the page shows it, and when the monitor recovers, the page goes back to green.
Create a status page#
- Open Status pages in the sidebar and click New status page.
- Enter a Page title, for example "Acme status".
- Click Create.
SutramX generates the page's URL from the title (for example /status/acme-status-3f9a1c2b) and opens the page editor, where you add monitors, set branding and change the URL.
How many status pages you can have depends on your plan: see Plans & limits. When you reach the limit, the list shows "Status page limit reached".
The status pages list#
Status pages lists your pages with their Title, Visibility, number of Monitors, custom Domain (with Verified or Pending verification) and Created date. The actions open the public page, copy its public URL or delete it.
| Visibility | Meaning |
|---|---|
| Public | Published; anyone with the link can see it. |
| Password protected | Published; visitors need the page password. |
| Private (SSO) | Published; visitors sign in to see it. |
| Unpublished | Hidden: visitors, the badge and the custom domain show "not found". |
A page can also be unpublished automatically when your workspace has more pages than your plan allows (for example after a downgrade). The editor then says the page is over your plan's status page limit and offline until you resolve it, with a link to review your plan.
General settings#
Open a page from the list to edit it. The General section has:
| Field | What it does | Default / limits |
|---|---|---|
| Title | Shown at the top of the public page and in the browser tab. | Required, up to 255 characters |
| Description | Shown under the title. | Optional, up to 1,000 characters |
| URL | The page's slug in /status/<slug>. | 3–64 lowercase letters, numbers and single hyphens; must be unique |
| Published | Whether visitors can see the page. | On for new pages |
| Show response times | Shows each component's latest response time publicly. | On |
Click Save changes. You can also use Publish / Unpublish at the top of the editor.
Public URL#
Every page is available at:
https://app.sutramx.com/status/<slug>If you set up a verified custom domain, the page is also served at the root of that domain, for example https://status.example.com/, and the editor shows that address as the public URL. See Branding & custom domains.
Add monitors (components)#
Each monitor you add to a page appears as a component.
- Open the page and go to Components.
- Choose a monitor in Monitor to add and click Add. Repeat for each monitor.
- Use the up and down arrows to set the order, and the X to remove a monitor from the page.
- Click Save changes.
You can also add a monitor from Monitors: open the monitor's menu, choose Status pages… and tick the pages that should show it.
A monitor can be on several pages. Removing a monitor from a page, or deleting the page, never changes the monitor or its history.
Group components into sections#
To group components under headings, give them a section name, for example "API" or "Website", in the Section field under each monitor (up to 100 characters). Consecutive monitors with the same section name appear together under that heading. A monitor you add takes the section of the last monitor in the list, so you can add a run of monitors to the same section quickly.
Paused monitors#
A paused monitor stays on the page and is shown as Paused. Paused components are left out when the page works out its overall status.
What visitors see#
The public page shows:
- An overall status banner, with a count of components that are operational, have issues, are in maintenance or are paused.
- Ongoing incidents and maintenance in progress, right under the banner.
- Components: each monitor with its current state, when it was last checked (and its response time, if you turned that on), and a bar for each of the past 90 days.
- Third-party services, if you added any.
- Scheduled maintenance: upcoming windows that affect the page's monitors.
- Incident history: incidents from the past 90 days.
- A form to subscribe to updates by email (and, on paid plans, Slack or webhook), and a link to the Atom/RSS feed.
- A "Monitored by SutramX" footer, unless you hide it (Pro).
Component states#
| State | When it's shown |
|---|---|
| Operational | The latest check passed. |
| Degraded | The monitor is responding slowly, or enough of its regions are failing but no outage has been confirmed yet. |
| Outage | The monitor has an open incident. |
| Maintenance | A maintenance window covering the monitor is in progress. |
| Paused | The monitor is paused. |
| Awaiting data | The monitor has no checks yet. |
Overall status#
| Banner | When it's shown |
|---|---|
| All systems operational | Every active component is operational. |
| Degraded performance | At least one component is degraded and none is down. |
| Partial outage | Some, but not all, affected components are down. |
| Major outage | Every affected component is down. |
| Under maintenance | Components are in maintenance and nothing is down or degraded. |
| Awaiting first check | No component has data yet. A page with no components shows No components yet, and one where every monitor is paused shows Monitoring paused. |
Uptime bars#
Each component has one bar per day for the past 90 days, coloured by that day's uptime. Days with no checks (for example before the monitor existed) are shown as having no data.
Incidents on the page#
Incidents appear automatically for every monitor on the page:
- Ongoing incidents appear at the top of the page, under the status banner, as "Monitor is unavailable", with when they started and which component they affect.
- Resolved incidents appear under Incident history as "Monitor was unavailable", with start and end times and how long they lasted. The history covers the past 90 days.
To tell visitors what's going on, post updates on the incident: add a note with Public (show on status page) ticked, or publish an AI-drafted update. Updates appear under the incident, oldest first, without the author's name. Internal notes and postmortems are never shown. See Incidents and AI incident assist.
Maintenance on the page#
Maintenance windows you create under Incidents → Maintenance appear automatically on every page that shows an affected monitor:
- Upcoming windows that start within the next 30 days appear under Scheduled maintenance, marked Scheduled.
- Windows in progress are marked In progress, and the affected components show Maintenance.
Each window shows its title, description, times and the components it affects. See Maintenance windows.
Languages#
The public page's built-in text (status labels, headings, dates) is available in English, Hindi, Spanish, French, German, Portuguese and Japanese.
In the Languages section of the editor:
| Field | What it does | Plans |
|---|---|---|
| Page language | The language your title, description and incident updates are written in. The page's built-in text uses it too. | All plans |
| Extra languages visitors can switch to | Adds a language switcher to the page. For each extra language you can enter a translated Title and Description; leave them blank to use the main ones. | Growth and Pro |
Visitors see the language they pick in the switcher (the page adds ?lang=<code> to the URL, for example ?lang=es). Otherwise they get the first language from their browser settings that the page offers, or the page language.
Incident updates can be translated per language from the incident page, by hand or with AI. See AI incident assist.
Share and embed#
The Share & embed section of the editor has copy buttons for:
- Public URL.
- Status badge, as Markdown or HTML. The badge shows the page's overall state, for example "operational" or "partial outage". Its image URL is
https://api.sutramx.com/status/<slug>/badge.svg. - Atom/RSS feed at
https://api.sutramx.com/status/<slug>/feed.xml, with incidents (including their public updates) and maintenance windows.
The section also shows how many email subscribers the page has. See Subscribers & updates.
Badge Markdown looks like this:
[](https://app.sutramx.com/status/acme-status-3f9a1c2b)Delete a status page#
- Open the page and scroll to Delete status page.
- Click Delete status page and type the page's slug to confirm.
Only the workspace owner can delete a status page. This removes the public page, its custom domain and all its subscribers immediately. Your monitors and their history are not affected.
Common questions#
Who can manage status pages? Any workspace member except a viewer can create and edit pages. Only the workspace owner can delete a page, add, verify or remove a custom domain, change who can view a page, or remove subscribers.
Why does a component show Degraded when nothing is down? Either the monitor is responding slowly, or enough of its regions are failing but the failure hasn't been confirmed yet, so no incident is open. If the failure is confirmed, it changes to Outage.
Why does an incident not show up on my page? Incidents only appear for monitors that are on the page. Check Components. Incidents older than 90 days drop off the history.
Can I show third-party providers like my cloud host? Yes, in the Third-party services section of the editor, on plans with third-party status. See Third-party status.
Related
- Branding & custom domains
- Private pages & SSO
- Subscribers & updates
- Incidents
- Maintenance windows
- Features: Public Status Pages
- Guides: Status Page Best Practices and Incident Response Basics
- Free tools: Incident Message Generator
- Use cases: Monitoring for SaaS Platforms
- More from SutramX: Status Page Features
Last updated . Something unclear or missing on this page? Tell us at support@sutramx.com.