Link each component to an uptime monitor. When its checks fail, the page on your own domain shows the outage. Post updates from the dashboard, the API or an AI agent, and customers follow along by RSS or in Slack.
A demo of the Acme status page: all systems operational, then a major outage of Checkout API with an open incident.
A monitor counts as down after two failed checks in a row, or anywhere from one to ten if you change it. It can also open an incident for you, published right away or saved as a draft until someone reads it.
One outage, start to finish
The outage in the page above, as it happened. Maple changes the component's status on its own; people write the words. Every update also goes out by RSS, Atom and Slack.
The checkout-api monitor fails one check. One failure is not enough to change the page.
A second check fails, so the monitor is down. The linked component switches to Major outage without anyone touching it.
The monitor opens an incident and publishes it. You can have it saved as a draft for review instead.
Investigating
Some card payments are failing. We're looking into it and will post again within 30 minutes.
The on-call engineer posts an update from the dashboard.
Identified
A timeout at our payment provider is failing card payments. We're switching to the backup route.
Checks pass again and the component goes back to Operational. The incident stays open while you watch.
Monitoring
Payments are going through on the backup route. We're watching error rates.
You resolve the incident. It stays on the page, and in the 90-day history, for customers to read.
Resolved
Card payments have worked normally for 30 minutes. This incident is resolved.
Your brand
Five themes to start from, each in light or dark, then your own logo, colours, corner radius and font. Below is the same page in each theme, rendered by the code that serves real pages.
Subscriptions and API
Every public page has RSS and Atom feeds, a status badge, and a status.json in the statuspage.io summary format, so tools that already read statuspage.io pages can read yours.
Acme status · RSS
Failed payments at checkout
Identified: A timeout at our payment provider is failing card payments. We're switching to the backup route.
/feed subscribe https://status.acme.com/feed.rss The page's Subscribe button lists the feed links and the Slack command, /feed subscribe, that posts each update to a channel.
GET /api/v1/status.json
{
"status": {
"indicator": "critical",
"description": "Major System Outage",
"delayed": false
},
"components": [
{
"name": "Checkout API",
"status": "major_outage"
},
{
"name": "Auth",
"status": "operational"
},
{
"name": "Web app",
"status": "operational"
}
]
} Overall status, every component, open incidents and planned maintenance in one request. Uptime history is available as JSON too.
status.acme.com/badge.svg
badge.svg shows the current status in a README, docs site or app footer.
What it does
On the plan
In production: Superwall sends Maple more than 80 billion traces, logs and metrics a month, about 18 TB, with nothing sampled out. Read the Superwall story
Link your uptime monitors, pick a theme and point your domain at it. Status pages come with the plan, with no separate meter.