Discord downtime alerts

Updated 25 October 2026 · By the Upcertain team

Create the webhook in Discord

1. Open the channel's settings (the gear next to its name).
2. Choose Integrations, then Webhooks, then New Webhook.
3. Name it, for example Upcertain, and check it posts to the right channel.
4. Choose Copy Webhook URL. It starts with https://discord.com/api/webhooks/.

You need the Manage Webhooks permission on the server. Anyone with the URL can post to the channel, so treat it like a password.

Add it in Upcertain

1. In Upcertain, open Settings, Alert channels and choose Discord. Owners, admins and editors can add channels.
2. Paste the webhook URL.
3. Pick the events to send: Down, Up (recovery) and SSL certificate expiry.
4. Tick Pre-select on new monitors if this should be the default for monitors you create from now on. Existing monitors keep their own choice.
5. Save, then use Send a test in the channel list to post a test message.
6. Open each monitor that should alert here and add the channel under its alert settings, with an optional delay and repeat interval.

What arrives in the channel

• Down: the monitor's name and address, the cause (for example HTTP 503, a timeout or a missing keyword), when it started, and buttons to acknowledge or view the incident.
• Still down: a reminder with the time so far, if you set a repeat interval on the monitor's channel (every 5 to 1440 minutes). Acknowledging the incident stops reminders.
• Up: the recovery with the cause and the total downtime, in the same channel.
• SSL certificate expiry: a warning on the days you chose before a certificate expires.
• Grouped alert: if alert grouping is on and several monitors fail within a few minutes, one message lists them all instead of one message each.

Alerts are embeds with a coloured edge (red, green or amber), the summary and the key fields, plus links to acknowledge or view the incident in Upcertain.

Public status for your community

If your users ask "is it down?" in Discord, pair the alert channel with a status page and pin its address. Your team gets the detail in a private channel; everyone else reads the status page.

Good practice

• Keep alerts in a private staff channel; post updates for users yourself.
• Use a repeat interval only on critical monitors, so the channel does not fill with reminders.
• Use Send a test after changing the channel's webhook in Discord.