Integration

Downtime alerts in Discord

Post open, acknowledge, and resolve into a Discord channel your team already stares at — after regions agree the target is down.

See pricing Setup docs

The message

What lands in Discord

Open, ack, and resolve — not a one-line “site down” with nowhere to go.

Event

What the room sees

Who should ack

Open

Monitor name, which regions failed, and a link into the incident. Not a bare “site down.”

Whoever owns that service in the server — often a volunteer. Name them in the topic, or Discord becomes a shout into the void.

Ack

Someone claimed it. The room can stop stacking “is this still down?” replies.

The person who clicked through. Discord does not assign an on-call; it only shows that a human showed up.

Resolve

A recover line so people stop refreshing status and arguing in-thread.

Nobody — unless you want a postmortem owner. That lives in Tallwatch, not in the Discord embed.

Use this when

Why Discord

Engineering or community already lives in Discord. You want the incident in that channel, not a second app they ignore.

Not instead of

What this channel is not

Discord does not wake a named person. Keep Slack if that is where work happens. Keep email or a webhook into your pager if someone has to own the ack at 2am.

Setup

Connect Discord

High-level steps — confirm the latest details in docs before you rely on it overnight.

Create or pick a Discord channel for incidents — not #general.
In Tallwatch, add a Discord alert channel and paste the webhook URL.
Attach it to a monitor or as a broadcast step, not as the only escalation.
Send a test. Confirm it is readable on mobile, then mute @everyone.

FAQ

Discord alerts, answered

Discord is a paid channel. Plan limits, on-call pairing, and what lands in the room.

Other channels

Not this one?

Slack

The channel you already have open. On Free.

The phone in your pocket. A bot, not a schedule.

Email

Works at signup. Slow. Still the backup everyone forgets to add.

Discord is on Pro — Slack works on Free tonight

Start with email and Slack. Add Discord when the server is already where the team lives.

See pricing Read the docs

Agent

Page as markdown

Raw agent-readable copy for this route. Copy it into a model, or browse the site-wide agent index at /llms.txt.

---
title: "Discord"
description: "Send Tallwatch downtime alerts to Discord after multi-region consensus. Open, ack, and resolve in your channel. Paid plans."
canonical: https://tallwatch.com/integrations/discord
url: https://tallwatch.com/integrations/discord
llms_url: https://tallwatch.com/llms.txt
updated: 2026-09-04
---
Integration

# Downtime alerts in Discord

Post open, acknowledge, and resolve into a Discord channel your team already stares at — after regions agree the target is down.

[See pricing](https://tallwatch.com/pricing) · [Setup docs](https://docs.tallwatch.com/alerts/discord)

## What lands in Discord

| Event | What the room sees | Who should ack |
| --- | --- | --- |
| Open | Monitor name, which regions failed, and a link into the incident. Not a bare “site down.” | Whoever owns that service in the server — often a volunteer. Name them in the topic, or Discord becomes a shout into the void. |
| Ack | Someone claimed it. The room can stop stacking “is this still down?” replies. | The person who clicked through. Discord does not assign an on-call; it only shows that a human showed up. |
| Resolve | A recover line so people stop refreshing status and arguing in-thread. | Nobody — unless you want a postmortem owner. That lives in Tallwatch, not in the Discord embed. |

Use this when
## Why Discord

Engineering or community already lives in Discord. You want the incident in that channel, not a second app they ignore.

Not instead of
## What this channel is not

Discord does not wake a named person. Keep Slack if that is where work happens. Keep email or a webhook into your pager if someone has to own the ack at 2am.

Setup
## Connect Discord

High-level steps — confirm the latest details in docs before you rely on it overnight.

1. **Step 1** — Create or pick a Discord channel for incidents — not #general.

2. **Step 2** — In Tallwatch, add a Discord alert channel and paste the webhook URL.

3. **Step 3** — Attach it to a monitor or as a broadcast step, not as the only escalation.

4. **Step 4** — Send a test. Confirm it is readable on mobile, then mute @everyone.

## Discord alerts, answered

Discord is a paid channel. Plan limits, on-call pairing, and what lands in the room.

### Is Discord on the free plan?

No. Free includes email and Slack. Discord needs Pro or Business.

### Can Discord replace on-call?

It can notify a room. For waking a specific person, pair it with on-call so someone owns the acknowledge.

### What does a Discord alert include?

Open, acknowledge, and resolve with the monitor name and a link back to the incident. Field layout is in the Discord alert docs.

## Discord is on Pro — Slack works on Free tonight

Start with email and Slack. Add Discord when the server is already where the team lives.

[See pricing](https://tallwatch.com/pricing) · [Read the docs](https://docs.tallwatch.com/alerts/discord)