How the pieces fit together
The feature pages above describe one loop: check, confirm, alert, tell your users, then learn from what happened. Each stage feeds the next, which is why they live in one product.
- CheckA monitor is a scheduled check from one or more probe regions. Every plan includes HTTP/HTTPS, API (assertions), Keyword, Ping, TCP port, UDP port, Cron/heartbeat, DNS record, MCP server monitors, and SSL certificate and domain expiry reminders can be switched on for any HTTP or API monitor.
- ConfirmA failed check is retried once from the same region about two seconds later. On plans with more than one region, the monitor goes down only when enough regions agree, so one bad network path does not page anyone.
- AlertA confirmed incident sends one alert thread, with the failure reason and the confirming regions, through any of 14 alert channels, then a recovery notice. Escalation policies on Growth and Pro pass it on if nobody responds.
- Tell your usersStatus pages show the live state of the monitors you choose, daily uptime bars built from real check results, and the incident updates you post.
- LearnOn Growth and Pro, reliability insights match deploys to incidents, track SLO error budgets, suppress alerts from monitors downstream of a failure, and send weekly reports.
If you are new to SutramX, read uptime monitoring and multi-region probes first, because they explain when an alert fires; then alerting for where it goes. The full decision process is described in how we check.
For the practice behind the features, the uptime monitoring guides cover check intervals, false alerts and incident response, and the free reliability tools put numbers on SLAs and downtime. To see which monitors suit your product, read the use cases for SaaS, e-commerce and developers; to weigh SutramX against UptimeRobot, Pingdom or Better Stack, see how SutramX compares and the guide to uptime monitoring services compared.