1. Open the vendors section
In the dashboard, go to Monitoring and find the Vendors section. The watchlist is a flat-rate add-on ($11.99/mo, $119.90/yr) on top of any paid Monitor plan (Growth or Scale); an account without it, on any tier including Free, sees an upgrade plate explaining the flat price rather than a truncated list.
2. Add the services you depend on
Search the catalog and add each vendor you rely on. With the add-on held, the account can watch up to 100, stated plainly as an internal fairness cap on probe capacity rather than a per-vendor charge: the price is the same flat rate whether you watch one vendor or the full cap. 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
An alert is sent when one reports an incident on its own status page, and again when it reports it resolved; for a service with no status feed we can read, when our checks of it fail from two or more distant regions, and again when they pass. The first kind is the vendor's own statement, with our regional reading beside it; the second is our own reading from outside, from named regions, at a named time, and is not the vendor's official status. A user report or a social-media spike never opens an alert on its own.
Go deeper
The full reference lives in the docs: Monitor documentation. Error codes named above are each explained in the error-code reference.