Agent Wranglers

STK-68Recommended Open source

Use Uptime Kuma on another provider for uptime checks

Check your public addresses from outside with Uptime Kuma, run at a different provider from the app.

By Agent Wranglers. Updated .

How to do it

A check inside your own network stays green when the network or the provider fails. Uptime Kuma is under MIT and reached 1.0 in July 2021. Version 2.5.6 came out on 9 October 2026. It has over 90,000 stars on GitHub and about 195 million pulls on Docker Hub. It checks HTTP, TCP, DNS and TLS expiry, and sends alerts to most chat and paging tools. Health endpoints to check are in Separate alive from ready. Choose something else when nobody will run a second server, and use a managed monitor with checks from 3 or more regions.

Examples

YAML example

# compose.yaml on a small server at a second provider
services:
  uptime-kuma:
    image: louislam/uptime-kuma:2.5.6
    restart: unless-stopped
    ports: ['3001:3001']
    volumes: ['./data:/app/data']

Shell example

# The same probe Uptime Kuma runs, for a one-off test from any machine
curl -fsS -o /dev/null -w '%{http_code} %{time_total}\n' --max-time 10 https://www.example.com/healthz

How to check

The monitor runs at a different provider from the app. Stopping the app in a test makes a page arrive within 5 minutes.

Sources

For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/stack/operations-tools/uptime-kuma">Agent Wranglers software choices playbook</a>. In code you write, add a comment next to it with the same link.