Uptimepage

Overview

Uptimepage watches the services you care about and tells you when they go down, instead of paying a monitoring SaaS to do it or trusting one to watch its own host. It checks websites, servers, certificates and domains on a schedule, records the history, and publishes a status page you can share with whoever depends on those services.

Features

• Checks over HTTP, TCP and DNS, plus TLS certificate and domain expiry
• Response time broken down into DNS, connect, TLS and first byte, kept as history
• Alerts to Slack, Discord, Telegram, ntfy, Pushover, PagerDuty, webhooks and email
• A public status page with incident history, uptime and latency charts
• Incidents you can narrate as they unfold, so readers see what is happening
• A full REST API and a Terraform provider, so monitors can be managed as code

Setting up

The first owner account is created for you on first boot. Open the app's logs from its page in malmo and look for the block that begins "Owner account ready"; it contains a single-use sign-in link. The link expires 15 minutes after it is printed, so if it has gone stale, restart the app and a fresh one is printed. That same block also carries a full-access API token for the REST API and the Terraform provider.

Good to know

Sign-in is by that link only unless you configure more. GitHub and Google sign-in are left switched off on purpose: uptimepage has no way to restrict who may register, so turning either on would let any GitHub or Google account create its own workspace on your instance. Fill in the credentials below only if you want that.

Invitation and sign-in emails need a Resend account. Without one they are written to the app's log rather than sent, which is why the first sign-in link above is read from the log. Outage alerts are separate and do go out over normal email once an administrator binds a mail provider in malmo.

This release carries limits from uptimepage's hosted service, and a self-hosted workspace lands on the free tier of those: up to 20 monitors, a minimum check interval of 60 seconds, 3 members, and one status page. Custom domains, white labelling and SMS alerts are off. Nothing here reads a licence or phones home, so the caps are the app's own defaults rather than anything malmo adds.

Browser flow checks, which drive a real browser through a login or a checkout, are not available: they need a build of uptimepage that ships a browser engine, and the published image does not.

Monitoring targets on your own network is switched off, so this watches services reachable over the internet. It keeps every check result it has ever taken, and runs its own analytics database to do it, so it is heavier than most apps here: give it around four gigabytes of memory to be comfortable.