Your client gets a status page they can bookmark, in their branding, and they see what's happening to their sites without emailing you to ask.
What clients ask when something breaks
When a site has a problem, the first message you get is usually a question. Is it down? Since when? Is anyone working on it? Each answer costs you a reply, and a client who hears nothing assumes nothing is happening. A status page answers the question before it's asked, and the update timeline shows the work.
What the page shows
- The websites and heartbeats you choose, side by side, with 90 days of history for each and an overall status at the top.
- Incidents you post, moving through four stages (investigating, identified, monitoring and resolved), with a public timeline of updates. While an incident is open you can override the status of the components it affects.
- Scheduled maintenance: windows that are running or start within the next 7 days, for the sites on that page, in the window's own time zone.
You can add your logo, a header image and a favicon, and set the colours, fonts, corner radius and badge style, or write your own CSS. A page can show or hide uptime percentages and response times. You can create as many pages as you need, one per client, and uptime badges for a site are available as images you can embed.
Your own domain
On a paid plan you can serve a page at your client's hostname, such as status.client.com, with the certificate included. You enter the hostname and OctoPing shows the DNS record to add. It gives each domain its own CNAME target, so only the person who controls the DNS can claim it. Once the record is in place OctoPing verifies it, issues the certificate and serves the page over HTTPS. A trial account can't set a custom domain.
That hostname serves the status page, its incident history, the subscribe and unsubscribe pages, the contact unsubscribe pages and the feeds, and nothing else. After setup OctoPing keeps watching: it emails the workspace Owner and Admins if the DNS record stops pointing at the page or the certificate looks like it won't renew.
Subscribers and feeds
Visitors can follow a published page by email. They enter an address, confirm it from a link in the message they receive, and can leave with one click from any email. They get an email when you post an incident or an update with Notify subscribers ticked (it's ticked by default for open incidents), up to 10 notified updates per incident. The emails come under your page's title, with a reply-to address you can set. A subscriber follows the whole page and not a single component.
Atom and RSS feeds carry the page's 50 newest incidents for anyone who prefers a reader. The feed address uses the page's own host, so a page on your client's domain doesn't point readers at ours. Maintenance windows appear on the page and are not sent to subscribers or in the feeds.
Client contacts
Subscribers choose to follow a page. Contacts are people you add. A Member or above adds a client's email address in the page's Contacts section and confirms the client agreed to receive it. The client gets a welcome message, then:
- Each kind of alert for the page's sites and heartbeats. Down and recovery, slow responses, certificate and domain expiry, DNS, content, robots.txt and hosting changes, and missed heartbeats. A contact gets the first alert of an outage and its recovery, not the reminders, and an expiry warning at most once every three days. Your alert rules decide when an alert is sent, so anything a maintenance window silences for you stays silent for them too.
- A monthly summary of the page's sites. Uptime, downtime and outages, response time, certificate and domain expiry dates and change counts, for the sites shown on that page. Heartbeats aren't in the summary.
Contacts aren't users and don't use a seat, and they have no login. Every email links back to the status page and names your workspace as the one monitoring the sites. A contact can unsubscribe from alerts, from the summary or from both. A contact hears about every site on the page, because you can't pick sites per contact. Mail pauses while the page is unpublished or the workspace is paused.
Subscribers and contacts share one allowance per workspace:
| Plan | Subscribers and contacts |
|---|---|
| Starter | 500 |
| Agency | 5,000 |
| Scale | 25,000 |
How it fits the price
White-labelled status pages are included on every plan, with the number of pages unlimited. Incidents, subscribers, feeds and client contacts are included too, and custom domains are part of every paid plan. Plans start at $19 a month for 20 sites. See pricing for the full list.
Every account starts with a 14-day free trial. No card required. Start your 14-day trial and add a client's site to see it working.
Last reviewed
Related
- FeatureWebsite uptime monitoring with the cause in every alertCheck client sites as often as every 30 seconds, see why a check failed, and flag slow responses as degraded. Planned work stays out of your uptime numbers.
- FeatureWebsite alerts by email, Slack, Discord, webhook and pushChoose where alerts go, how many failures it takes to send one and how often reminders repeat. Recovery messages and a log of every attempt are included.
- DocsStatus page JSONRead a published status page and its incident history as JSON: the fields, pagination, caching and error responses.
- DocsBadgesEmbed a site's uptime or current status as an SVG image: both endpoints, their parameters, colors and embed snippets.
- GuideShow live status on your own siteShow a client's live status inside your own website, portal or dashboard by reading their status page as JSON.
- GuideSet up a white-label status page for each clientGive each client a status page with their own logo and colors that lists only their sites, and publish it on your address or theirs.
- GuideAdd a client as a status page contactSend a client every alert for their sites and a monthly summary by email, without giving them a login or using a seat.