Uptime Kuma: Self-hosted monitoring and status pages
Node.js application monitoring HTTP, TCP, DNS, and ping endpoints.
Learn more about uptime-kuma
Uptime Kuma is a self-hosted monitoring tool built on Node.js that tracks service availability across multiple network protocols including HTTP, TCP, DNS, and ICMP ping. The application establishes real-time bidirectional communication between its server component and browser clients using Socket.IO, while the frontend is constructed as a Vue.js single-page application that receives live monitoring updates. Monitoring data, configuration settings, and historical uptime metrics are persisted in a local SQLite database, enabling stateful tracking of service health over time. The architecture supports flexible deployment through Docker containerization or direct Node.js execution on traditional server infrastructure. This design prioritizes ease of self-hosting and minimal external dependencies, making it suitable for internal network monitoring and generating public-facing status pages without relying on third-party monitoring services.
Multi-Protocol Monitoring
Monitors HTTP(s), TCP, ping, DNS, Docker containers, and Steam servers through a single application. Eliminates the need for multiple specialized monitoring tools across diverse infrastructure components.
90+ Notification Integrations
Built-in support for Telegram, Discord, Slack, email, and 85+ other services without external dependencies. Notifications trigger automatically on status changes with no additional integration configuration required.
Self-Contained Deployment
Runs as a standalone Node.js application with local SQLite storage and no external service dependencies. Operates in air-gapped or isolated network environments without cloud connectivity requirements.
import io from 'socket.io-client';
const socket = io('http://localhost:3001');
socket.on('monitorList', (monitors) => {
monitors.forEach(monitor => {
console.log(`${monitor.name}: ${monitor.active ? 'UP' : 'DOWN'}`);
console.log(`Uptime: ${monitor.uptime}%`);
});
});
socket.emit('login', { username: 'admin', password: 'password' });Patch release fixing a migration false positive for Google Chrome monitoring and updating security documentation.
- –Fixes false positive detection of Google Chrome during database migration that could block upgrades.
- –Updates SECURITY.md with revised supported version policy and Docker tag guidance; no functional changes.
Fixes a critical bug where healthchecks could terminate Uptime Kuma mid-migration.
- –Upgrade to prevent unexpected shutdowns during database migrations triggered by healthcheck probes.
- –Release notes do not specify if manual intervention is required for systems that experienced this issue.
Major version with breaking changes; backup before upgrading and follow the migration guide to handle schema changes.
- –Read the migration guide at the wiki; schema changes include `monitor.ip_family` now string and `ping` column defaults to 0.
- –Replace proxy-agent dependency to fix vm2 vulnerability (GHSA-vffh-c9pq-4crh) and review beta changelogs for additional breaking changes.
See how people are using uptime-kuma
Top in Developer Tools
Related Repositories
Discover similar tools and frameworks used by developers
cadvisor
Daemon for monitoring container resource usage and metrics.
git
Snapshot-based version control with distributed repository architecture.
pygame
Python wrapper for SDL enabling 2D game development.
awesome-css-frameworks
Categorized catalog of CSS frameworks with GitHub metrics.
redoc
React component rendering OpenAPI specifications as interactive HTML documentation.