Self-Hosting Uptime Kuma: Monitor Everything

Why Monitor Uptime?

You need to know when your apps go down before your users tell you. Uptime monitoring checks your services regularly and alerts you instantly when something fails.

What Uptime Kuma Monitors

HTTP/HTTPS

Check if a URL returns a 200 status. Measure response time.

TCP Port

Check if a port is accepting connections. Good for databases, Redis, custom services.

DNS

Verify DNS records resolve correctly.

Ping

Basic ICMP ping to check server reachability.

Docker Container

Check if a container is running directly via Docker socket.

Push Monitor

Your app pushes a heartbeat to Uptime Kuma. If the heartbeat stops, alert.

And More

Steam game servers, MQTT, gRPC, MongoDB, MySQL, PostgreSQL, Redis, and others.

Setting Up

1. Deploy Uptime Kuma on TinyPod

2. Add monitors for each of your services

3. Configure notification channels

4. Create status pages for public display

Notification Channels

Uptime Kuma supports 90+ notification methods:

Status Pages

Create public status pages for your users. Show real-time status of all your services with historical uptime data. Custom domain support included.

Best Practices

Check Intervals

Avoid Alert Fatigue

Monitor from Outside

Don't run Uptime Kuma on the same server as your apps. If the server goes down, your monitoring goes down too. Use a separate server or use TinyPod's built-in monitoring alongside your own Uptime Kuma instance.

Resource Requirements

512 MB RAM is plenty. Uptime Kuma is lightweight and handles hundreds of monitors easily.