Alerting & Notifications
An uptime monitor is only useful if it tells you when something breaks. DownWarning supports five notification channels out of the box, with configurable routing so the right team member is alerted at the right time.
Slack
Post alerts directly into any Slack channel. Includes monitor name, status, response time, and a link to the incident.
Telegram
Receive instant messages in a Telegram chat or group. Lightweight and fast — ideal for on-the-go engineers.
Microsoft Teams
Route alerts to Teams channels via incoming webhooks. Keep your incident response in the same tool your team already uses.
Classic email notifications with full incident details. Configure per-monitor or account-wide alert contacts.
Webhooks
Send a signed HTTP POST to any URL when an incident occurs. Integrate with PagerDuty, Opsgenie, or your own automation.
Multi-channel escalation
Assign different alert contacts to different monitors. Route production database alerts to the DBA team on Slack while sending front-end outage notifications to the web team via Telegram. Scale plan users can configure up to 50 alert contacts across all channels.
Every plan includes email alerting. Slack, Telegram, Teams, and Webhooks are available on all plans — from the free Starter plan onward.
Alert fatigue is a real cost: teams that get paged for every blip start ignoring pages altogether. DownWarning's per-monitor routing and escalation rules exist so that only the people who actually need to act get notified, and everyone else's phone stays quiet. Getting this right early — before an on-call rotation grows resentful of a noisy tool — is usually easier than fixing it after the fact.
Escalation rules matter most during an actual incident, not while configuring the dashboard, so it's worth testing them before you need them. Trigger a monitor manually, confirm the right channel receives the alert with the right formatting, and adjust routing before a real outage becomes the first time anyone finds out the notification never arrived. A five-minute test now is cheaper than finding out during an incident that a Slack webhook was misconfigured.
Alerting FAQ
Can different monitors alert different people?
Yes. Assign specific alert contacts per monitor, so a production database alert reaches your DBA team on Slack while a marketing site outage goes to the web team on Telegram instead.
What information is included in an alert?
Every alert includes the monitor name, current status, response time or failure reason, and a direct link to the incident so you can start investigating immediately.
Can I integrate DownWarning with PagerDuty or Opsgenie?
Yes, through Webhooks. Send a signed HTTP POST to any URL when an incident opens or resolves, and wire it into PagerDuty, Opsgenie, or your own automation.
Will I be notified when a monitor recovers, not just when it fails?
Yes. Recovery notifications go out through the same channel as the original alert, so your team knows an incident is over without having to check the dashboard. No manual acknowledgment step is required for that notification to fire.