---
title: "Use Uptime Kuma on another provider for · Agent Wranglers"
url: https://agentwranglers.se/playbook/stack/operations-tools/uptime-kuma
id: STK-68
level: Recommended
updated: 2026-10-22
tokens: 767
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Use Uptime Kuma on another provider for uptime checks

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Operations tools](https://agentwranglers.se/playbook/stack/operations-tools.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-22.

- ID: STK-68
- Level: Recommended
- Chapter: [Operations tools](https://agentwranglers.se/playbook/stack/operations-tools.md)
- Rule: Check your public addresses from outside with Uptime Kuma, run at a different provider from the app.
- Check: The monitor runs at a different provider from the app. Stopping the app in a test makes a page arrive within 5 minutes.
- Cost: Open source. MIT licence, free to run. The small server at a second provider is paid.
- How: 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](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/health-check-and-rollback.md). Choose something else when nobody will run a second server, and use a managed monitor with checks from 3 or more regions.

## Examples

**Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

### YAML example

```yaml
# 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

```sh
# 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
```

## Sources

- [Uptime Kuma](https://github.com/louislam/uptime-kuma)

## Related rules

- ENG-9 [Give the server a health check](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/health-check-and-rollback.md) in Engineering

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/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.

- Previous: [Use Sentry only for features GlitchTip lacks](https://agentwranglers.se/playbook/stack/operations-tools/sentry.md)
- Next: [Use PagerDuty for paging and keep schedules as code](https://agentwranglers.se/playbook/stack/operations-tools/pagerduty.md)
- [Operations tools](https://agentwranglers.se/playbook/stack/operations-tools.md)