Skip to content

Discord downtime alerts that reach you first.

Uptimia checks your sites from 171+ locations and posts every confirmed failure into a Discord channel through a webhook — nothing joins your member list. The recovery post closes the loop in the same channel.

Outages ignore your working hours

A server dies at 02:07 on a Saturday. Nobody is watching a dashboard, the inbox is asleep, and the only app still making a sound on anyone’s phone is Discord.

The plan

I’ll see it from my desk

Site down
2:07 · Saturday
hours pass
You, asleep
phone on the nightstand

A web server has no way to tell you it stopped answering. Whatever breaks outside working hours stays broken until working hours.

How it usually ends

The community finds out for you

Site down
2:07 · silent
by breakfast
“uhh… is the site dead?”
#general · 8:30

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.

The fix is making the outage report itself, into the app already on your phone. Here is the same 02:07 failure with a webhook in the channel.

An outage handled from bed

At 02:07 the store stopped answering with an HTTP 502. The dashboard still showed a green fleet average, the status page still said operational, and nobody was awake to look at either.

2:07 Store — playforge.gg stops answeringThe 502 is repeated by 3 backup probes before the post goes to #alerts #alerts
2:09 Maya taps the acknowledge linkThe link in the post is signed — no login — and it freezes the escalation ladder #alerts
2:12 Two of them hop into voiceFaster than typing at 02:12 — culprit: a full disk on the app box #alerts
2:31 Recovery posts itself to #alertsGreen embed, same channel, carrying the total time down — back to sleep #alerts
24 mindown → up
Handled without opening a laptop0 logins
Notification, acknowledge link, a voice huddle, all-clear — the whole incident lived in one channel. The dashboard could wait until morning.
3 probes agreedacknowledged in 2 mindown 24 min1 voice call
Nobody else’s phone made a sound. The acknowledgement at step one froze the pending steps, so the SMS to the second name never fired. ladder stopped

Wired up in three steps

A webhook, a routing decision, a safety net. No bot invite, no roles to grant, no OAuth screen.

Step 11 min

Create the channel webhook

In Discord, open the channel’s settings → Integrations → Webhooks → New Webhook. Paste the URL into Uptimia and press Send test — you watch the embed land before anything real depends on it.

#alerts Send test
test ping landed in #alerts · wiring proven
Step 21 min

Tell each monitor where to shout

Each webhook is an alert contact, and each monitor picks its contacts. The store and the API post to #alerts, certificate and domain warnings to #warnings, the speed feed somewhere nobody gets notified.

Alert this monitor to
#alerts#warningsEmail
Store — playforge.gg → posts to #alerts
Step 3optional

Decide what happens if nobody taps

Put the monitor on an escalation policy and the post carries an acknowledge link. Ignored, the ladder climbs on your timings — SMS to the on-call, then the next name. Quiet hours are set per recipient. Escalation policies come with the Professional plan and above; the webhook itself works on every plan.

If nobody acknowledges — escalate
#alerts → +5 min SMS on-call → +15 min #mods-urgent
quiet hours per person · maintenance muted
Technical setup guide

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.

  • Create a Discord webhook
  • Add the Discord integration
  • Test the integration
  • Assign it to your monitors
Open the setup guide help.uptimia.com

What else pings your channel

A green homepage hides a certificate expiring, a cron job that stopped on Tuesday, a checkout that 500s on the last step. Twelve monitor types can post to one webhook — here are eight of them, and what each one notices.

Uptime checksEvery route, not just /
SSL certificatesExpiry pinged before it lapses
Domain expiryRegistrar dates, watched
Server metricsCPU, disk and RAM below deck
1 Discord channel #alerts — one webhook, one door
Heartbeats & cronBackups that stop without a word
TransactionsSignup and checkout, replayed
Virus & malwareMalware caught before users see it
Page speedSlow pages, caught drifting
Whichever layer gives way first, the post looks the same — same channel, same embed, same recovery message when it clears. 12 types · 1 webhook

One channel per kind of news

A channel gets muted when it mixes a 502 with a speed report. Create a webhook per channel, point each monitor at the one it belongs in, and let Discord’s per-channel notification settings do the rest.

#alerts
The one room allowed to ping everyone.
Uptime & HTTP checks
Checkout & transactions
Server metrics & heartbeats
urgent · notifications on
#warnings
Read with coffee, fixed this week.
SSL certificate expiry
Domain expiry
Virus & malware flags
important · no push
#perf-watch
Numbers for the next standup argument.
Page speed & Core Web Vitals
Uptime on marketing pages
Campaign landing pages
fyi · scoreboard only
Half the team lives elsewhere? The same alert also goes to MS TeamsSlackTelegramPagerDutyWebhooksEmail & SMS

Bad news travels fastest in Discord.Let it outrun your customers.

Every monitor type and every alert channel — free for 30 days.

Start your free 30-day trial
30 days free no credit card cancel anytime

What sits behind the webhook

Uptimia accepts webhook URLs on discord.com and discordapp.com only, pins the address it resolved so the post cannot be redirected elsewhere, and never follows a redirect. Behind that one door sits the platform that finds the problems and proves your uptime.

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.

Store — playforge.ggUPTIME · 99.98% Signup flowTRANSACTION · OK playforge.ggSSL · 61 DAYS

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.

171+ checkpoints · 70+ countries

A status page for the community

Publish status on your own domain and watch the “is it down?” DMs dry up.

 status.playforge.gg · live

Monthly uptime PDFs

Numbers for the client, the sponsor or the retro — generated and emailed on schedule.

June · 99.98% · PDF sent

Time to acknowledge, recorded

Every acknowledgement is stamped against the incident, so “we got faster at this” is a number, not a feeling.

avg. response · 2 min

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.

Step 1 — #alertsDISCORD Step 2 — on-callSMS · +5 MIN Quiet — per personMUTED

How Discord downtime alerts work

Uptimia runs uptime, SSL, speed, transaction and server checks from 171+ locations and posts every alert to Discord through a channel webhook. The message arrives as an embed: a colour-coded heading, the monitor name, what state it is in and since when, plus its type and priority. Recoveries post to the same channel with the total time down. Monitors on an escalation policy (Professional plan and above) also carry a signed acknowledge link, and the ladder climbs to SMS or another channel until someone taps it.

“Email alerts were enough”

Email doesn’t buzz your pocket

Site down
2:07 · confirmed
seen at 9 a.m.
alerts@ inbox
unread · 7 h

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.

A Discord ping

The push finds whoever’s awake

Site down
2:07 · confirmed
seconds
#alerts
push on every phone

Discord handles the last mile: its per-channel notification settings decide whose phone lights up, and whoever stirs first taps the acknowledge link.

Every event

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
MessagePosts whenWhat it carries
Down alertBackup probes repeat the failureMonitor and state, plus the acknowledgement link on an escalation policy
Escalation stepThe post goes unansweredThe next channel or an SMS, then the next person
Group digestMonitors on one policy fall togetherOne post for the storm, not one per monitor
Join updateMore monitors join that groupA throttled follow-up naming the newcomers
RecoveryThe check goes green againThe all-clear, with total time down
Test messageYou press Send testProof it lands, before anything is at stake

Discord alerts FAQ

01How do I get downtime alerts in Discord?+
Create a webhook on the channel you want (channel settings → Integrations → Webhooks), paste its URL into Uptimia as an integration, and press Send test. Uptimia creates a matching alert contact, and any monitor you assign it to — uptime, SSL, checkout, server — posts there from then on.
02Do I have to invite a bot?+
No. A webhook is not a bot: nothing joins your member list, there are no roles to grant, and it cannot read messages. It has one ability — posting into the channel it belongs to. Uptimia only accepts URLs on 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.?+
Only if you choose to. Discord’s per-channel notification settings decide who gets the push; Uptimia’s quiet hours and routing decide what’s allowed to fire at night. Most teams let #alerts ping and keep everything else silent.
04Can alerts go to a private channel?+
Yes — webhooks work on any channel you can edit, private ones included. Only the people in that channel see the alerts.
05What does a ping look like?+
An embed posted by “Uptimia”: a colour-coded heading — red for down, amber for trouble, green for recovered — then a line naming the monitor, its state and the time it started, with Type and Priority beside it. Recoveries carry the total time down. On an escalation policy (Professional plan and above) the embed also carries the incident number and an Acknowledge incident link.
06Can different monitors post to different channels — or servers?+
Yes. Each webhook is its own destination and each monitor picks one, so outages, warnings and speed stats can live in different channels — even in different servers.
07What stops #alerts becoming noise?+
Three things: a failure is repeated by up to 3 backup probes before anything is posted, monitors that share an escalation policy and fall together are merged into one group with one digest, and maintenance windows mute planned work. A post in #alerts should always mean something.
08Is Uptimia just an uptime pinger?+
No — uptime is one of twelve monitor types. Uptimia also replays checkouts in a real browser, runs multi-step API checks, watches SSL, domain and DNS records, checks page speed, malware and blacklists, reads real-user timings, and takes heartbeats from your cron jobs and servers.
09What happens if nobody reacts to the ping?+
Put the monitor on an escalation policy — Professional plan and above — and the ladder climbs: after a delay you set, Uptimia texts the on-call phone, then the next person. Tapping the acknowledge link freezes the pending steps at any point.
10Is Discord support a paid add-on?+
No — it is one of 12 built-in alert channels, available on every plan and during the 30-day free trial. No credit card needed to try it.

Your next outage posts to #alerts

Create the webhook, paste the URL, press Send test. After that, bad news knows which channel to find you in.

No bot to invite Test ping proves the wiring 30-day free trial No credit card
Discord is one of 12 alert channels built into Uptimia — every monitor type can post to it.