Public status pages

Publish a status page from the uptime checks: components, 90 days of availability, incidents and maintenance, e-mail subscriptions and feeds.

Updated

A status page tells your visitors, at a public address, whether your service works: the parts you choose, under the names you give them, with their availability over the last 90 days and the incidents you write. It is built on the uptime monitoring of your proved domains.

Status pages are included from the Solo plan: one page on Solo, five on Agency, 25 on Agency Plus. On Free, the Status pages page says what they bring and links to the plans. Owners and admins create and change them; the other members can read their settings.

Create a status page

  1. Open Status pages in the menu.
  2. Give the page a title. Leave the address empty for one nobody can guess (twelve random letters and digits), or choose one: app.perimetry.cloud/status/your-choice.
  3. Press Create a status page. Its settings open.

Choose what it shows

  • Components: tick the monitored domains to show and give each a public name, such as “Website” or “Customer area”. Only proved domains whose uptime checks are on can be shown. The order sets their place on the page.
  • Language of the page: English, French or German. The page, its e-mails and its feeds are in that language, whoever reads it.
  • Colour: one of six, readable in light and dark mode.
  • Show your logo: the workspace’s logo, the same as on the agency reports; upload one from this page if you have none.
  • Show the average response time: over the last 24 hours, per component.
  • Keep search engines away: ticked by default, so the page is not indexed. Untick it to let search engines list it.
  • Allow e-mail subscriptions: ticked by default. Untick it to hide the subscription form; nothing is then sent to the existing subscribers either. The feeds stay.
  • Published: untick it to take the page offline without deleting it.

Titles and component names cannot contain a web address: they are shown and e-mailed to your visitors. An address you give up (page deleted or address changed) stays reserved for your workspace for 90 days, so nobody else can take it in the meantime.

The page never shows the address that is monitored, an IP address or an error message: only the public names, their state, their daily availability and what you write.

What visitors see

At the top, an overall banner: all systems operational, degraded performance, partial or major outage, or maintenance in progress. Then each component with its state and 90 bars, one per day, coloured by its availability that day (hover a bar for the figure), its availability over 90 days and, if shown, its average response time.

Outages detected by the uptime checks appear on their own, under Past incidents, with when they started and how long they lasted, never their technical cause. The page is refreshed at most every 30 seconds.

Write incidents and maintenance

Under Incidents and maintenance:

  1. Open New incident (or Plan a maintenance), give it a title, an impact (degraded performance or outage), the components concerned (none ticked: the whole page) and a first message.
  2. Press Publish. The incident shows at the top of the page and subscribers are told by e-mail.
  3. As things move on, open the incident, choose its new status (investigating, identified, monitoring, resolved) and write a message, then press Post an update. Each update is timestamped. A resolved incident goes to the history.

A maintenance has a start and an end (in UTC); it is shown as planned until it starts.

Subscriptions and feeds

Visitors enter their e-mail address at the bottom of the page. They receive a link to confirm, valid 48 hours from their first request, and nothing else until they confirm; an address that is never confirmed is erased within 54 hours. The answer is always the same and never says whether an address is already subscribed; three confirmation e-mails a day at most go to the same address. Subscribers are told of each update you post and of the outages detected, one outage e-mail and one recovery e-mail per component and per hour at most (when a site goes up and down more often, they get its current state at the start of the next hour), and every message has a one-click unsubscribe link that erases their address. Five subscriptions an hour at most come from the same network. The settings page shows how many subscribers you have, never their addresses.

The page also has an Atom feed and an RSS feed (…/feed.atom, …/feed.rss).

Without the Perimetry name

On Solo and Agency, the page ends with “Status page by Perimetry Cloud”, and the e-mails to subscribers say so in one line. On Agency Plus, neither the page nor its e-mails mention Perimetry, and the e-mails are sent in the name of the page (its title as the sender’s name). The sending address stays the service’s own: e-mails cannot be sent from your domain yet. A custom domain (status.example.com) is not available yet.

If your plan changes to one with fewer pages, the oldest pages stay online and the others stop being shown, without being deleted; on Free, none are shown.