Warden's own console
If this is down, nobody can see what any of the others are doing.
- the site answers200 in 673ms
- the process is uponline, 46 restarts since deploy
- the certificate is not about to expire63 days left, until 2026-12-13 (Let's En
The public fleet
Three real services, no sign-up.
This is the fleet this Warden actually watches, live. It is not a screenshot, the outages in it really happened, and the button below really causes one.
3services watched
1,800checks run
33problems
31closed without waking anyone · median 2m down
Nothing of yours yet.
Give Warden a URL and it starts checking. Add your deploy hook and, when that URL stops answering, it works out why over the network, redeploys within the rules you set, and proves it by asking the check again. Give it the machine and the process as well and it can read the logs, the process table and the last few commits too.
No account and no email: a signed cookie makes a service yours. Below is the fleet this Warden actually watches, live — it is not a screenshot, and the outages in it really happened.
Point it at somethingWatching, right nowanyone can watch these · only their owner can change them
up
Vigil
A public site. If it is down, visitors get nothing.
- the site answersexpected 200, got 502
- the process is uppm2 says "stopped"
- the certificate is not about to expire63 days left, until 2026-12-13 (Let's En
SAGE
Someone else's production, and it is submitted to two competitions. Warden watches it and touches nothing.
- the site answers200 in 233ms
- the process is uponline, 16 restarts since deploy
- the certificate is not about to expire56 days left, until 2026-12-06 (Let's En