A Public Status Page conveys information on scheduled maintenance, downtime events, and general system uptime to your site or service users. Display current status for components and configure Page settings to meet your needs.
- Add components to your Page to represent the various parts of your infrastructure & communicate their uptime and performance to your users
- Associate a component with a check to display response time and automate the displayed status depending on a check’s state
- Display components, uptime percentages, and metrics in a public or private URL
- Manage incidents with real-time updates and manually control component statuses
For this use case let’s look at an enterprise SaaS Company working to better communicate incidents as they unfold. If the company does not react quickly enough, support tickets and negative press become difficult thorns to deal with in addition to incident management.
We will create a customized Public Status Page to communicate outages and uptime, and also to build trust through transparency. Here are our requirements:
- Notification of downtime events including scheduled maintenance
- A Status Page should be accessible from a public URL displayed prominently on the homepage
- This Page should use custom branding that matches the company’s colors and logo.
- External Page visitors should be able to subscribe to receive incident & scheduled maintenance related update push notifications
- Visual metrics are optional, to further increase visibility into the system performance
- Historical uptime & performance metrics as well as past incidents should be accessible for accountability purposes
We will need to manage our Public Status Page, and click the to get started. You can add your company logo, as well as inline HTML or CSS to your Page’s header and footer from the Customize Look & Feel menu.
Tip: You can customize your SPF record to control the Send from email address used for incident and maintenance email notifications. Customize your email template as well for a unified appearance with your page and company correspondence.
One of the requirements is to set our CNAME, which we will point to “cname.uptime.com” and name “status.ourcompany.com”.
When downtime occurs, we can choose when and how to update component status.
For our purposes, it is enough to have some components that we will manually update and others that are associated with checks and will automatically update to a predetermined status when an outage occurs. This way, we can control the status of individual components or groups, with some automation in place.
Let’s see an example of this:
- An outage occurs, and check A goes to DOWN status.
- Component A, which is linked to Check A, is set to automatically change to Degraded Performance when Check A fails. This occurs on our status page without human input.
- We create an incident related to this outage, and during the third update we identify the problem and manually change status to Major Outage. Our manual change affects Component A’s status, changing from Degraded Performance to Major Outage (which is the most severe status in this scenario).
All status pages reference components which can either be associated with your Uptime.com checks or represent other assets; databases, websites, servers, etc (and component status can be adjusted manually). Components associated with checks are always displayed with current status and corresponding metrics for visibility.
Displaying Incident History is optional, but in this scenario the company has elected to enable this tab making their uptime performance metrics and incident history available to their userbase to promote the reliability of their platform
- Updating your site viewers and users on downtime events (to reduce load on Support Teams)
- Providing a historical view of past incidents and global uptime percentages
- Displaying current statuses of components as well as system performance metrics
Learn how to customize and configure your Public Status page here.