Slack, PagerDuty, Email — Delivered in Under 10 Seconds
Zero-downtime reliability for modern cloud apps. StatusPulse routes every incident to the right team on the right channel, with smart deduplication and configurable escalation so your on-call engineers never sleep through a real outage.
Supported Notification Channels
Connect every channel your team already uses. StatusPulse pushes structured alerts with incident IDs, affected endpoints, and one-click runbook links — no raw JSON decoding required.
Slack
Post incident cards directly into #ops-incidents or your on-call channel. Each message includes the affected endpoint (e.g., api.statuspulse.io), current status, time since first failure, and an interactive "Acknowledge" button that syncs back to your dashboard. Webhook and Slack App install both supported.
PagerDuty
Trigger PagerDuty incidents with full severity mapping. StatusPulse sends v2 Events API payloads containing custom details like monitoring check type (HTTP, TCP, SSL), consecutive failure count, and the last successful response time. Automatically resolves PagerDuty incidents when the monitored endpoint recovers — no manual close needed.
Send HTML-formatted alert summaries to distribution lists or individual engineers. Emails include a live status snapshot table, affected check details, and a direct link to the incident timeline. Supports SMTP relay through your own infrastructure or StatusPulse's managed delivery pipeline with 99.97 % deliverability.
Escalation Policies
Define how alerts escalate when a critical incident isn't acknowledged. StatusPulse supports time-based and severity-based escalation rules so nothing falls through the cracks during off-hours.
Time-Based Escalation
If an incident goes unacknowledged for a configurable window — say 5 minutes for P1, 15 minutes for P2 — StatusPulse automatically notifies the next tier. Example: a failed HTTPS check on checkout.stripe-integration.example.com first alerts the primary on-call engineer via PagerDuty; after 5 minutes without acknowledgment, it escalates to the engineering manager and the #leadership-ops Slack channel.
Severity Routing
Map check failures to severity levels and route accordingly. SSL certificate expiring in 14 days triggers a P3 email digest; complete TLS handshake failure triggers a P1 PagerDuty incident with immediate Slack blast. You define the severity per endpoint, per check type, and per business-criticality tier.
Maintenance Windows
Suppress alerts during planned maintenance without disabling checks. Schedule a 2-hour window for a Kubernetes rolling restart, and StatusPulse records every probe result silently. If the endpoint doesn't recover by the end of the window, alerts resume immediately with full context about the planned downtime.
Smart Deduplication
Prevent alert fatigue without missing real incidents. StatusPulse correlates failures across checks, time windows, and endpoints so your team sees one actionable incident — not forty-seven noisy notifications.
Incident Grouping
When multiple checks fail simultaneously — for example, HTTPS, TCP, and DNS probes all return errors for the same host — StatusPulse groups them into a single incident. The first alert fires normally; subsequent failures within the grouping window (default 30 minutes) update the existing incident instead of creating new notifications.
Flapping Suppression
Intermittent network blips shouldn't wake your on-call engineer. If an endpoint alternates between up and down faster than the configured threshold — say 5 state changes in 10 minutes — StatusPulse pauses new alerts and posts a single "flapping detected" summary to Slack. Alerting resumes once the endpoint stabilizes in either direction.
Digest Mode
For non-critical monitors — like a staging environment health check or a third-party API you don't control — switch to digest mode. StatusPulse batches all status changes into a single daily or hourly email summary. During business hours you get real-time Slack pings; after hours you wake up to a consolidated report with every incident, recovery, and mean-time-to-repair metric.
Ready to Eliminate Alert Fatigue?
Join 2,400+ engineering teams that trust StatusPulse to deliver the right alert, to the right person, at the right time — every single time.