Status · Guides
Share a status page
Each project can have a public status page: the monitors you choose, their states and their last 90 days, for your customers to open without signing in.
Show a monitor
A monitor is on the page only when you say so. Open it, choose Change, and in the Public status page part:
- tick Show on the public page,
- Its name there (optional): what customers read, such as "API". Blank: its own name.
- Its group there (optional): monitors of one group show together, such as "Services" or "Apps".
- Slow after (optional, HTTP checks): in milliseconds. A good answer slower than this shows as Slow, and the page's head says Degraded.
Then choose Save. A deploy's list can say the same with public, public_name, public_group and slow_ms (Sync the monitors).
A project with no public monitor has no page: its address answers 404.
The page's address
Once a monitor is public, every page of the project has a Public status page button, and step 5 of the setup guide lists the page's address with a button to copy it. The page needs no sign-in, and it opens again by itself every minute, so it can stay on a screen.
It answers only at that address, which belongs to the project's workspace.
What the page shows
- Its state as the head, with since when and when it was last checked.
- Each public monitor, in its group: its name there, its state and a bar for each of the last 90 days, with its uptime over them. A full, pale bar is a day with no downtime; a shorter, stronger one had some (the shorter, the longer it was down); a dash is a day it wasn't watched.
- The downtimes of the last 14 days that lasted 3 minutes or more, and any still going on. Shorter ones count in the bars only.
- The maintenance windows you made public, planned and running.
- The incidents a responder showed there, when the project's Incidents is connected.
It never shows an address, why a monitor was down or who was told. Times on it are in UTC. A monitor checking again after one failed check still shows as Up there; a paused one shows as Not checked.
What its head says
| It says | When |
|---|---|
| All up | Every monitor on the page is up. |
| Partly down | Some of them are down. |
| Down | All of them are down. |
| Under maintenance | A maintenance window you made public is running. Downs it covers don't count. |
| Degraded | Nothing is down, but at least one is answering slower than its Slow after. |
| Waiting | Nothing on the page has been checked yet. |
| Not confirmed | Status itself hasn't run its checks for a while, so it doesn't claim anything. It says when it last checked. |
The first that fits wins, in the order of the table but for Not confirmed, which comes before every other.
Incidents on the page
When the project's own Incidents is connected, the page also shows the incidents a responder marked "Show on the status page" there, open or resolved in the last 14 days, with their public updates. Status fetches them every minute. If Incidents doesn't answer, the last ones stay, saying as of when.
Only what was written for customers is shown: never internal notes, or who wrote anything.
Follow it in a feed reader
Add /feed.atom to the page's address for an Atom feed: its outages of 3 minutes or more, its incident updates and its announced maintenance, newest first. Any feed reader follows it, and so does Slack's RSS app. Step 5 of the setup guide has the address to copy.
Add a badge
Add /badge.svg to the page's address for a small image of the page's head: "status: all up", "partly down", "degraded", "under maintenance". Put it in a README or your app's footer. The setup guide gives the Markdown for it, like this:
When the subscription ends