Back to home
Incident Management

Structured response from first alert to resolution

Vantaj opens, tracks, and resolves incidents automatically as your monitors change state. Every outage gets a timeline, a duration, and a record — so your team responds faster and learns from every event.

Automatic incident creation

The moment a monitor fails, an incident is opened with a timestamp, affected service, and severity level. No manual triage required.

Auto-resolution

When a monitor recovers, the incident closes automatically. Duration is calculated precisely — no forgetting to mark things resolved.

Escalating alert policies

Define multi-step escalation policies: notify on-call immediately, page the team lead after 10 minutes, trigger a webhook after 30. Fully configurable.

Severity levels

Incidents are classified as Critical, Major, or Minor based on your policy configuration. Route and escalate differently depending on severity.

MTTR tracking

Mean Time to Resolution is calculated automatically across all incidents. Understand your team's response performance over time.

Full incident history

Every incident is stored with its complete timeline — start, escalation steps, recovery, and total duration. A permanent record for postmortems and SLA reporting.

Incident lifecycle

StageWhat happens
Detected
Monitor fails — multi-region verification confirms the outage is real
Incident opened
Incident record created with severity, affected service, and start timestamp
First alert
Immediate notification to configured channels — Slack, email, webhook, and more
Escalation
If unresolved after your configured delay, escalation steps fire to reach broader teams
Resolved
Monitor recovers — incident closes, duration calculated, recovery notification sent
Reported
Incident logged in history for MTTR analysis, SLA reporting, and postmortems

How it works

01 — Create an alert policy

Define who gets notified and when

Set up escalation steps: immediate notification to your on-call channel, then broader alerts after a configurable delay if the incident isn't resolved.

02 — Attach to monitors

Connect policies to services

Assign alert policies to individual monitors or groups. Different services can have different escalation paths — critical infrastructure can page an entire team while minor services send a single Slack message.

03 — Incident fires automatically

No manual work during outages

When a monitor fails, the incident opens, the timeline starts, and alerts fire — all automatically. Your team can focus entirely on resolution, not incident coordination.

04 — Review and improve

Learn from every outage

After resolution, review the incident timeline, MTTR, and escalation log. Use the data to tighten alert policies, identify flaky services, and reduce future response times.

Frequently asked questions

Can I manually open or close incidents?
Yes. You can open incidents manually from the Incidents page for planned maintenance or issues detected outside of automated monitoring. You can also manually resolve any open incident.
How are severity levels determined?
Severity is set by your alert policy configuration. You can define rules like "if down for more than 5 minutes, escalate to Critical" or assign fixed severities per monitor type.
Does Vantaj send recovery notifications?
Yes. When a monitor recovers and an incident closes, a recovery notification is sent through the same channels as the original alert — so your team knows the situation is resolved without manually checking.
How long is incident history retained?
Incident history is retained for 7 days on the free plan, 90 days on Developer, and 6 months on Team plans.
Can I post manual updates to an incident?
Yes. From the Incidents page you can post timeline updates to any open incident. This is also how incidents appear on your public status page — customers see your updates in real time.

Ready to set up Incident Management?

Up and running in under a minute. Free for up to 20 monitors, no credit card required.

Start for free