Uptime.com Status Pages follow one of three themes: Legacy, Inspire, and Inspire 2.0. Theme determines the visual styling of the page as well as the available customization options. Status Pages that currently use the Inspire theme will be automatically upgraded to Inspire 2.0 in an upcoming release. There will be no changes to URLs or CNAME for existing pages when they are upgraded, so you will continue to access them using the same methods.
Inspire 2.0 is a rebuilt status page experience with a new design, new appearance and visibility controls, and revised defaults for how incidents drive the overall status that is displayed on the page.
This document outlines important differences between versions.
Table of Contents
- How Do I Determine and Configure Which Version I’m Using?
- Will Inspire 2.0 Pages Look Different to My Visitors?
-
What Status Page Behaviors Have Changed in Inspire?
Component Groups Now Display Status According to the Worst Component
Resolving an Incident Now Sets Affected Components Back to Operational By Default
Component Status Updates Default to “No Change” Instead of Forcing a Status
Global Downtime Calculations Checkbox Does Not Appear for Check-Based Status Pages
How Do I Determine and Configure Which Version I’m Using?
Select your Status Page theme on the Design tab when managing the page. On this tab, use the Theme picker to choose the theme for the page:
Note: this selection is only available for Status Pages currently on the Legacy theme. Once a page is switched to Inspire, it is not possible to return to Legacy, and this option will not appear. Status Pages that currently use the Legacy theme can remain on this theme if you choose, and there will be no automatic migration from Legacy to Inspire. Your Legacy page will continue to function as it always has.
The Status Page version and theme can also be quickly determined by its unique visual styling. Following are examples of each theme:
Legacy:
Inspire 1.0:
Inspire 2.0:
Will Inspire 2.0 Pages Look Different to My Visitors?
Although the visual styling has been improved, the actual content of Status Pages will not change. All of your components and incidents will remain. However, viewers will have some additional visualization options, including dark mode and a new item-count badge for section headings.
Custom CSS may appear differently, especially if switching from Legacy to Inspire 2.0. We recommend using the preview link available when managing your Status Page to see if any changes will affect customization prior to switching:
What Status Page Behaviors Have Changed in Inspire?
In addition to the visual styling improvements in Inspire, several default behaviors have also been improved to more closely align with customer feedback and actual use cases. Following is a short outline of changes that can be expected when using the Inspire theme; we recommend reviewing these to determine if they will affect any expected behavior or workflows.
Overall Status Banner Now Follows Component Status
The Overall Status Banner (displaying All Systems Operational or Some systems are experiencing issues) will now only change when the components associated with the Status Page also change their status, or if an incident is created which is associated with a specific component whose status also changes.
Example scenarios:
- A check goes down which is associated with a component on a Status Page. The component is set to change its state to Major Outage when the check goes down. The Overall Status Banner changes to Some systems are experiencing issues since a component has changed its status. When the check and the component recover, the Overall Status Banner reverts to All Systems Operational.
- An incident is created which is associated with a component. In creating or updating the incident, the status of a component is changed to Major Outage. The Overall Status Banner changes to Some systems are experiencing issues. The banner reverts to All Systems Operational when the incident is resolved.
- An incident is created which is not associated with a component. The Overall Status Banner does not change.
- An incident is created which is associated with a component, but the status of the component does not change as a result. The Overall Status Banner does not change.
Component Groups Now Display Status According to the Worst Component
If a component group has a sub component that is in a state of degraded performance or a major outage, the overall component group will display that status rather than simply saying “Operational.”
Grouped Components No Longer Show a Response Time Graph
Previously, component groups displayed a response time graph for the overall group as well as individual components. The graph for the overall group has been removed to reduce confusion about how the data was generated. Response time graphs for individual components are still displayed; view them by drilling down into the group.
Resolving an Incident Now Sets Affected Components Back to Operational By Default
When creating the “Resolved” update for an incident, the option to reset all affected components to “Operational” is now checked by default:
Component Status Updates Default to “No Change” Instead of Forcing a Status
When creating or editing an incident and selecting the affected components, the Update field defaults to “No Change,” and does not enforce a status change if it is unnecessary:
Notification Incidents Do Not Affect Components
Notification incidents let you post general updates to viewers without implying downtime or an outage. Because of that, they're not associated with components, and you won't be prompted to select one when creating a Notification incident.
Global Downtime Calculations Checkbox Does Not Appear for Check-Based Status Pages
Status pages have two methods of calculating downtime: check-based or incident-based. When a status page is set to incident-based calculation and an incident is created, a checkbox will appear to confirm that the incident should contribute to global downtime calculations. When a status page is set to check-based calculation, this checkbox will not appear to reduce confusion.
Comments
0 comments