UptimeRobot Discord Alerts and What Each Plan Adds
November 2026 · UptimeHub
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
UptimeRobot sends Discord alerts on every plan, including Free. You paste a Discord channel webhook into UptimeRobot as an integration and pick which monitors and events post there. What you pay for is not the Discord connection. It is how quickly the alert fires (every 5 minutes on Free, 60 seconds on Solo, 30 on Team, 15 on Scale) and how many people besides the Discord channel get told.
This is a reading of UptimeRobot's own Discord integration page and pricing page, checked on 17 November 2026. UptimeRobot localizes its price list by visitor location, so euro and dollar amounts vary by region and we do not repeat them here. The plan structure is the same everywhere, and the plan structure is what decides which tier you need.
UptimeRobot Discord alerts by plan
| Plan | Discord alerts | Check interval | Monitors | Status pages | Notify-only seats |
|---|---|---|---|---|---|
| Free | Yes | 5 minutes | 50 | 1 | None listed |
| Solo | Yes | 60 seconds | 10, or 50 as an option | 3 | 0 |
| Team | Yes | 30 seconds | 100 | 100 | 3 |
| Scale | Yes | 15 seconds | 200, or 500 as an option | Unlimited | 5 |
UptimeRobot groups Discord with Google Chat, Pushover, Pushbullet and Splunk as its basic third-party integrations. Slack, Mattermost, Telegram and Microsoft Teams sit in a separate row on the comparison table, and webhooks, Zapier and PagerDuty are listed among the additions on Team. So if Discord is the only place your team reads alerts, the integration will never be the reason to upgrade. The interval and the seat rules will be.
How long a Discord alert takes at each interval
An outage starts at a random moment between two checks. On average it waits half an interval before the first failed check, and at worst it waits a full interval. That wait is the floor on how late your Discord message arrives, before any retry or confirmation the monitor runs. The table assumes six outages a month, which is ordinary for a small SaaS once you count deploys gone wrong, a database restart and a provider incident.
| Interval | Average wait before the first failed check | Worst case | Unreported minutes over 6 outages |
|---|---|---|---|
| 5 minutes (Free) | 2.5 minutes | 5 minutes | 15 minutes |
| 60 seconds (Solo) | 30 seconds | 60 seconds | 3 minutes |
| 30 seconds (Team) | 15 seconds | 30 seconds | 1.5 minutes |
| 15 seconds (Scale) | 7.5 seconds | 15 seconds | 45 seconds |
Fifteen minutes a month sounds small until you look at where those minutes land. They are the first minutes of every incident, the stretch where customers find the problem before you do and the support inbox fills up. For a hobby bot or a community server that is fine. For anything with paying users, the step from 5 minutes to 60 seconds is the one that changes who notices first, and the step from 60 to 30 seconds is the one that keeps short blips from going unseen.
How to connect UptimeRobot to Discord
The setup takes about two minutes and needs no bot. In Discord, open the channel settings, go to Integrations, create a webhook and copy its URL (Discord explains the mechanics in its introduction to webhooks). In UptimeRobot, open Integrations and API, click Add next to Discord, paste the URL, choose the events and save. Then attach that integration to the monitors that should post there.
Two settings are worth a minute of thought. First, decide whether recovery messages belong in the same channel. Down and up messages together make a clean timeline, but a flapping monitor can post a dozen pairs in an hour. Second, use separate webhooks for separate channels. Production alerts in one channel and staging in another stops the production channel from being muted out of fatigue, which is the most common way Discord alerting quietly fails.
Do you need a Discord bot for uptime alerts?
No. For website, API and server monitoring a channel webhook does everything a bot would, with nothing to host. A bot only makes sense when you want commands inside Discord, such as asking for the current status of a monitor, or when the thing you monitor is itself a Discord bot that has no public URL. For that last case, have the bot send a heartbeat to a heartbeat monitor every few minutes, so a crashed bot shows up as a missing ping.
Where Discord alerts fall short for a paying product
Discord is a good place for awareness and a poor place for waking someone up. Channel notifications follow each member's server settings, busy servers are often muted on phones, and nothing escalates if nobody reacts. At 3am a Discord message is a log entry, not a page.
The fix is to layer channels rather than replace Discord. Keep Discord for the team's shared view, then send confirmed outages on revenue paths to SMS or PagerDuty for whoever is on call. On UptimeRobot, SMS and voice calls run on credits (Solo includes 10 to 20, Team 30, Scale 50 to 200), and PagerDuty sits with webhooks on Team. The seat rules matter too. Solo includes no notify-only seats, so the Discord channel ends up doing the job of telling everyone, which is exactly the job it is worst at.
UptimeRobot vs UptimeHub for Discord alerts
We build UptimeHub, so weigh this table accordingly. Every cell comes from each product's own pricing page.
| UptimeRobot | UptimeHub | |
|---|---|---|
| Discord on the cheapest tier | Yes, on Free | Yes, on Starter ($24 a month billed yearly) |
| 60 second checks from | Solo | Starter |
| 30 second checks from | Team | Pro ($49 a month billed yearly, 100 monitors) |
| Slack, Teams, Telegram, PagerDuty, webhook | Spread across tiers | Every plan |
| Outage confirmation | Not stated on the pricing page | Retry from other regions before alerting, two regions |
| Team and client seats | Counted per plan | Unlimited, never per seat |
| Free plan | Yes, 50 monitors at 5 minutes | No |
The honest verdict is simple. If you run a hobby project or a community server and Discord is the only channel you need, UptimeRobot Free does the job and you should keep it. If the thing being monitored earns money, the comparison that matters is UptimeRobot Team against UptimeHub Pro, because that is where 30 second checks, PagerDuty and a team bigger than one person meet. Our UptimeRobot pricing breakdown converts every tier into a cost per monitor, and the UptimeRobot alternative page covers the rest of the switch, feature by feature.
A setup that works for a small team
Here is what we would run for a five person product team that lives in Discord. One channel for production alerts with down and up messages, one quieter channel for staging and SSL warnings, and SMS to the on-call phone only for the checkout, login and API monitors. Background jobs get heartbeats that post to the production channel when a ping is late. If your app runs a PHP framework scheduler and queue workers, our scheduler and queue heartbeat setup shows how each one sends those heartbeats with a single line.
Pair the alerts with a status page so customers are not the ones posting in your Discord to ask whether you are down. UptimeRobot's own limits on that are in our breakdown of UptimeRobot status page limits by plan, and every UptimeHub plan includes a branded page that updates itself from the same checks. You can compare the plans and have the first Discord alert posting in a few minutes.
Is the UptimeRobot Discord integration free?
Yes. UptimeRobot lists Discord among its basic integrations and states that it works on all plans, including Free. The free tier checks every 5 minutes, so alerts can arrive up to 5 minutes after an outage begins. Paid tiers keep the same Discord integration and shorten the interval to 60, 30 or 15 seconds.
Why is UptimeRobot not sending alerts to Discord?
The usual cause is that the Discord integration exists but is not attached to the monitor, or the webhook was deleted in Discord and UptimeRobot still holds the old URL. Check the monitor's notification settings, recreate the webhook if needed, and test it with a temporary monitor pointed at a URL that returns an error, which should post within one interval.
Know your site is down before your customers do
Start monitoring your sites, APIs and services from two regions, with alerts by Slack, email, SMS and webhook and a branded status page. Transparent, flat pricing per monitor.