Alert integrations
Get alerts where your team already works. Route each monitor to its own channels, set team-wide defaults, or hand everything to an escalation policy.
How alerts are routed
A channel is one destination: a Slack webhook, a set of email addresses, a PagerDuty service. Each monitor sends to the channels you pick for it, or to the channels marked as team defaults. For anything that should wake someone up, attach an escalation policy instead, which alerts the person on call and keeps going until someone acknowledges.
You'll hear when a monitor goes down (only after the failure is confirmed), when it recovers and how long it was down, and when someone acknowledges. Every channel can send a test before you rely on it, and a delivery log shows what was sent where, and any errors.
Email, chat, webhook, PagerDuty and Opsgenie alerts are included on every plan, including Free. SMS and phone calls use credits included in the paid plans, from Essentials up.
Send alerts to up to 20 addresses per channel, such as a shared ops inbox and a couple of people. Each email gives the monitor, what happened, the target, the time, a link to the incident and a one-click acknowledge link. Email is included on every plan.
SMS
Text messages through Twilio to up to 10 numbers per channel, in international format (+447700900123). Messages are short and end with an acknowledge link. Each message uses one credit: Essentials 20, Pro 100 and Business 300 credits a month. SMS also works as a method in escalation policies, sent to whoever is on call.
Phone calls
A voice call through Twilio that reads the alert out, twice. Calls are kept for bad news, a service going down, a reminder or a test, so a recovery never rings anyone at 3am; recoveries go to your other channels. Calls use the same credits as SMS.
Slack
Post to a channel with a Slack incoming webhook. Each message is colour-coded (red for down, green for recovered, amber for acknowledged) with the details, an Open link and an Acknowledge link, so whoever picks it up can claim it from Slack.
Microsoft Teams
Post to a Teams channel through a Workflows or incoming webhook URL. Alerts arrive as an Adaptive Card with the title, details and target, and Open and Acknowledge buttons.
Discord
Post to a Discord channel with a channel webhook. Alerts arrive as a colour-coded embed linking to the incident, with an acknowledge link when the incident can still be acknowledged.
Google Chat
Post to a Google Chat space with the space's webhook URL. Messages carry the title, details, target and links to open and acknowledge the incident.
Telegram
Send alerts from your own Telegram bot to a chat, group or channel. Add the bot token from BotFather and the chat ID (a number, or an @channel name). Messages are plain text with every detail and link.
Webhooks
POST a JSON payload to your own endpoint for anything the other channels don't cover: a chat bot, a ticketing system or your own automation. The payload has event (down, up, acknowledged, incident, reminder or test), title, text, monitor, target, incidentId, at, url and ackUrl.
Add a signing secret and every request carries an X-Signature-SHA256 header: the HMAC-SHA256 of the raw body with your secret, in hex. Check it before trusting the request:
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const ok = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(req.get('X-Signature-SHA256') ?? ''));Webhook URLs must use HTTPS, and can't point at private network addresses.
PagerDuty
Send events to a PagerDuty service with its Events API v2 integration (routing) key. A failure triggers a PagerDuty incident, acknowledging in Uptime Dog acknowledges it, and recovery resolves it. A stable deduplication key ties them together, so one outage is one PagerDuty incident.
Opsgenie
Create alerts in Opsgenie with an API integration key, in the US or EU region. A failure opens a P1 alert (a test opens a P5), acknowledging in Uptime Dog acknowledges it, and recovery closes it. Alerts are matched by alias, so updates land on the same alert.
REST API
Everything in the app is available at /api/v1 with a team API key: monitors, checks and response-time series, incidents and their updates, maintenance, status pages and subscribers, channels, on-call schedules, escalation policies and reports. Use it to create monitors from your deploy scripts or open incidents from your own tools.
curl -H "Authorization: Bearer $UPTIMEDOG_KEY" https://uptimedog.makingstuffs.com/api/v1/monitorsSet up your first monitor in under a minute
Uptime Dog is free for up to 20 monitors. No card needed.
Start monitoring free