Alert Channels
Configure how and where you receive notifications when monitors go down or recover.
Supported channels
Receive alert emails at one or more addresses. Emails include the monitor name, status, error details, and a direct link to the monitor.
Slack
Post alerts to a Slack channel using an incoming webhook URL. Messages include monitor details and a color-coded sidebar (red for down, green for recovery).
Discord
Send alerts to a Discord channel via webhook. Similar formatting to Slack with rich embeds showing monitor status.
Microsoft Teams
Post alerts to a Teams channel using an incoming webhook connector. Formatted as adaptive cards.
PagerDuty
Trigger PagerDuty incidents when monitors go down and automatically resolve them when monitors recover. Requires a PagerDuty integration key.
Webhook
Send alert data as JSON to any HTTP endpoint. Useful for custom integrations, Zapier, n8n, or your own alerting pipeline.
The webhook payload includes:
{
"event": "monitor.down" | "monitor.up",
"monitor": {
"id": "...",
"name": "...",
"url": "...",
"status": "down" | "up"
},
"check": {
"responseTime": 1234,
"statusCode": 500,
"error": "Connection timeout"
},
"timestamp": "2025-01-15T10:30:00Z"
}Push Notifications
Receive push notifications on the UptimeGuard mobile app. Enable push alerts in the mobile app settings.
Escalation rules
Each alert channel supports escalation settings:
- Alert after N failures — only send alert after consecutive failures (avoids false positives).
- Reminder interval — re-send alert every N minutes while the monitor is still down.
- Quiet hours — suppress alerts during specific hours (e.g. 11 PM - 7 AM).
- Notify on recovery — send a recovery notification when the monitor comes back up.
Testing alerts
You can send a test alert from the alert channel settings page. This sends a sample notification so you can verify your configuration is working.