1. Open the vendors page
In the dashboard, go to Monitoring and find the Vendors section. Growth and Scale accounts can add services from the Outages catalog; the free tier sees an upgrade plate rather than a truncated list, because the watchlist is a paid feature.
2. Add the services you depend on
Search the catalog and add each vendor you rely on. Growth watches up to 10, Scale up to 50. Each tile shows RealUptime's own live probe reading for that vendor and, when we have one, the vendor's own status-page claim shown separately and never merged into our reading.
3. Pick where the alert goes
Alerts route through your account's normal alert rule: email, Slack, a registered webhook endpoint, or the notification channel registry (Discord, Teams, Opsgenie, Zapier). No separate setup — the same channels that page you for your own monitors carry vendor alerts.
4. Know what triggers an alert
Only a probe-confirmed measured event: when our own probes open, reopen, or close an outage on a watched service, from named regions, at a named time. A user report, a social-media spike, or the vendor's own status-page claim never opens an alert on its own — that is exactly the never-falsify rule the rest of RealUptime Outages holds to.
Go deeper
The full reference lives in the docs: Monitor documentation. Error codes named above are each explained in the error-code reference.