# Node monitoring tool

**URL:** <https://forum.storj.io/t/node-monitoring-tool/32982>\
**Category:** Node Operators\
**Tags:** uptime, monitoring\
**Created:** [October 27, 2026, 3:28pm UTC](https://forum.storj.io/t/node-monitoring-tool/32982 "2026-10-27T15:28:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pmateu](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pmateu/32/7816_2.png) [@pmateu](https://forum.storj.io/u/pmateu)\
**Post date:** [October 27, 2026, 3:28pm UTC](https://forum.storj.io/t/node-monitoring-tool/32982/1 "2026-10-27T15:28:09Z")

</div>

Hi everyone! I’m the developer of [Uptime Monitor](https://uptime-monitor.kwart.es), a monitoring tool that might be useful for the external checks discussed in this thread.

It supports HTTP and TCP monitoring, uptime history, and notifications through channels including email and Telegram.

For the approach described here, you can configure an HTTP monitor using your node’s public address and port. A TCP monitor can also check port reachability, although an open port alone doesn’t mean the node is healthy.

I’d be interested in feedback from Storj node operators, especially on what you find most useful when monitoring multiple nodes. Happy to answer questions!

---

<div class="post-metadata">

**Author:** ![lyoth](https://storj.bcdn.literatehosting.com/letter_avatar/lyoth/32/6_449c533f586939b6e5f246632a46421f.png) [@lyoth](https://forum.storj.io/u/lyoth)\
**Post date:** [October 27, 2026, 4:45pm UTC](https://forum.storj.io/t/node-monitoring-tool/32982/2 "2026-10-27T16:45:31Z")

</div>

I use [Prometheus Storj-Exporter](https://forum.storj.io/t/prometheus-storj-exporter/1939) for more than 6 years and it works perfectly for me, also has metrics on each of my nodes.  
Alerts on pretty much everything, and grafana offer a free cloud instance with 30 days retention.  
And you can set so that alerts are more smart, say alert if no ingress or egress for x amount of minutes.  
Adding more node is a single line in the prometheus config.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 27, 2026, 9:17pm UTC](https://forum.storj.io/t/node-monitoring-tool/32982/3 "2026-10-27T21:17:45Z")

</div>

How is it different from UptimeRobot, Uptime Kuma, and why do we need yet another tool like this? What problem does it solve? What is the competitive advantage? Why does it copy Kuma’s visual design under a layer of AI slop? What is going on here?

Why are you advertising it as “node monitoring tool” when it’s just a generic port monitor?

---

<div class="post-metadata">

**Author:** ![pmateu](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pmateu/32/7816_2.png) [@pmateu](https://forum.storj.io/u/pmateu)\
**Post date:** [October 28, 2026, 7:32am UTC](https://forum.storj.io/t/node-monitoring-tool/32982/4 "2026-10-28T07:32:52Z")

</div>

Asking what it offers is fair, but it isn’t “just a port monitor.”

It’s free, with no limit on the number of monitors, and you don’t need to run your own monitoring server. It includes native Telegram alerts and machine scripts for Linux and Windows to monitor disk usage, CPU temperatures where available, and other host metrics, with configurable threshold alerts. You can’t do that in Uptime Robot, as far as I know.

I use it for my own Storj setup. It’s a general-purpose tool, not a Storj-specific exporter, and my original post clearly states that an open port doesn’t guarantee a healthy node.

Nobody needs to replace a setup they’re happy with. I’m sharing something I built and use. Concrete feedback is welcome; calling it “AI slop” isn’t useful feedback.

---

<div class="post-metadata">

**Author:** ![MarviBiene](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/marvibiene/32/1124_2.png) [@MarviBiene](https://forum.storj.io/u/MarviBiene)\
**Post date:** [October 28, 2026, 8:14am UTC](https://forum.storj.io/t/node-monitoring-tool/32982/5 "2026-10-28T08:14:04Z")

</div>

> [@pmateu](#):
>
> It’s free, with no limit on the number of monitors, and you don’t need to run your own monitoring server. It includes native Telegram alerts and machine scripts for Linux and Windows to monitor disk usage, CPU temperatures where available, and other host metrics, with configurable threshold alerts. You can’t do that in Uptime Robot, as far as I know.

Uptime robot is good enough for storage node monitoring. It can send you notifications for free to and even can detect if your node gets unhealthy if you set up http monitoring (as I did)

And you can set up alerts too in uptime robot. If you have the app it can send push notification to you phone. (I like Pushover quite a lot). And the others sound like it needs access to the server which is in my eyes quite dangerous to give random scripts access to your hardware
