Broken Link Checker logo Broken Link Checker
& SEO Suite Login / Register

Uptime Monitor

Alert channels

Send uptime alerts to extra email addresses, Slack, Microsoft Teams, Discord or your own webhook, and attach each channel to the monitors it covers.

3 min read

An alert channel is one more place your uptime alerts go. By the end of this page you will have added a channel and attached it to a monitor.

Channels belong to your account. The same list shows on the Uptime Monitor page of every project.

Channel types

  • Email sends the alert mail to another address.
  • Webhook sends a JSON message to your own URL.
  • Slack, Teams and Discord post a short message to a channel through an incoming webhook URL.

SMS alerts are coming to Pro Business and Pro Agency.

Add a channel

  1. Open the project and click Uptime monitor in the sidebar.
  2. Click the Alerts tab.
  3. Pick a Type.
  4. Fill in the Destination. The field shows an example for each type, such as https://hooks.slack.com/services/... for Slack.
  5. Click Add channel.

The message "Alert channel added." confirms it. Webhook, Slack, Teams and Discord addresses must start with https://. They must also be reachable from the internet. Otherwise the form shows "That address is not reachable from our checkers."

Attach the channel to a monitor

A new channel is attached to nothing. It only fires for the monitors you tick it on.

  1. Click Edit on the monitor's row.
  2. Tick the channel under Alert channels.
  3. Click Save changes.

Repeat this for each monitor the channel should cover. Monitors on other projects need the same step from their own project page.

What each channel receives

Slack and Teams get a JSON message with one line of text. A down alert reads "Front page is down. Cause: HTTP 503." and a recovery reads "Front page is back up." Discord gets the same line.

A webhook gets a POST request with a JSON body like this one:

{
  "event": "incident.opened",
  "monitor": {"id": 123, "name": "Front page", "url": "https://example.com/", "type": "http"},
  "incident": {"id": 456, "cause": "HTTP 503", "started_at": "2026-09-26T09:41:03+00:00", "ended_at": null},
  "sent_at": "2026-09-26T09:41:10+00:00"
}

A recovery sends incident.resolved as the event, with ended_at filled in. Times are in UTC.

Your endpoint has 10 seconds to answer. Any 2xx status counts as delivered. A failed webhook, Slack, Teams or Discord delivery is not retried.

Change or delete a channel

Channels cannot be edited. To change a destination, delete the channel and add it again. Then tick the new channel on your monitors.

To delete a channel, click Delete next to it and confirm. The message "Alert channel deleted." confirms it.

Email alerts Who receives uptime mails, what the down, recovery and expiry mails say, and how to send alerts for one monitor to a different address. Escalation ladders Alert a second and third contact when nobody acknowledges an incident. Set the order and the delay for each step, and stop the ladder with one click. HTTP monitors Add an HTTP monitor, pick its check interval, watch for a keyword, set Alert after, and pause, edit or delete a monitor later.