Creating and Managing Incidents
When something goes wrong with your service, an incident helps you communicate with your users transparently. Here’s how to create and manage incidents effectively.

When to Create an Incident
Create an incident when:
- Your service is down or unavailable
- Performance is significantly degraded
- A feature isn’t working correctly
- You’re aware of an issue affecting users
Even if only some users are affected, it’s usually better to communicate proactively.
Creating a New Incident
- Go to Incidents in the left menu
- Click New Incident
- Fill in the incident details
- Click Create
Incident Fields
| Field | Description |
|---|---|
| Title | Short, clear description (e.g., “Website Loading Slowly”) |
| Status | Current state of the incident |
| Message | Details about what’s happening |
| Affected Components | Which services are impacted |
Incident Statuses
Each incident moves through different states:
| Status | Meaning |
|---|---|
| Investigating | You’re aware of the issue and looking into it |
| Identified | You’ve found the cause |
| Monitoring | A fix is in place, watching for stability |
| Resolved | Issue is fixed and service is normal |
Keep your status accurate - users rely on this information.
Adding Incident Updates
As you work on the issue, add updates:
- Open the incident
- Scroll to the Add Update section
- Write what’s happening
- Change the status if appropriate
- Click Post Update
Updates appear in chronological order on your status page.
Good Update Examples
- “We’ve identified the issue as a database connection problem.”
- “A fix has been deployed. Monitoring for stability.”
- “Service is fully restored. We’ll continue monitoring.”
Choosing Affected Components
Select the components that are impacted by this incident:
- This updates their status on your status page
- Users can see exactly what’s affected
- Components automatically return to normal when resolved
Link components to your incident for accurate status page display.
Writing Good Incident Messages
| Do | Don’t |
|---|---|
| Be honest about the issue | Blame users or other companies |
| Use simple, clear language | Use technical jargon |
| Provide estimated resolution time (if known) | Make promises you can’t keep |
| Update regularly | Go silent for long periods |
Example Incident Message
“We’re experiencing issues with our API that may affect integrations. Our team is investigating and we expect to have more information within 30 minutes. We apologize for any inconvenience.”
Resolving an Incident
When the issue is fixed:
- Open the incident
- Add a final update explaining the resolution
- Change status to Resolved
- Click Update
Resolved incidents move to your incident history but remain visible on your status page for the configured number of days.
Viewing Incident History
To see past incidents:
- Go to Incidents in the left menu
- All incidents are listed with their status
- Click any incident to view details and updates