Incident Alerting & Notifications
Real-time monitoring for zero-downtime SaaS
Configure Alerts
View API Docs
Intro
Downtime costs money. When your API spikes or your CDN goes silent, you need to know within seconds, not minutes. StatusPulse routes critical incidents to the exact teams responsible, ensuring your SREs and product managers wake up to resolved tickets, not panicked Slack threads.
We process over 2.4 million health checks daily across 14 global probe locations. When a threshold is breached, our notification engine triggers instantly, bypassing email inboxes and delivering actionable payloads directly to your incident command channels.
Where Your Alerts Arrive
Slack & Microsoft Teams
Push formatted incident blocks directly to dedicated channels like #ops-incidents or #api-reliability. Includes runbook links, affected endpoint names, and one-click acknowledge buttons that sync back to your status page.
PagerDuty & Opsgenie
Seamless integration with enterprise on-call scheduling. We map HTTP 5xx errors and latency spikes to P1/P2 severity levels, automatically creating incidents and rotating alerts across your engineering shift.
Discord & Webhooks
For community-facing projects and custom internal tools, Discord bots and raw JSON webhooks deliver millisecond-precision payloads. Define your own schema or use our pre-built templates for rapid deployment.
Transactional Email
Fallback and executive summaries via SMTP or SendGrid. Perfect for non-technical stakeholders who need daily digest reports, weekly uptime summaries, and post-incident review attachments.
Policies That Scale
Alert fatigue kills reliability. StatusPulse uses intelligent escalation tiers to ensure the right person gets paged at the right time, without spamming your entire engineering org.
Define time-based or severity-based rules. If a payment gateway returns 503 for over 30 seconds, Tier 1 notifies the DevOps Slack channel. If it persists for 5 minutes, Tier 2 triggers a PagerDuty on-call rotation. After 15 minutes, Tier 3 emails the CTO and engineering leads. All policies are version-controlled and can be toggled during maintenance windows to prevent false positives.
Customization That Reduces Noise
Generic alerts create confusion. Our templating engine lets you inject dynamic variables, suppress redundant notifications, and format messages for human readability.
Use Liquid-style syntax to pull in incident severity, endpoint names, response times, and error codes. Set deduplication windows so a flaky DNS resolver doesn't trigger 400 emails in an hour. Add custom runbook URLs, assignee tags, and severity color codes. Every template is previewable in the dashboard before deployment, ensuring your team receives clear, actionable instructions the moment an incident strikes.
Build Your First Template