> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/incidents.md).

# Incidents

- [What is an incident?](https://docs.spike.sh/incidents/what-is-an-incident.md): An incident is any issue that needs investigation and resolution, often one that affects your customers or systems.
- [Incident lifecycle](https://docs.spike.sh/incidents/incident-lifecycle.md): The incident lifecycle covers the stages an incident moves through, from the moment it's triggered to when it's resolved.
- [Incident statuses](https://docs.spike.sh/incidents/incident-statuses.md): Every incident on Spike has one of three statuses: triggered, acknowledged, or resolved. The status determines what Spike does next.
- [How to change incident status](https://docs.spike.sh/incidents/how-to-change-incident-status.md): Change an incident's status directly from any alerting channel — SMS, phone, Slack, or email — without opening Spike.
- [Acknowledge timeout](https://docs.spike.sh/incidents/acknowledge-timeout.md): Acknowledge timeout automatically moves an acknowledged incident back to triggered state if it isn't resolved within a set time.
- [Grouping incidents](https://docs.spike.sh/incidents/grouping-incidents.md): Spike automatically groups repeated incidents so you can see how often an issue recurs and when it first appeared.
- [Priority and severity](https://docs.spike.sh/incidents/priority-and-severity.md): Priority indicates how urgently an incident needs to be resolved. Severity indicates the degree of damage to your systems.
- [Mute alerts](https://docs.spike.sh/incidents/mute-alerts.md): Mute alerts on an incident to stop repeat notifications for a set period, without resolving the incident itself.
- [Reassign incidents](https://docs.spike.sh/incidents/reassign-incidents.md): Reassign any incident to a different team member directly from the dashboard, incident page, or service view page.
- [Sharing incidents](https://docs.spike.sh/incidents/sharing-incidents.md): Share any Spike incident as a public link with customers, stakeholders, or your team to communicate an outage.
- [Why does message parsing fail?](https://docs.spike.sh/incidents/why-does-message-parsing-fail.md): Message parsing fails when Spike can't convert an integration's JSON alert payload into a readable incident format.
- [Rate limiting on duplicate incidents](https://docs.spike.sh/incidents/rate-limiting-on-duplicate-incidents.md): Spike rate-limits duplicate incidents to reduce noise when the same incident triggers repeatedly in a short window.
- [Resolve by Timer](https://docs.spike.sh/incidents/resolve-timer.md): Resolve by Timer automatically resolves incidents after a set duration if they haven't been manually resolved.