Do incidents close on their own?

Yes. A workflow can close the incident as soon as conditions return to normal, so the timeline and the duration stay accurate.

Anyone you route to: email, Telegram and Discord on every plan, Slack, Microsoft Teams and Pushover from Pro, PagerDuty and webhooks on Business.

Do incidents show up on my status page?

Yes, if you want them to. Incidents can appear on your public status page and are tracked there through resolution.

Can I handle incidents from my AI assistant?

Yes. Claude, ChatGPT and any MCP-capable client can connect to the Fivenines MCP server to read incidents, acknowledge, comment and resolve them. It is included on every plan.

Incidents

Handle every incident, from detection to resolution

Incidents open on their own, with a timeline your whole team can follow.

Get a demo Start free trial

app.fivenines.io/acme/incidents/482 SM

Fivenines OverviewInstancesUptimeNetworkCron jobsWorkflowsIncidentsStatus pages

api.acme.io is downOpenAcknowledgedResolvedIncident #482 · Uptime monitor · opened at 14:03 CommentResolve

Timeline

14:03Opened by the workflow Uptime downConfirmed from 4 of 4 regions

14:03Notified #ops on SlackSarah M. is on call

14:05Acknowledged by Sarah M.Time to acknowledge: 2 min

14:12Comment from Claude via MCPRoot cause: the reindex job on api-02 has been stuck since 14:02.

14:13Status page updatedShown as Identified on status.acme.io

14:21Resolved automaticallyapi.acme.io is back up. Duration 18 min.

Details

DurationOngoing18 min

Affectedapi.acme.io

Regions4 of 4 failing

Status pagePublic

MTTA, 30 days3 min

MTTR, 30 days21 min

Escalate until someone answers.

Build the path an incident takes with the visual workflow builder, or start from a ready-made template.

Recheck before anyone is paged
Route by time of day, severity or team
Escalate when nobody acknowledges
Pause alerts during maintenance windows

Explore workflows

TriggerUptime downapi.acme.io fails a check

LogicRecheck triggerConfirm from the other regions

ActionCreate incidentOpens #482 with a full timeline

NotifySlack #opsAlert the on-call engineer

GateAcknowledged within 10 min?Otherwise, escalate

NotifyEmail the whole teamIf nobody acknowledged

Less noise, faster fixes.

Everything your team needs to go from the first alert to the fix.

Opened for you

Workflows open an incident once an outage is confirmed, and close it when things are back to normal.

One timeline

Every alert, acknowledgement, comment and status change, in the order it happened.

Acknowledge and escalate

If nobody acknowledges in time, the next person or the whole team gets the alert.

No alert storms

Rechecks filter blips, and a host that is down does not page you for every service on it.

MTTA and MTTR

Track how fast your team acknowledges and resolves incidents across the organization.

Investigate with your AI assistant

Claude, ChatGPT or any MCP client gets the timeline, the affected host and its CPU and memory in one call.

Frequently asked questions

Workflows open them. A trigger fires, for example a failed uptime check, a metric threshold or a missed cron job, the workflow rechecks it, then creates the incident with a full timeline.

Something else on your mind? Talk to us →