Skip to content

Self-hosted alternatives to updown.io

Updown.io is a hosted website monitoring service with HTTP, TCP and ICMP checks, SSL and domain expiry monitoring, cron job monitoring and status pages. Three listed apps do its main job and run in your own Cloudflare account.

Each answer comes from the app’s README and source code, compared with the features updown.io describes on its own site.

  • Uptime Guard dashboard for a Production project with one service down, one warning and the recent checks of each service

    Uptime monitor for websites, ports, DNS, certificates and cron jobs, with Telegram alerts and public status pages

    Deploy
    One-click
    License
    MIT
    GitHub stars
    29 stars
    Last commit
  • UptimeFlare status page reporting all systems operational, with daily uptime bars and response-time charts

    Serverless uptime monitor and status page with HTTP, TCP and keyword checks, deployed through GitHub Actions

    Deploy
    Manual
    License
    Apache-2.0
    GitHub stars
    3.9k stars
    Last commit
  • Uptimer public status page with website and server monitors, 60-day availability bars and latency of the last 60 checks

    Uptime monitor and status page with HTTP and TCP checks, incidents and webhook alerts, on Workers, Pages and D1

    Deploy
    Manual
    License
    MIT
    GitHub stars
    481 stars
    Last commit

updown.io features, app by app

FeatureUptime GuardUptimeFlareUptimer
HTTP(S) monitoring with text matchingYesYesYes
TCP and ICMP ping checksPartlyPartlyPartly
SSL certificate validity and expiry monitoringYesNoNo
Domain expiration monitoringYesNoNo
Periodic task and cron job monitoringYesNoNo
Downtime confirmed from at least two locationsPartlyPartlyPartly
Alerts by email, webhook, Slack, Teams, Telegram and SMSPartlyPartlyPartly
Hosted status pagesPartlyYesYes

Uptime monitor for websites, ports, DNS, certificates and cron jobs, with Telegram alerts and public status pages

What a updown.io user would miss
It covers ICMP ping, rechecks from another location, email/SMS alerts and a full status page only in part.
What it adds
It also has multi-step script checks, owner login that needs a password plus an authenticator code and data that stays in your Cloudflare account.
  • Yes HTTP(S) monitoring with text matching. HTTP(S) checks with an optional body keyword present or absent, or a JSON field value.
  • Partly TCP and ICMP ping checks. TCP port checks; no ICMP ping.
  • Yes SSL certificate validity and expiry monitoring. TLS certificate expiry check, warns 14 days before by default.
  • Yes Domain expiration monitoring. Domain registration expiry through RDAP, warns 30 days before by default.
  • Yes Periodic task and cron job monitoring. Heartbeat monitors with a unique /ping URL and a grace window.
  • Partly Downtime confirmed from at least two locations. A failed check is retried twice, 3 seconds apart, from the same Worker.
  • Partly Alerts by email, webhook, Slack, Teams, Telegram and SMS. Telegram and Web Push only; email, Slack and Discord are on the roadmap.
  • Partly Hosted status pages. Read-only public page per project with each monitor's status and 90-day uptime; no incident posts.

Sources:github.com/calmray-solutions/uptime-guard#readmegithub.com/calmray-solutions/uptime-guard/blob/main/worker/src/checks.ts

Serverless uptime monitor and status page with HTTP, TCP and keyword checks, deployed through GitHub Actions

What a updown.io user would miss
It has no certificate checks, domain expiry checks and cron job monitoring, and covers ICMP ping, rechecks from another location and email/SMS alerts only in part.
What it adds
It also has a password protected status page, a monitor status that can be embedded in another page and data that stays in your Cloudflare account.
  • Yes HTTP(S) monitoring with text matching. HTTP(S) checks with responseKeyword and responseForbiddenKeyword options.
  • Partly TCP and ICMP ping checks. TCP port checks; no ICMP ping.
  • No SSL certificate validity and expiry monitoring. SSL certificate checks are unchecked on the README roadmap.
  • No Domain expiration monitoring. No domain expiry checks.
  • No Periodic task and cron job monitoring. No heartbeat monitor type.
  • Partly Downtime confirmed from at least two locations. A grace period of failed checks before notifying; not rechecked from another location.
  • Partly Alerts by email, webhook, Slack, Teams, Telegram and SMS. Webhook alerts with a grace period; no built-in email or SMS.
  • Yes Hosted status pages. Status page with groups, incident history and scheduled maintenance.

Sources:github.com/lyc8503/uptimeflare#featuresgithub.com/lyc8503/UptimeFlare/blob/main/uptime.config.ts

Uptime monitor and status page with HTTP and TCP checks, incidents and webhook alerts, on Workers, Pages and D1

What a updown.io user would miss
It has no certificate checks, domain expiry checks and cron job monitoring, and covers ICMP ping, rechecks from another location and email/SMS alerts only in part.
What it adds
It also has incident timelines on the status page, signed, templated webhook messages and CSV export of uptime history.
  • Yes HTTP(S) monitoring with text matching. HTTP(S) probes with keyword assertions on the response.
  • Partly TCP and ICMP ping checks. TCP port checks; no ICMP ping.
  • No SSL certificate validity and expiry monitoring. No certificate checks.
  • No Domain expiration monitoring. No domain expiry checks.
  • No Periodic task and cron job monitoring. No heartbeat monitor type.
  • Partly Downtime confirmed from at least two locations. Failure and success thresholds before a state change; not rechecked from another location.
  • Partly Alerts by email, webhook, Slack, Teams, Telegram and SMS. Webhooks to Discord, Slack, ntfy or any URL, plus a Telegram preset; no email or SMS.
  • Yes Hosted status pages. Public status page with uptime, latency charts, incidents and maintenance windows.

Sources:github.com/vriancao/uptimer#featuresgithub.com/VrianCao/Uptimer/blob/master/docs/notifications.md