Self-hosted alternatives to Hyperping

Uptime Guard

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

What a Hyperping user would miss

It has no multi-region checks and browser tests, and covers ping checks, subscribers/custom domain and email/SMS/phone alerts only in part.

What it adds

It also has owner login that needs a password plus an authenticator code and data that stays in your Cloudflare account.

• Yes HTTP(S) and API uptime monitoring with keyword checks. HTTP(S) checks with an optional body keyword present or absent, or a JSON field value.
• Partly TCP port, ICMP ping and DNS monitoring. TCP port and DNS record checks; no ICMP ping.
• Yes SSL certificate expiry tracking. TLS certificate expiry check, warns 14 days before by default.
• No Checks from 18 global regions with cross-region verification. Checks run from the Worker with no location choice.
• Yes Cron job and heartbeat monitoring. Heartbeat monitors with a unique /ping URL and a grace window.
• No Playwright browser tests for user flows. Script monitors chain HTTP requests only; no real browser.
• Partly Status pages on your own domain with email subscribers. Public page; no custom domain or subscribers.
• Partly Alerts by email, SMS, phone and chat apps with on-call escalation. Telegram and Web Push with reminders at widening gaps and a recovery message; no phone, SMS, email or on-call schedules.

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 Hyperping user would miss

It has no certificate checks, heartbeat monitoring and browser tests, and covers ping checks, multi-region checks, subscribers/custom domain and email/SMS/phone 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) and API uptime monitoring with keyword checks. HTTP(S) checks with responseKeyword and responseForbiddenKeyword options.
• Partly TCP port, ICMP ping and DNS monitoring. TCP port checks; no ICMP ping or DNS checks.
• No SSL certificate expiry tracking. SSL certificate checks are unchecked on the README roadmap.
• Partly Checks from 18 global regions with cross-region verification. A monitor can run from one chosen region through a check proxy that you set up.
• No Cron job and heartbeat monitoring. No heartbeat monitor type.
• No Playwright browser tests for user flows. No browser checks.
• Partly Status pages on your own domain with email subscribers. Own domain through a CNAME; no subscribers.
• Partly Alerts by email, SMS, phone and chat apps with on-call escalation. Webhook alerts with a grace period; no phone, SMS, email or escalation.

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