In this section
Resources / Help / Status page
Incidents and scheduled maintenance
Post incidents, add updates through to resolution, and schedule maintenance windows.
Incidents
Open Status Page → Incidents and create an incident when something is wrong. An incident has a name, a status, an impact, the affected components and a message.
| Incident status | Meaning |
|---|---|
| Investigating | You know about the problem and are looking into it. |
| Identified | You found the cause. |
| Monitoring | A fix is in place and you are watching it. |
| Resolved | The incident is over. |
| Impact | Use when |
|---|---|
| None | Informational. |
| Minor | Small effect on a few users. |
| Major | Significant effect. |
| Critical | Severe or complete disruption. |
Add updates as things change. Each update is stored with a message and a status, so customers see the full timeline. Resolve the incident when it is over. It moves to History.
Maintenance
Use Maintenance to tell customers about planned downtime ahead of time. Set a name, the affected components, a start and an end. Statuses for maintenance are Scheduled, In progress and Completed.
- Create the maintenance with its start and end time.
- It appears under upcoming maintenance on the public page.
- Move it to In progress when work starts and to Completed when it is done.
Writing good updates
- Say what customers experience, not what the root cause is in code.
- Give a time for the next update, even if nothing changed.
- Close with a short summary when you resolve.
Email subscribers
People who subscribed on the status page receive an email when you post an update. See Subscribers.
Manual, not automatic
Hubbo does not detect outages. If you forget to post an incident, the page keeps showing the service as operational.