Uptimepage

Uptimepage combines uptime monitoring, on-call scheduling, and public status pages in one hosted service. When a check fails, it alerts the right person, tracks the incident, and lets customers follow along on a branded status page. You run the fix; it runs the monitoring stack.

Eight monitor types cover the common failure modes most teams discover the hard way:

• HTTP/HTTPS checks status codes, headers, and body text from every region you pick
• TCP dials a port directly, useful for databases, mail servers, and anything without an HTTP endpoint
• DNS validates that a lookup returns the answer you expect, not just that a resolver responds
• ICMP ping confirms a host is reachable at the network layer
• Heartbeat inverts the model: your cron job calls in, and silence is the alert
• TLS certificate reads the expiry off every handshake and pages you while there's still time to renew
• Domain expiry checks the registry directly so a missed invoice doesn't take the domain down
• Browser login flow runs a real browser through your sign-in steps and charts how long each one takes, catching a broken OAuth secret that a 200 response would hide

Alerts reach Slack, Discord, Teams, PagerDuty, email, SMS, Telegram, WhatsApp, ntfy, Gotify, or any HTTPS webhook. Failure thresholds filter brief interruptions before anything gets paged.

On-call is built in. Schedules rotate people daily, weekly, or on a custom length, with overrides for holidays and swaps, and each person can subscribe to their shifts as a calendar feed. Escalation policies page channels and schedules level by level until someone acknowledges, and a policy can be bound to one monitor or set as the organization default.

Status pages publish live incidents and scheduled maintenance windows with your logo and colors. Customers can review uptime history without signing in. Maintenance windows silence the alert engine so planned work doesn't generate false pages.

For teams managing client work, a shareable monitor link gives a client or vendor a live view of one monitor's uptime, latency, and incidents, with credentials redacted and no access to anything else. Monitors and incidents export as JSON; public incidents are available over RSS. The REST API, Terraform provider, and an MCP server make the whole setup manageable as code.

The source is public under AGPL, so you can verify how it works or self-host if your requirements change. The API and Terraform provider are identical either way. Teams looking at Uptime Kuma, OpenStatus, or Healthchecks will find Uptimepage covers more of the on-call and status-page side without needing a separate tool for each.