Website monitoring with Discord alerts
Uptimia checks your sites from 171+ locations and posts every confirmed failure into your Discord channel — which site is affected, what failed and since when. When it comes back, it posts again, so nobody has to go and check whether it is fixed.
Overview
Last 7 DaysIncident #4127 · policy Store on-call
Outages ignore your working hours
A server dies late on a Saturday night. Nobody is watching a dashboard, the inbox is asleep, and the only app still making a sound on anyone’s phone is Discord.
I’ll see it from my desk
A web server has no way to tell you it stopped answering. Whatever breaks outside working hours stays broken until working hours.
The community finds out for you
By morning the outage has its own thread — screenshots, tagged mods, a mod answering the same question twelve times. The channel that stayed silent all night is the one that should have spoken first.
An outage handled from a phone
The check fails at night and the phone buzzes. The alert is acknowledged with a tap, the fix is talked through in the channel, and the recovery posts itself to the same place.
Wired up in three steps
A channel, a routing decision, a safety net. Nothing joins your member list, no roles to grant, no app to approve.
Connect your channel
Point Uptimia at the Discord channel the alerts should land in and send a test — you see one arrive before anything real depends on it.
Choose what posts where
Outages to #alerts, certificate and domain warnings to a quieter channel, the speed feed somewhere nobody gets notified. Each monitor picks its own.
Add the safety net
If nobody picks the alert up, Uptimia keeps going — a text to whoever is on call, then the next name on the list. Quiet hours are set per person.
Connect Discord to Uptimia
The whole walkthrough, in the Help Center: creating the channel webhook in Discord, adding the integration, sending a test ping, and assigning it to your monitors.
What else pings your channel
A green homepage hides a certificate expiring, a cron job that stopped on Tuesday, a checkout that dies on the last step. Every check Uptimia runs can post into the same channel — here are eight of them, and what each one notices.
Send each alert to the channel that should see it
A channel that mixes a real outage with a weekly speed report is a channel people mute. Keep the urgent ones in a channel that pings everyone, and send the rest somewhere quieter.
Bad news travels fastest in Discord.Let it outrun your customers.
Every monitor type and every alert channel — free for 30 days.
What sits behind the ping
Discord is where the news arrives. Behind it sits the platform that finds the problem in the first place, keeps the record that proves your uptime, and tells your community while you fix it.
The dashboard behind the pings
When you want the whole picture — every monitor, incident and response time — it’s one tab away, not an everyday obligation.
Confirmed before the post
A failure is re-checked from other regions — up to 3 of them, your call per monitor — so one flaky route never wakes a channel.
A status page for the community
Publish status on your own domain and watch the “is it down?” DMs dry up.
Monthly uptime PDFs
Numbers for the client, the sponsor or the retro — generated and emailed on schedule.
Time to acknowledge, recorded
Every acknowledgement is stamped against the incident, so “we got faster at this” is a number, not a feeling.
The ladder past Discord
Post ignored? On an escalation policy (Professional plan and above) Uptimia texts the on-call, then their backup. Maintenance windows and per-recipient quiet hours keep planned work silent.
How Discord downtime alerts work
Uptimia checks your sites from 171+ locations and posts every confirmed failure into your Discord channel. The message says which site is affected, what failed and since when — and when it recovers, it posts again with the total time down.
Email doesn’t buzz your pocket
Email is where alerts wait their turn. For a team that lives in Discord, the inbox is the last surface anyone checks — and the last one that makes a sound at night.
The push finds whoever’s awake
Discord handles the last mile: its per-channel notification settings decide whose phone lights up, and whoever stirs first taps the acknowledge link.
Every message your server receives
The channel gets the full lifecycle, not just the bad news — each stage is its own post, so scrolling #alerts reads like the incident’s diary. How the ladder is built →
See all 12 alert channels →| Message | Posts when | What it carries |
|---|---|---|
| Down alert | Backup probes repeat the failure | Monitor and state, plus the acknowledgement link on an escalation policy |
| Escalation step | The post goes unanswered | The next channel or an SMS, then the next person |
| Group digest | Monitors on one policy fall together | One post for the storm, not one per monitor |
| Join update | More monitors join that group | A throttled follow-up naming the newcomers |
| Recovery | The check goes green again | The all-clear, with total time down |
| Test message | You press Send test | Proof it lands, before anything is at stake |
Discord alerts FAQ
01How do I get downtime alerts in Discord?+
02Do I have to invite a bot?+
discord.com or discordapp.com, over HTTPS, and pins the address it resolved so the post cannot be redirected.03Will it actually wake me at 2 a.m.?+
#alerts ping and keep everything else silent.04Can alerts go to a private channel?+
05What does a ping look like?+
06Can different monitors post to different channels — or servers?+
07What stops #alerts becoming noise?+
#alerts should always mean something.08Is Uptimia just an uptime pinger?+
09What happens if nobody reacts to the ping?+
10Is Discord support a paid add-on?+
Your next outage posts to #alerts
Point Uptimia at your channel, send one test message, and after that bad news always knows where to find you.