UptimeRobot

UptimeRobot is uptime monitoring for websites, APIs and cron jobs, with checks from 5 minutes down to 15 seconds and a free tier that runs 50 monitors.

UptimeRobot is uptime monitoring software that checks websites, APIs, ports and scheduled jobs from outside a network and raises an alert when one of them stops answering. It exists for the case where a customer notices an outage before the team does. The product is built and run by UptimeRobot s. r. o. in Bratislava, Slovakia, and it is part of the itrinity portfolio alongside Mangools, EmailListVerify and Warmup Inbox. Monitoring covers HTTPS checks, keyword monitoring for a string that must appear or stay absent in the page body, ICMP ping, TCP port monitoring and DNS monitoring, plus SSL certificate and domain expiry alerts that fire days before a renewal is due. Cron job monitoring waits for a heartbeat from a scheduled job and speaks up when the ping goes silent. Checks run from several locations and a failure is re-tested from another region before anyone is woken. Alerts go out by email, SMS, voice call and Email2SMS, and into Slack, Microsoft Teams, Discord, PagerDuty, Zapier or any webhook. Response time monitoring plots every check per monitor, maintenance windows pause alerting for planned work, and status pages publish monitor state on a customer's own domain. The product suits freelancers looking after a set of client sites, developers who need proof that a nightly job ran, and small teams running production web apps who share an on-call rota. Check interval, monitor count, status pages and data retention are what separate the tiers, so the choice follows how quickly a team needs to hear about an outage. It watches services from the outside with no agent to install, so it sits beside the tools that read metrics from inside a server rather than replacing them. One account subscription, paid monthly or annually, covers the monitors, and login seats are added on top. In daily use it is the outside check on anything with an address: marketing sites, checkout flows, API endpoints, mail and database ports, and backup or billing jobs that ping when they finish. Agencies give each client a status page so support requests drop while an incident is visible. Alerts land in the chat channel a team already reads and route on to PagerDuty for a rota, while webhooks and Zapier pass an incident into a ticketing or logging system. The API creates, edits and pauses monitors, so a new endpoint can be added to the checks by the same script that deploys it.