How we monitor your apps

Your apps are checked automatically. If one stops responding, you get an email — rather than finding out when a customer tells you.

What the check does

We request your app's own address, exactly the way a visitor would, and look at how it answers.

Anything that answers counts as healthy, including a login page or a redirect. Only a server error or no response at all is treated as a problem.

A single failed check is not enough to email you. Apps restart, updates take a moment, and networks hiccup. We wait for the problem to persist before telling you about it.

What we will not email you about

An app you stopped yourself. If you stop an app from the panel, that is a deliberate action and we do not treat it as an outage. The same applies while an app is being updated, resized or restored.

You will only hear from us about something you did not ask for.

When you get one

The email tells you which app, and when it was last seen working. From there:

1. Check the Logs tab — most causes are stated plainly in the app's own output.
2. Check the app's status on the Overview tab. If it is stopped, start it.
3. If it is running but not answering, restart it.
4. If none of that helps, open a ticket. The email includes a link.

You will get a second email when the app starts responding again, so you can stop worrying without having to check.

What this does not cover

This tells you your app is reachable. It cannot tell you whether the app is doing anything useful — a blog that answers requests while showing an error page inside will look healthy to this check.

For deeper checks, the catalogue includes monitoring apps like Gatus and Uptime Kuma that you can point at your own services and configure however you like.