Incidents
Incident management without another tool
When a monitor really fails, StatusTick opens an incident, alerts the right people, drafts the update for your users and records what happened. When it recovers, the incident resolves on its own.
From failure to resolved
Opens on its own
An incident opens when a monitor stays down for the failed checks you set. Its start time is the first failed check.
Resolves on its own
It resolves after the good checks you set, with an optional delay against flapping.
Manual incidents
Declare an incident for problems no monitor can see.
Severity rules
Set a severity per status, organization-wide or per monitor: Critical, High, Medium or Low.
Work on it together
Acknowledge and assign
Show the team who is on it. Acknowledging stops escalation.
Timeline and comments
Status changes, alerts, escalations and notes in one place.
Roles
Owners, admins and members, with invites by email.
Audit log
Changes to monitors, channels and members are recorded.
Tell your users
Status page update, drafted for you
StatusTick drafts the public incident post from the incident; publish it as is or edit it.
Vendor outages in context
When Stripe, AWS or another vendor you follow has an incident at the same time, StatusTick shows it on your incident.
Questions
Do I need a separate incident tool?
For many small teams, no: incidents, acknowledge and escalation are built in. If you need on-call rotations, connect PagerDuty.
Can I open an incident by hand?
Yes, for problems that no monitor can see.
Try StatusTick before launch.
Launching Q1 2027. The closed beta is free.