UptimePad posts uptime alerts to Discord as rich embeds with status color, monitor link, affected regions, and recovery context. Discord alerts unlock on Starter and above. Below: how UptimePad compares to UptimeRobot, Better Stack, and StatusCake on Discord integration.
| Tool | Lowest tier | Rich embeds | Webhook setup | Per-channel routing | Recovery alerts |
|---|---|---|---|---|---|
| UptimePad Starter: Discord plus two monitoring regions | Starter+ | ✓ | Discord webhook URL | ✓ | ✓ |
| UptimeRobot Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
| Better Stack Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
| StatusCake Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
UptimePad uses Discord's embed format, which means the alert renders as a colored card (red for down, yellow for degraded, green for recovery), not a wall of plain text. Each embed shows: monitor name, URL, the regions that disagreed, response code, the time the state changed, and a deep link to the incident in the dashboard.
Paid plans can include the affected regions and HTTP result in the embed, so whoever is on call gets the useful context without opening the dashboard first.
Create a Discord webhook in the channel that should receive alerts, paste the URL into UptimePad, and save it as a notification channel. UptimePad validates the webhook during setup so a typo is caught before an incident.
You can attach the same Discord channel to as many monitors as you want, or route different monitor groups to different channels (status-page traffic to #incidents-public, internal API monitors to #ops-internal).
Discord gets noisy fast if every monitor lands in one channel. UptimePad lets you create separate Discord notification channels and attach them to the monitors that need them. Customer-facing incidents can go to a visible operations room while lower-priority checks stay in a quieter channel.
No. Free uses email alerts only. Discord unlocks on Starter and above so the free tier stays useful without becoming an unlimited alert fan-out service.
Discord embeds show the standard incident details: affected regions, response code, response time, and a link to the incident timeline.
Yes. Create multiple Discord channels in UptimePad and attach them per monitor. Common pattern: customer-facing monitors go to #incidents-public, internal monitors go to #ops-internal.
No. Discord delivery uses webhook URLs. Create the webhook in Discord, paste it into UptimePad, and UptimePad sends a test message before saving the channel.
Three safeguards: (1) selected regions must agree before a state change is confirmed, (2) flap protection requires a monitor to hold a state for two consecutive checks, (3) alert grouping collapses repeated events from the same monitor into one alert with a count.
Yes. Recovery alerts are green-embed and include the duration of the incident, the regions that recovered, and a link to the incident timeline. You can disable recovery alerts per channel if you only want to be paged on downs.
Starter includes Discord alerts, two monitoring regions, and 100 monitors.
Start monitoring free →