Creating Incidents
Report service disruptions to keep users informed
When a service disruption occurs, creating an incident quickly and accurately keeps your users informed and reduces support inquiries.
Impact Levels
Major Outage
Complete service unavailable
Partial Outage
Some features unavailable
Degraded
Performance issues
Minor
Minimal user impact
Creating an Incident
1
Open Incidents
Navigate to Admin → Incidents
2
Create Incident
Click the "Create Incident" button
3
Fill Details
Enter title, status, and impact level
4
Select Components
Choose affected services
5
Publish
Click Create to publish the incident
Incident Fields
| Field | Required | Description |
|---|---|---|
| Title | ✓ Yes | Brief description of the issue |
| Status | ✓ Yes | Current state (Investigating, Identified, etc.) |
| Impact | ✓ Yes | Severity level (Major, Partial, Degraded, Minor) |
| Status Page | ✓ Yes | Which status page to display on |
| Components | No | Affected services/components |
| Message | No | Initial update message for users |
Quick Create
Use keyboard shortcuts for faster incident creation during critical situations:
Ctrl/Cmd + Shift + I → Open incident creation modal
Tab → Move between fields
Enter → Save and publish incidentBest Practices
- Be clear and concise - Avoid technical jargon
- Update frequently - Keep users informed of progress
- Set correct impact - Don't over or understate severity
- Link affected components - Shows scope of the issue
- Provide ETA when possible - Helps users plan
Auto-notifications: When you create an incident, subscribers are automatically notified via email and any configured webhooks (Discord, Slack, etc.).