UptimePad posts uptime alerts to Discord as rich embeds with status color, monitor link, affected regions, and an @-role mention so on-call gets pinged automatically. 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 | Role mentions | Per-channel routing | Recovery alerts |
|---|---|---|---|---|---|
| UptimePad Starter: Discord plus two monitoring regions | Starter+ | ✓ | ✓ | ✓ | ✓ |
| UptimeRobot Free: 50 monitors | ✓ | - | - | - | ✓ |
| Better Stack Paid only | - | ✓ | ✓ | ✓ | ✓ |
| StatusCake Paid · webhook only | - | - | - | - | ✓ |
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.
Most uptime tools make you create a Discord webhook URL in your workspace, then paste it back into the monitor. UptimePad has the OAuth flow built in: authorize the bot once, pick the channel(s), done.
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).
On a downtime alert, UptimePad can mention a Discord role (@oncall) so members of that role get a push notification on their phone, not just a passive message in a channel. Combine this with a rotating role in Discord (the on-call person changes the role each week) and you have a free pager. UptimeRobot only sends plain channel messages with no mentions.
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.
Yes. When you set up the Discord channel in UptimePad you can pick a role to mention on down alerts. Members of that role get a push notification on their phone (Discord defaults). Use a rotating "@oncall" role for a free pager.
Three layers: (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 →