Notice & Component Statuses
Every notice and component has a status. We have included the statuses for each notice type and the corresponding component status below, along with our recommendation on when to use them.
Current Incident
| Notice Status | Component Status | How to use |
|---|---|---|
| Investigating | Degraded | An incident has just started, and the team is looking into what the problem is and where the root cause may be. At this time, you may not know the full impact. |
| Identified | Degraded | You have been able to confirm what the customer impact is and what is causing the issue. At this stage, you are working on a fix/patch. Providing a short outline of the steps to restore service is good. Hint: You can use this state for updates, but be sure to set expectations on when customers can expect the next update. |
| Recovering | Operational | A fix has been created and deployed. You are now monitoring the results. Hint: It's good to say how long you'll monitor for (e.g., 24 hours). |
| Resolved | Operational | Service has been fully restored after monitoring for some time. |
| False Alarm | Operational | Your team has identified no customer impact on the original incident. |
Planned Maintenance
| Notice Status | Component Status | How to use |
|---|---|---|
| Scheduled | Operational | Maintenance has been planned along with the start and end date and time. Please ensure you provide expectations on what this maintenance is about and whether there is any impact. |
| Cancelled | Operational | Plans have changed and the scheduled maintenance is no longer taking place. Use this status to formally notify subscribers that the maintenance has been cancelled. Cancelled maintenance will move to your status page history and display with strikethrough styling. |
| Underway | Under Maintenance | Maintenance is now in progress. You can use this state as a way to provide updates if you need to during the maintenance. |
| Complete | Operational | Maintenance has been successful and has now ended. |
Historic Incident
Historic incidents are used to document past issues that have already been resolved. Unlike current incidents, historic incidents skip directly to the Resolved status, allowing you to maintain a complete incident history and transparency with your subscribers.
| Notice Status | Component Status | How to use |
|---|---|---|
| Resolved | Operational | Historic incidents always use the Resolved status since they document issues that have already been fully resolved. Use this notice type when you need to add past incidents to your status page history for transparency, or when an incident was resolved before you had a chance to notify subscribers in real-time. |