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.
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 who gets notified, and after how long it escalates to the next person 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.
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.