Instant Alerting — Slack, PagerDuty, Webhooks
Route downtime notifications to the tools your team already uses. Sub-second delivery to Slack channels, PagerDuty services, custom webhooks, SMS, and email — with zero missed incidents.
Deliver Alerts Where Your Team Lives
StatusPulse pushes verified incidents through five delivery channels simultaneously. When the payment-api endpoint at api.stripe-payments.io drops HTTP 200 responses, your on-call engineer gets a Slack thread, a PagerDuty critical event, an SMS to their registered number, and a detailed email — all within 800 milliseconds of detection.
Each channel supports rich payloads: incident ID, affected check name, last known response time, error class, and a direct link to the live status dashboard. Duplicate suppression ensures your team sees one consolidated alert per incident, not 47 repeated pings.
Slack
Post threaded alerts to any channel or direct message a user. Supports attachments with response-time graphs, emoji-based severity indicators, and interactive buttons to acknowledge or escalate directly from Slack. Connects via Incoming Webhooks or the Slack Bolt SDK.
PagerDuty
Integrates with PagerDuty's Events API v2. Maps StatusPulse severity levels to P1–P4 priorities. Includes automatic incident resolution callbacks when checks recover, so your PagerDuty timeline stays accurate without manual closure.
SMS
Delivered via Twilio and Vonage with global coverage across 190+ countries. Messages include a short URL to the incident detail page. Rate-limited to three SMS alerts per incident to prevent carrier throttling and bill shock.
HTML-formatted digests sent through SendGrid with dedicated IPs. Supports distribution lists, individual recipients, and CC fields. Daily summary emails aggregate all incidents from the previous 24 hours for managers who don't need real-time pings.
Webhooks
POST JSON payloads to any HTTPS endpoint. Retry logic with exponential backoff (1s, 5s, 30s, 2m, 10m) over five attempts. Payloads include the full check result object, your API key in the X-StatusPulse-Signature header, and a retry_count field for idempotency handling.
Microsoft Teams
Adaptive Card notifications posted to Teams channels via Incoming Webhook connector. Cards display color-coded severity, check status, and actionable buttons to mute, investigate, or create a linked Planner task for post-incident follow-up.
Automate On-Call Escalation
When a critical check fails — like the TLS certificate on checkout.acme-commerce.com expiring in under 72 hours — StatusPulse escalates through your defined policy chain until someone acknowledges the incident. No more silent failures buried in an unread Slack channel at 3 AM.
Tiered Escalation
Define up to 10 escalation tiers. Tier 1 notifies your primary on-call (e.g., Sarah Chen via PagerDuty). If unacknowledged after 5 minutes, Tier 2 pages the secondary on-call (Marcus Rivera via SMS + Slack). Tier 3 escalates to the engineering manager (Priya Sharma via email + phone call). Each tier can have different channels and timing.
Acknowledgment Tracking
Escalation pauses immediately when any responder clicks the acknowledge link in their alert. StatusPulse records who acknowledged, at what timestamp, and from which channel. Post-incident reports show mean time to acknowledge (MTTA) — currently averaging 4 minutes 12 seconds across all customers.
Recovery Notifications
When a check returns to healthy status, StatusPulse sends a resolution alert to the same channels used for the initial incident. Recovery messages include total downtime duration, number of failed probes, and a link to the full incident timeline for your postmortem documentation.
Follow-the-Sun Handoffs
Schedule escalation policies by timezone. When your US East Coast team clocks out, incidents automatically route to your Singapore office on-call (e.g., Wei Lin) without manual handoff. Policies support recurring weekday schedules, holiday calendars, and one-time overrides for known change windows.
Escalation policies are configured per-check or per-group. A certificate expiration warning on a staging environment might only email the DevOps team, while a 5xx error rate spike on your production API gateway triggers a full three-tier escalation with SMS and PagerDuty from the first tier.
Silence Alerts During Planned Downtime
Rolling out a database migration on db-primary.prod.internal? Deploying a new Kubernetes cluster in us-east-1? Schedule a maintenance window to suppress alerts for specific checks, groups, or your entire account — without disabling the underlying monitoring.
Scheduled Windows
Create one-time or recurring maintenance windows with start/end times in any timezone. Recurring windows support weekly patterns (e.g., "every Tuesday 02:00–04:00 UTC" for your nightly backup jobs). Windows can target individual checks, check groups, or all checks in a specific region.
Grace Periods
Configure a 5-minute grace period at the start of each maintenance window. If a check recovers within that window, no incident is created at all. If it stays down beyond the grace period and the maintenance window hasn't started yet, alerts fire normally — protecting you from accidentally silencing real outages.
Audit Trail
Every maintenance window is logged with who created it, when it was active, which checks were silenced, and whether any incidents would have fired during that period. Export audit logs as CSV or query them via the API for compliance reporting and SOC 2 documentation.
API-Driven Windows
Create, modify, and delete maintenance windows programmatically via REST API. Hook into your CI/CD pipeline so that every deployment to production automatically opens a 30-minute maintenance window for the affected service, then closes it when the pipeline completes — no manual dashboard clicks required.
Maintenance windows override all escalation policies. During an active window, checks continue running and recording metrics, but no Slack messages, PagerDuty events, SMS messages, emails, or webhook payloads are dispatched. The moment the window expires, full alerting resumes immediately — no restart or reconfiguration needed.