Reading a status page
Written for the people who read a status page: your customers, your support team, an auditor checking a claim. To set one up, see Status pages.
Every screenshot here is our own status page. It is public, so you can compare what you read here against the live page at any time.
The banner
Section titled “The banner”The top line sums up the whole page in one sentence: All systems operational, or the most severe state among the components below it. It is derived from the components and never typed by hand, so nobody sets a status page to green.
A component
Section titled “A component”Each component is one monitored service. It carries three things:
The state dot and label: operational, degraded, or down. This is the quorum-confirmed state, so a failure seen by one region alone leaves the dot unchanged. Quorum and regions explains the rule.
The availability bar: one segment per day, up to 90 days here. Green is a day without confirmed downtime, and the percentage to the right is the availability over that window. The bar is built to be trusted:
- It rounds down. The figure is a lower bound you can rely on.
- It shows gaps as gaps. A day without checks appears as a gap, never as a green segment.
- It labels the span it draws. A page published two weeks ago reads “14 days ago”, because the label always names the span actually shown.
The response time chart: the latency over the same window. It answers the question a bar chart leaves open: was it slow before it broke?
Where it was measured from
Section titled “Where it was measured from”Checked from Africa · Asia · Europe · North America · Oceania · South America
Six regions, one per inhabited continent. This line tells you how much the figure covers: availability measured from one place describes one network path. Measuring from six continents shows whether a service answers in São Paulo as well as in Frankfurt.
The number of regions depends on the operator’s plan, listed under Plans and limits.
Subscribing
Section titled “Subscribing”The subscribe box sends an email when an incident is opened and when it is resolved. It is double opt-in: you get a confirmation mail first, and updates start once you follow that link. Every message afterwards carries a one-click unsubscribe.
The page also offers an RSS feed with the same events, for readers who prefer not to share an address.
On a phone
Section titled “On a phone”The page reflows to a single column, and the availability strip keeps every day it has. A narrow screen shows thinner bars and the full history.
What the page reports
Section titled “What the page reports”- Confirmed state. The page shows confirmed state at check-interval resolution.
- Confirmed outages. Failures below the alarm quorum stay off the page, so readers see what actually affected the service.
- Maintenance as maintenance. Planned work is labeled as such, kept apart from downtime, and shown as a banner while it runs.
The line at the bottom
Section titled “The line at the bottom”Powered by Perstat links to perstat.io on pages without white-label. From Command, the
operator can replace that mark with its own light- and dark-mode branding, as described under
Status pages.
- Status pages: set up a page like this on your own domain.