ON-CALL & ALERTING

Never miss a critical alert again

Smart escalation policies, on-call rotation management, and multi-channel alerting. Reduce your mean time to response and keep your incident response platform running like clockwork.

Escalation Policy: Production Critical
1
Notify on-call engineerACTIVE

Current on-call from "Platform Team" schedule

SMS
Push
Wait 5 minutes
2
Phone call to on-call

Same on-call engineer with voice alert

Phone
Wait 10 minutes
3
Escalate to team lead

Notify engineering manager + team Slack

Phone
Slack
Email
mihari.io / alerts / fire
LIVE
FIRING
INC-3012
CRITICAL Triggered min ago

checkout-api · HTTP 503

checkout-api.acme.com returning 503 — confirmed by 3 consecutive checks

Servicecheckout-api
Error rate%
EscalationStep 1 of 3
Assigned
YTYuki Tanaka
Acknowledge
Resolve

PAGE-API-P1 · ROTATION

Page the right human. Once. Never twice — escalation falls forward until somebody acknowledges.

mihari.io / on-call / page-api-p1
LIVE
ROTATION · PAGE-API-P1
Y
Yuki Tanaka primary
SRE · GMT+9 · acked 2 incidents this week
HAND-OFF IN4h 12m→ @maël
ESCALATION POLICYstops at first acknowledgement
T+0m● firing
Page primary
Yuki
T+5m
Page secondary
Maël
T+12m
Notify leads
##sre-leads
T+20m
Trigger runbook
▸ rb-checkout
WEEK 18 · GMT+0
Yuki
Maël
Priya
Sam
Mon
Tue
Wed
Thu
Fri
Sat
Sun
P1Checkout API · elevated 5xx in eu-west-1paged @yuki · 00:01:42 ago

ESCALATION POLICIES

Route alerts to the right person, every time

Build multi-step escalation policies that ensure no critical alert goes unacknowledged. Define who gets notified first, how long to wait, and who to escalate to if the incident remains unresolved. Your on-call management software should work as hard as your team does.

  • Multi-step escalation with configurable wait times between each level
  • Automatic escalation when alerts are not acknowledged within your SLA
  • Per-severity escalation policies for critical, warning, and info alerts
  • Time-based routing: different policies for business hours vs. off-hours
  • Unlimited escalation steps with any combination of notification channels
March 2026
Mon
Tue
Wed
Thu
Fri
Sat
Sun
23
Sarah K.
24
Sarah K.
25
Sarah K.
26
Sarah K.
27
Sarah K.
28
Sarah K.
1
Sarah K.
2
Sarah K.
3
Sarah K.
4
Sarah K.
5
Sarah K.
6
Sarah K.
7
Sarah K.
8
Mike R.
9
Mike R.
10
Mike R.
11
Mike R.
12
Mike R.
Alex P.
13
Mike R.
14
Mike R.
15
Alex P.
16
Alex P.
17
Alex P.
18
Alex P.
19
Alex P.
20
Alex P.
21
Alex P.
22
Sarah K.
23
Sarah K.
24
Sarah K.
25
Sarah K.
26
Sarah K.
27
Sarah K.
28
Sarah K.
29
Mike R.
Sarah K.
Mike R.
Alex P.
Override
ON-CALL SCHEDULES

On-call rotations that respect your team

Create fair, predictable on-call rotation schedules that distribute the load evenly across your team. Support for weekly, daily, and custom rotation patterns with override shifts for vacations and holidays. Your on-call management software should make scheduling effortless, not stressful.

  • Weekly, bi-weekly, and custom rotation intervals
  • Override shifts for vacations, holidays, and planned absences
  • Automatic handoff notifications when rotations change
  • Google Calendar and Outlook calendar integration
  • Fair rotation algorithms that balance on-call load across the team
MULTI-CHANNEL

Reach your team on every channel that matters

Different situations call for different alert management approaches. A warning might go to Slack, but a critical production outage needs an SMS and a phone call. Configure notification preferences per team member, per severity level, and per time of day. Every page is tracked until someone acknowledges it.

Email

Rich HTML alerts with full context

Active
sent / 24h

SMS

Reply ACK/RES to manage incidents

Active
sent / 24h

Phone Call

Automated voice alerts for critical issues

Active
sent / 24h

Slack & MS Teams

Interactive messages with action buttons

Active
sent / 24h

Push Notifications

Mobile app alerts for iOS and Android

Active
sent / 24h
Email Notification
From: alerts@mihari.ioJust now

[CRITICAL] api.example.com is DOWN

HTTP 503 confirmed by consecutive checks at 14:32 UTC. Escalation policy "Production Critical" activated.

SMS Alert

[Mihari] CRITICAL: api.example.com DOWN. HTTP 503, confirmed by retries. Acknowledge: mihari.io/i/3012

Slack Message
M
MihariAPP2:32 PM

Critical Alert - api.example.com

Service is consistently returning HTTP 503

Acknowledge
View Incident
Phone Call Alert

Calling Sarah K. (+1 ***-***-4829)

Automated voice alert with incident details

INCIDENT MANAGEMENT

Track every incident from detection to resolution

A complete incident response platform with timelines, team collaboration, acknowledgments, and structured postmortems. Reduce your MTTR and learn from every outage.

Incident INC-3012RESOLVED
Duration: 23m 14s

Connects with your existing tools

Integrate Mihari with the communication and incident management tools your team already uses. Send alerts wherever your team works.

Slack

Interactive alerts

MS Teams

Bot & cards

PagerDuty

Events API v2

Push

Mobile notifications

Email

Rich HTML alerts

SMS

Text alerts

Webhooks

Custom payloads

Phone

Press 1 to acknowledge

Built to get the right person on the incident

What the alerting stack actually ships — product facts, not marketing promises.

8

Notification channels

24/7

On-call schedule coverage

ACK

From app, Slack, or press-1 call

€0

Email alerts on the Free plan

Streamline your incident response today

Set up escalation policies, on-call rotations, and multi-channel alerting in minutes. Free for small teams.