The account owner and every teammate with notification permission receive an email the moment a region flips down or recovers. No setup required: it works from the first monitor you add.
Slack
Press Connect Slack under Alert channels, pick a channel on Slack's own screen, and every confirmed outage and its recovery posts to that channel. Pasting an incoming webhook URL works too. Send test posts a test message right away.
Webhooks
Add plain HTTP webhook endpoints, up to 5 on Free, 25 on Pro and 150 on Business. Each receives a POST with the monitor, the new state, and a timestamp whenever a monitor changes state, so you can wire status changes into whatever else you already run. Every delivery is signed, and for a deprecation window carries both a legacy signature and a newer, timestamped one that a receiver can use to reject a replayed request. See the API reference's "Verifying the signature" section for both header shapes, the tolerance, and a worked example.
PagerDuty
Paste your Events API v2 integration key from a PagerDuty service. RealUptime opens a PagerDuty incident when a monitor is confirmed down and resolves it automatically on recovery, no manual close needed. Step by step: RealUptime + PagerDuty.
Confirmed by most regions
On a monitor that runs from more than one region, nothing fires and no incident opens until most of the regions that ran in the last 10 minutes are failing and none of them is up on its latest run. With four regions that means three. A monitor with one region alerts as soon as that region is down. A region the site refuses (HTTP 401, 403 or 429, a Cloudflare 1020 or a challenge page) is never counted as down: your dashboard shows it as blocked from that region. Details: how a monitor is called down.
Alert routing
By default every monitor alerts every channel above. From RealUptime Monitoring's settings, create a rule to send only some monitors to only some channels, or to mute a set of monitors entirely, like a staging environment nobody needs paged for. Alert routing decides which of the channels above fire; it does not change on-call escalation below, which keeps paging whoever its own policy names regardless of what is routed here.
On-call and escalation
On Pro and Business, build escalation policies: an ordered list of steps, and after how long each one escalates to the next if nobody acknowledges. Assign a policy to a monitor so its alerts follow that chain instead of going to everyone at once. See pricing for what each plan includes.
Each step pages one of three things. A person (or whoever is on call in a rotation attached to the step) is emailed, plus paged through any of the account's notification channels they chose under "How to page me" on their profile. A notification channelfrom your registry (Discord, Microsoft Teams, Opsgenie, incident.io, FireHydrant, or a generic JSON webhook) is delivered in that channel's own format. A built-in channel is the account's Slack webhook, its PagerDuty integration, or every enabled webhook endpoint. Opsgenie and PagerDuty pages open their own alert under an escalation key; acknowledging the incident in RealUptime does not close it there. A Discord, Teams or Slack post does not wake anybody unless that app's own notifications do. SMS alerts are included from Pro; there is no native phone-call paging.
Server-health alerts
The Monitor agent's own server-health alerts, disk almost full and out of memory, flow through the same email, Slack, webhook, and PagerDuty channels above. See server health for exactly what triggers one.