Auto-create from monitor alerts
Configure a service to open an incident automatically when a monitor fails — no human needs to click "Declare incident" in the middle of the night.
Incident Management
One timeline from
One timeline from
alert to resolved.
Declare, track, and close incidents without leaving the platform. Severity levels, structured updates, affected-service linking, and postmortems — incidents can auto-create from any monitor failure and auto-resolve when it recovers.
Free tier included
No credit card
2-minute setup
INC-0291 · Checkout API InvestigatingLIVE
SEVERITYP1 Critical
DURATION18m
RESPONDERS3
checkout-api98ms
payments-api88ms
web-app42ms
auth-service12ms
cdn8ms
What you get
A structured response, not a chat thread.
Every incident has a severity, a status, a timeline of updates, and a list of affected services. Your on-call engineer sees it the moment it fires; your users see it on the status page; your team writes the postmortem — all in the same place.
Severity levels that mean something
P1 through P4 severity levels let responders triage at a glance and drive different escalation paths, notification urgency, and SLA tracking.
Timestamped update timeline
Every status transition — Investigating, Identified, Monitoring, Resolved — is stamped and logged. Visitors see the full history; your team has an audit trail.
Status page publishing included
Incidents post to your public status page automatically. Components switch to "Degraded" or "Outage" and return to "Operational" when you resolve — no separate update needed.
Responder acknowledgment tracking
Know who has been paged, who acknowledged, and who is actively working the incident. Responders move through Triggered, Acknowledged, and Resolved states with timestamps.
Postmortems on every incident
Attach a structured postmortem to any resolved incident — root cause, timeline, action items — and build a searchable history of how your team responded.
01 · From monitor to incident in seconds
No manual step
No manual step
to declare it.
When a monitor fails, Site Qwality can open an incident, set the severity, link the affected service, page the on-call responder, and update the status page — all before anyone has typed a single word into Slack. You step in to add context, not to trigger the process.
- Monitor failure triggers incident creation automatically
- Severity, service, and responder set from service config
- Status page component flips to degraded in the same event
INC-0291 · Checkout API IdentifiedLIVE
SEVERITYP1 Critical
UPDATES POSTED3
TIME TO IDENTIFY11m
checkout-api98ms
payments-api88ms
web-app42ms
auth12ms
status-page8ms
02 · Built for the whole lifecycle
Close the loop with
Close the loop with
a postmortem.
After resolution, the incident timeline becomes the backbone of your postmortem. Capture root cause, contributing factors, and action items directly on the incident record. Build a searchable archive so your team learns from every event — not just the big ones.
- Postmortem template attached to every resolved incident
- Action items tracked to completion inside the platform
- Full incident archive, searchable by service and severity
resolve an incident via API$ curl -X POST https://api.siteqwality.com/incident/INC-0291/resolve \
-H "Authorization: Bearer $TOKEN" \
-d '{"resolution":"Rolled back CDN config. All checks passing."}'
# Incident resolved · status page updated · subscribers notified
-H "Authorization: Bearer $TOKEN" \
-d '{"resolution":"Rolled back CDN config. All checks passing."}'
# Incident resolved · status page updated · subscribers notified
<30s
from monitor failure to incident open and on-call paged
P1–P4
severity tiers to triage and route correctly
100%
of incidents linked to a postmortem for follow-up
$0
free tier — full incident workflow included
FAQ
Questions, answered.
Yes. Configure a service with automatic incident creation and Site Qwality opens an incident the moment a linked monitor fails. You can also require manual confirmation, or disable auto-creation and declare incidents manually.
Incidents have P1 (Critical) through P4 (Low) severity levels. Severity drives escalation policy selection, notification urgency, and SLA tracking. You can change severity at any point during the incident lifecycle.
Yes. When you resolve an incident, affected components return to "Operational" and a resolved update is posted to the status page timeline automatically. Subscribers receive a resolution notification.
Every status change — Investigating, Identified, Monitoring, Resolved — is recorded with a timestamp and the optional message you provide. The timeline is visible to your team and, if published, to your status page visitors.
No, but they're strongly encouraged. You can attach a postmortem to any resolved incident, capturing root cause, contributing factors, and action items. The postmortem lives on the incident record permanently.
More of the platform
Explore the rest of the platform
Ready?
Start watching in under a minute.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.