Severity

To help you and your users to understand the severity of an incident, we have defined a set of severity levels. You can select one of the following severity levels when you create a status report.

You don’t have to select a severity level and can always delete it.

The severity level will be displayed in both the status page report and email notifications sent to subscribers. This helps your users quickly understand the impact level of any incident.

Incident Severity Reference Guide

Level	Description	Example Incidents	Response Priority
Critical (S1)	Major outage or failure impacting all users or core operations.	Payment system down, database corruption, full platform outage.	Immediate, all-hands response.
High (S2)	Major degradation affecting many users or key functionality.	Core feature down, severe slowness, major security issue.	High-priority response.
Moderate (S3)	Partial loss or degraded experience for a small group.	Slow API, minor bugs, low-risk security concerns.	Handled during business hours.
Low (S4)	Cosmetic or minor issues with no real user impact.	Typos, misaligned buttons, UI glitches.	Logged for future resolution.
Informational (S5)	No impact — tracking, improvements, or documentation-related.	Enhancement requests, doc updates, future ideas.	Backlogged for future review.