Set up and manage uptime monitors and a public status page with Uptime Kuma
domain: github.com/louislam/uptime-kuma · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Deploy Uptime Kuma via Docker ('docker run -d -p 3001:3001 -v uptime-kuma:/app/data louislam/uptime-kuma:latest') or as a Node.js process, then complete first-run setup at http://localhost:3001
Create monitors through the web UI or REST-like API by POSTing to '/api/v1/monitor' (when API access is enabled) with 'type' (http, tcp, ping, keyword, dns), 'url', 'interval' in seconds, and 'name'
Configure notification channels under Settings > Notifications supporting integrations such as Slack, PagerDuty, email, Telegram, and webhooks; attach channels to monitors in the monitor edit view
Create a status page via the Status Pages section by selecting monitors to display publicly, setting a custom domain or subdomain, and publishing the page with visibility controls
Use the built-in maintenance scheduler (Maintenance menu) to create scheduled maintenance windows that suppress notifications and display a maintenance banner on the status page during planned downtime
Known gotchas
Uptime Kuma does not have a formally versioned public REST API; the internal API used by the UI can change between releases without notice — prefer the UI or official Docker upgrade paths over API automation
Monitor intervals below 20 seconds are not recommended and may be blocked or rate-limited depending on deployment; very short intervals against external services can also trigger rate limiting or IP blocks on the target
Status page custom domains require DNS CNAME configuration pointing to the Uptime Kuma host and may require a reverse proxy handling TLS termination; Uptime Kuma itself does not manage TLS certificates for custom domains
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?