Upptime

A small engineering team managing public microservices needs external uptime monitoring without provisioning extra virtual machines or paying per-endpoint SaaS subscriptions. Upptime turns a standard GitHub repository into an automated synthetic monitor and status website. Scheduled GitHub Actions workflows execute HTTP probes, record latency directly into Git history, and open incident tickets via GitHub Issues.

Why Upptime instead of Uptime Robot

Uptime Robot tracks availability through synthetic probes on a managed dashboard. While its free tier offers fifty monitors at five-minute intervals, configuration lives in a closed web console, metrics expire without paid plans, and status pages carry vendor branding. Upptime moves monitor configuration into Git. Endpoints, headers, and alerting rules reside in .upptimerc.yml under pull request review. Latency metrics and uptime logs commit directly to repository branches, preserving operational history and publishing a customized Svelte status portal on GitHub Pages without subscription fees.

The trade-off centers on runner infrastructure and scheduling control. Uptime Robot runs dedicated daemons across global regions, providing deterministic minute-level checks and multi-region quorum that filters out transient routing blips. Upptime relies on GitHub Actions cron runners on a best-effort queue where platform congestion can delay scheduled runs by several minutes. Because probes originate from Microsoft Azure runner IPs, edge firewalls occasionally challenge requests, triggering false alerts. If GitHub suffers an outage, monitoring halts and the status page goes dark simultaneously.

What it does well

• GitOps configuration: Declares endpoints, HTTP methods, expected status codes, headers, and check rates within a single YAML file tracked in Git.
• Automated incident issues: Opens a GitHub issue with failure diagnostics when an endpoint fails, assigning team members and closing the ticket upon recovery.
• Zero server maintenance: Operates entirely on GitHub Actions cron runners and GitHub Pages hosting, eliminating monitoring virtual machines.
• Serverless status portal: Builds and deploys a fast Svelte status site that pulls uptime metrics and incident logs directly from repository history.
• Version-controlled metrics: Commits response times and uptime records directly into Git, maintaining an audit trail without an external database.