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, and affected-service linking. Incidents can auto-create from any monitor failure and auto-resolve when it recovers.
Free tier included
No credit card
2-minute setup
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 posts the next update, all in the same place.
Severity levels that mean something
Incidents are minor, major, or critical. That label is what visitors see on the status page. P1 through P4 labels are not used.
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, with 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.
A timeline on every incident
Post timestamped updates through Investigating, Identified, Monitoring, and Resolved. Structured postmortem documents are not built yet.
From monitor to incident, automatically
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
SEVERITYCritical
UPDATES POSTED3
TIME TO IDENTIFY11m
checkout-api98ms
payments-api88ms
web-app42ms
auth12ms
status-page8ms
Built for the whole lifecycle
Close the loop with
Close the loop with
a timeline.
After resolution, the incident timeline stays on the record: what you posted, when you posted it, and who you told. Structured postmortem documents are not built yet.
- Timestamped updates through Investigating to Resolved
- Severity is minor, major, or critical
- Email subscribers get the same updates they confirmed for
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
fastest check interval, which is what bounds time to incident
3
severity levels: minor, major, and critical
100%
of published incidents visible on the status page timeline
$0
free tier, full incident workflow included
FAQ
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 use minor, major, or critical. Severity drives how you label the event on the status page. P1 through P4 labels are not used.
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.
There is no postmortem document type today. Keep the story on the incident timeline.
Related features
Start free. No credit card.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.