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 check you add.
Slack
Create an incoming webhook in Slack, paste its URL into the Slack alerts field, and every region flipping down or recovering posts to that channel.
Webhooks
Add any number of plain HTTP webhook endpoints. Each receives a POST with the check, 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 region goes down and resolves it automatically on recovery, no manual close needed.
Alert routing
By default every check alerts every channel above. From RealUptime Monitor's settings, create a rule to send only some checks to only some channels, or to mute a set of checks 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 Growth and Scale, 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 check 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. There is no native phone call or SMS 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.