Although as it states there:

Cachet v3.x is currently in development and not yet released. The following instructions are intended for development purposes only and are subject to change.

@joseph Version 3.X is now available

Is it? Where?

It's not showing up in releases and the most recent post by the author in the 3.X announcement thread, posted on 2 Jan 2025 says:

We're working hard on v3 though and we expect something by the end of the year.

So I'm pretty sure 3.X is not available yet and it sounds like it won't be for some time.

This would make me sign up to Cloudron

If you are around, there is hope! Cachet is back and they made a new release - https://github.com/cachethq/cachet/releases/tag/v2.4.0 .

Also, discussion for 3.x at https://github.com/orgs/cachethq/discussions

@jdaviescoates It's the incident communication element that makes Cachet more suitable for business.

Thanks, I'm not sure exactly what that is (?), but is it much different from all the notifications Uptime Kuma supports?

See https://github.com/louislam/uptime-kuma/issues/284

I need a good status page

Uptime Kuma does the job nicely imho.

• https://vivaldistatus.com/

Not found anything that compares to Updown.io yet but CachetHQ looks decent and the demo shows more features like explaining incidents:

• https://demo.cachethq.io/

The thing I don't like about StatPing is the red blocks for a whole day when you might have had a 1 minute outage.

If so, it would be really nice to have someone explain how to install it using the cli.

Thanks!

Monitoror is a quite passive status page meant to be displayed on a large screen, so does not offer any way to interact with it.

code: https://git.cloudron.io/fbartels/monitoror-app
my installation: https://monitor.9wd.eu/?configPath=./config.json

monitoror has this one downside to me that you cannot pass a default configuration but always need to specify the configuration through the url. this makes monitoror very flexible since one installation can serve a practically unlimited amount of dashboards, but you also always need to know the name of your configuration.

Monitoror can work together with statping since it can parse and show data from the json status of statping.

apart from that statping seems to have some bugs that make it a bit difficult. like for whatever reason I cannot use local assets, but must use their cnd. i have mixed feelings about the android app and the auto configuration through the qr code did not work for me (did not fill api secret). but still everything else looks to be less simple, but flexible.