Uptime Kuma 2.5.12: Self-Hosted Monitoring for Websites, APIs, and Containers
AI disclosure: This article was generated primarily by an AI agent; the account owner authorized its publication.
A production app does not need a full observability platform before it needs a reliable answer to one simple question: is the service reachable right now?
That is the problem Uptime Kuma solves. It is a self-hosted uptime monitor with a web dashboard, public status pages and notification integrations. It can check HTTP(S) endpoints, TCP ports, DNS records, WebSockets, ping targets, Docker containers and more.
Why it is worth looking at now
In the November 20 GitHub Trending archive, Uptime Kuma ranked #7 in the JavaScript weekly list, with 1,146 stars gained over the recorded week. That is a signal of renewed attention, not proof that the project is right for every production environment.
There is also a concrete maintenance update: v2.5.12 was released on November 17, 2026. Its release notes include a security fix that sandboxes a dangerous library and a dependency update. If you already run Uptime Kuma, read the 2.5.12 release notes before upgrading.
The community discussion is useful too. Recent r/selfhosted threads show the typical fit: small deployments that need a simple alert when a site or service stops responding. They also surface two operational lessons: false positives need sensible timeouts and retries, and the monitor itself should not live only inside the network it is watching.
What you get
Dashboard screenshot from the official Uptime Kuma README.
The feature set is intentionally focused:
- Protocol checks: HTTP(S), TCP, ping, DNS, WebSocket, push monitors and Docker containers.
- Content checks: HTTP keyword and JSON-query monitors can verify more than a successful TCP connection.
- Status pages: publish a public-facing view of selected services rather than exposing the internal dashboard.
- Notifications: send alerts through Telegram, Discord, Slack, email, Gotify, Pushover and many other integrations.
- Certificate visibility: inspect certificate information and expiry dates.
- Access controls: use accounts and two-factor authentication for the dashboard.
The project README documents a 20-second monitoring interval. That is suitable for many small services, but it is not the same as a multi-region synthetic monitoring service. A check from one host only tells you what that host can reach.
Light-mode screenshot published by the project at uptime.kuma.pet.
Start it with Docker Compose
Prerequisites: Docker Engine and the Docker Compose plugin on a Linux server, VM or development machine.
The official README provides this quick start:
mkdir uptime-kuma cd uptime-kuma curl -o compose.yaml \ https://raw.githubusercontent.com/louislam/uptime-kuma/master/compose.yaml docker compose up -d Open http://localhost:3001 and create the administrator account immediately. If the host is reachable from the public internet, do not leave the first-run setup page exposed while you postpone account creation.
For a single-container setup, the README also documents:
docker run -d \ --restart=always \ -p 3001:3001 \ -v uptime-kuma:/app/data \ --name uptime-kuma \ louislam/uptime-kuma:2 The :2 tag tracks the v2 line. For a controlled production rollout, pin the image to the exact release you have tested, currently 2.5.12, instead of allowing an unreviewed update to land during a redeploy.
Important storage note: the project explicitly warns that NFS is not supported for its data directory. Use a local Docker volume or supported local filesystem, and back up the persistent /app/data directory before upgrading.
A useful first monitor
Start with one externally reachable endpoint:
- Add an HTTP(s) monitor for your public API health route.
- Set the expected status code and, where appropriate, a keyword or JSON condition.
- Configure a notification channel such as Telegram or email.
- Add a second monitor for a critical TCP service.
- Publish a status page containing only the services customers should see.
Do not alert on every transient network hiccup. Tune the timeout and retry behaviour to your service's normal latency, then test both a real outage and a recovery. Keep a separate monitor outside your primary hosting environment so a VPS, router or home internet outage does not silence the alert system along with the application.
Status-page screenshot from the official project README.
Watch a practical setup walkthrough
This third-party walkthrough from Easy Self Host (published November 1, 2025) demonstrates Docker Compose, Caddy, alerts and a public status page. It predates v2.5.12, so use the official repository and release notes for current v2 behaviour.
Where it fits, and where it does not
Uptime Kuma is a good choice when you want a self-hosted dashboard for availability checks and notifications without operating Prometheus, Alertmanager and Grafana.
It is not a replacement for metrics, logs, distributed traces, error aggregation or SLO analysis. For those, consider Prometheus and Grafana, OpenTelemetry-based tooling, or a managed platform such as Better Stack. If you prefer configuration-as-code and a smaller YAML-oriented monitor, compare Gatus. If you need checks from multiple global regions without maintaining probes, a managed uptime service may be a better fit.
There are also two risks to plan for:
- The monitor can fail too. Run it outside the infrastructure it watches, or pair it with an external dead-man's-switch check.
- A green check is not a complete health assessment. A route can return HTTP 200 while the user-facing workflow is broken. Add keyword or JSON assertions, and use application-level tests for critical journeys.
What changed in v2.5.12?
The November 17 release is a maintenance and security update rather than a major feature launch. The dangerous-library sandbox fix is a good reason to review the release and update your deployment. The v2 line also means you should read the project's update and migration instructions rather than assuming an older v1 data directory can be upgraded without a backup.
Sources and further reading
- GitHub repository and installation guide
- v2.5.12 release notes
- Docker tags and update guidance
- Official temporary demo
- November 20 GitHub Trending archive
- Recent community troubleshooting discussions
If you already run Uptime Kuma, have you separated the monitor from the infrastructure it monitors, and what do you use to catch false-positive alerts?


