New: Connect AI assistants via MCP
Incident Response

Incident Management From Detection to Resolution

Track every incident from the moment it's detected through acknowledgment, diagnosis, and resolution. Keep your team and clients informed at every step.

clientsite.com

https://clientsite.com

resolved

Root Cause

HTTP 503 — Service Unavailable

Started

Mar 10, 2026, 10:42:18 GMT-5

Ended

Mar 10, 2026, 10:58:34 GMT-5

Duration

16m 16s

Activity Log

Incident created — monitor is offline

10:42:18
ASH503

Notification sent to 3 recipients via Email, Slack

10:42:20

Status changed to investigating

10:44:05

Confirmed offline from ASH, PDX, NBG regions

10:45:12
Multi-region

Incident resolved — monitor recovered

10:58:34
200342ms

Why Incident Management?

Why Incident Management?

When a client site goes down, the clock starts ticking. Sentinel automatically creates detailed incident records so your team can respond fast, track progress, and share updates with clients.

  • Automatic incident creation on any type of failure
  • Full timeline with acknowledgment and resolution tracking
  • Diagnostics including traceroute and HTTP headers
6
Incident Types
90d
History Retained
<1s
Detection Speed
∞
Incidents Tracked

Features

Everything you need to manage incidents

Automatic Detection

Incidents are created automatically for uptime failures, SSL expirations, DNS changes, keyword failures, JSON assertion failures, ping outages, port unreachability, and slow responses.

Incident Timeline

Track every event from detection through resolution. See who acknowledged, what diagnostics were run, and when it was fixed.

Team Acknowledgment

Team members can acknowledge incidents to signal they're working on it. No more duplicate efforts during outages.

Built-in Diagnostics

Run traceroutes and inspect HTTP headers directly from the incident view. Diagnose root causes without leaving Sentinel.

Incident Notes

Add notes to incidents for internal documentation. Record root causes, workarounds, and follow-up actions.

Regional Awareness

See which regions are affected. Distinguish between localized network issues and full global outages.

FAQ

Incident management questions

How does Sentinel create incidents?

Incidents are created automatically the moment a problem is detected. This covers uptime failures, SSL certificate issues, DNS changes, domain expiration, keyword failures, JSON or API response problems, ICMP ping outages, TCP port unreachability, and missed heartbeats or cron runs.

What is included in an incident timeline?

Each incident has an automatic timeline that tracks every event from detection through to resolution, along with the root cause and resolution notes. You get a complete record of what happened and when.

Who gets notified when an incident opens?

When an incident is created, Sentinel sends alerts through your configured channels, which can include email, SMS, Slack, Discord, and webhooks. Your team is informed the moment something breaks.

Does an incident tell me which regions were affected?

Yes. Because checks run from four global regions, an incident shows which regions detected the failure, so you can tell a localized network issue apart from a full global outage.

Can I add my own notes to an incident?

Yes. You can record root cause findings, workarounds, and resolution notes directly on the incident, building documentation you can reference later or share with clients.

How quickly are incidents detected?

Uptime checks can run as often as every 30 seconds, so incidents are opened soon after a problem starts. Multi-region consensus ensures the incident reflects a real failure rather than a transient blip.
Respond faster, resolve sooner

Turn every incident into a learning opportunity

Track incidents from detection to resolution with full diagnostics. 14-day free trial, cancel anytime.

Start Free Trial → View Pricing
14-day free trial
No credit card required
Cancel anytime