Status Pages

A status page shows your users whether your services are up, how they've done over the last 90 days, what you're doing about current issues and what maintenance is coming up.

Status pages are listed under Status Pages in the dashboard. Each card shows the page's current overall status — the same one visitors see (Operational, Degraded, Partial outage, Major outage or Maintenance) — and its public address: the custom domain once it is verified, otherwise <subdomain>.zharp.io. Click the address to open the page. Your plan sets how many a workspace can have.

Create a status page

1. 1
   Start a new page

   On Status Pages, click Create status page.

2. 2
   Name it and pick its subdomain

   On the Settings tab, enter a Page name. The Subdomain fills in from the name; change it if you like. It can contain lowercase letters, numbers and hyphens, must not be taken by another Zharp status page, and a few names we use ourselves (such as www, app, api and docs) are reserved.

3. 3
   Choose who can see it

   Under Visibility, pick Public, Password protected or Private. See Visibility.

4. 4
   Save

   Click Save changes. A page can be saved before it has any monitors; the Status updates, Maintenance and Subscribers tabs work once it is saved.

Choose what it shows

Go to the Structure tab. Under Displayed components, add sections with Add section and use Search to add resources to put monitors in them. Drag sections and resources into the order you want, then click Save changes.

• Section name. Shown as a heading on the page. Leave it blank to show the section without a heading.
• Resource name. The name visitors and subscribers see for the monitor. Your monitor's own name, URL and settings are never shown.
• With / without status history. Whether the resource shows its 90 daily uptime bars or just its current status.

Adding a monitor to a page from the monitor's own menu puts it at the end of the last section.

Where the page lives

On the subdomain and on a custom domain, the history is at /history. On those addresses only the status page is served: the Zharp dashboard isn't reachable there.

Custom domain

1. 1
   Enter the domain

   On the Settings tab, under Custom Domain, enter a hostname you own, for example status.example.com, and save. A domain can belong to one status page only, and can't be a zharp.io address.

2. 2
   Add the DNS record

   At your DNS provider, add a CNAME record for that hostname pointing to statuspage.zharp.io, as shown in the dashboard:

   Type	Name	Target
   CNAME	status.example.com	statuspage.zharp.io

   Some providers want only the part before your domain in Name (status). A root domain such as example.com can't have a CNAME at most providers: the dashboard then also lists A (and AAAA) records with Zharp's addresses. Add those instead, or an ALIAS / flattened CNAME to statuspage.zharp.io if your provider offers one. Remove any other A or AAAA records on that name, or some visitors would land elsewhere.

3. 3
   Wait for it to be verified

   Zharp looks the record up as soon as you save, then every few minutes. The Custom Domain section shows where it stands, with when it was last checked; choose Check now to look again right away. Once it is Verified, the page is served on your domain over HTTPS (the certificate is issued on the first visit, which can take a few seconds). To stop using the domain, clear the field and save.

Visibility

Visibility applies to everything the page offers: the page itself, its history and subscribing. It applies on every address the page is served from.

To change the password, type a new one in New password and save; leave the field empty to keep the current one. Changing it signs out everyone who entered the old password.

Opening a private page on its own domain

Your Zharp sign-in belongs to zharp.io, so a private page on its custom domain or on <subdomain>.zharp.io first shows This status page is private. Choose Sign in:

1. 1
   Sign in on Zharp

   You're taken to Zharp. If you aren't signed in yet, sign in as usual (two-factor and Google or GitHub sign-in work too).

2. 2
   Zharp checks your membership

   If you're a member (or the owner) of the workspace that runs the page, you're sent straight back to the page you were on. If you aren't, you see You don't have access to this status page, with the option to use another account.

3. 3
   You're in

   That browser stays signed in to the page on that address for 12 hours; after that, choose Sign in again. The custom domain and the zharp.io subdomain each ask once.

Removing someone from the workspace locks them out of its private pages immediately, on every address, even within those 12 hours. The handover link Zharp sends you back with works once, for one minute, and only for that page.

Look & feel

• Status page design. Modern (rounded cards), Classic (a coloured status banner and bordered lists) or Minimal (no cards, just dividers).
• Color theme. Dark, Light, or Auto, which follows each visitor's system setting.
• Header layout. Vertical puts the overall status in a large block under your logo; Horizontal shows it in a single bar.
• Logos. Upload a logo for a light background and one for a dark background (PNG, JPG, GIF or WebP, up to 2 MB). The page uses the one that suits its theme, or the other if only one is set. Without a logo, the page name is shown.
• What URL should your logo point to? Clicking the logo opens this address, typically your homepage.
• Get in touch URL. Adds a Get in touch button. Use a web address or a mailto: address.

Links have to start with https:// or http:// (or mailto: for Get in touch).

What visitors see

• The overall status: All systems operational, Some systems are degraded (an open status report or ongoing incident, or a resource marked as affected), Partial outage or Major outage (some or all resources down), or Under maintenance.
• Current issues. Open status reports with their updates, and ongoing incidents on the page's monitors.
• Scheduled maintenance. Maintenance in progress or starting in the next 60 days.
• Your sections. Each resource with its current status (Operational, Degraded, Outage, Maintenance) and, if you turned it on, a bar for each of the last 90 days: green for 100% uptime, amber for some downtime, red for down all day, grey for no data. Hover a bar for the date and uptime.
• Overall uptime across the page's monitors for the last 24 hours, 7 days, 30 days and 90 days.
• Status updates — last 30 days. Status reports, incidents and maintenance on the page's monitors from the last 30 days. View history lists the last 90 days.

The page refreshes itself every 60 seconds; the header shows when it was last updated and counts down to the next refresh.

Status reports

A status report is how you tell visitors what's going on. Open the page's Status updates tab and click Create status report.

• Give it a Title, a Status (Investigating, Identified, Monitoring or Resolved) and a Message.
• Tick the Affected services: they show as Degraded on the page until the report is resolved (a service that is actually down still shows Outage).
• It is published straight away and e-mailed to the page's confirmed subscribers.

From a report's ⋮ menu:

• Post update adds a message with a new status to the report's timeline. Subscribers are e-mailed.
• Resolve posts a Resolved update, which closes the report. Reopen with an update opens it again.
• Edit changes the title, the first message or the affected services. Subscribers aren't e-mailed about edits.
• Delete removes the report from the page.

Maintenance

The page's Maintenance tab lists maintenance windows for its services, from the last 30 days on. Click Schedule maintenance to add one: give it a name, a description visitors will see, a start and an end, and pick the services (all of the page's services are ticked to begin with).

The window is a regular maintenance window — it also appears under Maintenance, where you can edit, repeat or delete it. It shows on every status page that includes one of its services: as scheduled beforehand, then in progress, and afterwards in the status updates. While it runs, the services show as Maintenance and their alerts are paused.

The page's confirmed subscribers are e-mailed twice: when the window is scheduled (if it starts later — one that is already under way only gets the second e-mail), and when it starts. Each e-mail gives the window's name, the time in the window's timezone, the affected services under their names from your Structure tab, and its description, with a link to the page and an Unsubscribe link. A recurring window e-mails each time an occurrence starts. Someone subscribed to several affected pages gets one e-mail.

Subscribers

How visitors subscribe

1. 1
   Subscribe

   A visitor clicks Subscribe on the page and enters an e-mail address.

2. 2
   Confirm

   We e-mail a confirmation link. Nothing else is sent to the address until the link is used, so nobody can be signed up by someone else.

3. 3
   Receive updates

   Confirmed subscribers are e-mailed when a service on the page goes down and when it recovers, when a status report is published or updated, and when maintenance is scheduled and when it starts. The e-mails use the names from your Structure tab and link to the status page — never to your dashboard.

Every e-mail has an Unsubscribe link. Unsubscribing removes the address straight away.

Subscribers get e-mail only. Slack, Discord and webhook subscriptions aren't available on status pages; to send alerts to those, set up an integration for your team instead.

Managing subscribers

The page's Subscribers tab lists everyone who subscribed, with the date and whether they have confirmed (Confirmed) or not yet (Pending). Search with the box at the top, and remove an address from its ⋮ menu.

To invite a list of people, click Upload and choose a CSV or text file. Every e-mail address in the file is picked up, whatever the columns. Each new address is sent the same confirmation e-mail a visitor would get; addresses that are already confirmed aren't e-mailed again. Up to 1,000 addresses per upload.