Status
How to tell whether we are actually watching.
The dangerous failure in monitoring is not the loud one. It is the watcher that stops while everything still looks calm.
This is not a live status board. We do not have one yet. Rather than put a green tick on a page and update it by hand — which is how status pages come to say “all systems operational” during an outage — this page explains what we publish instead and where to look.
The heartbeat
The process that runs your checks publishes a heartbeat every time it
completes a cycle. The web application reads that heartbeat and reports
it at
app.plumbline-lb.com/health,
which is open and needs no account.
If the heartbeat is recent, checks are running. If it is stale, they are not, and that is visible to you at the same moment it is visible to us. There is no version of this where we know and you do not.
What happens when we fail
A check we could not carry out is never recorded as a site failure. It is recorded as ours, shown in its own state with its own wording, and excluded from the counts in your client’s monthly report — with the report saying how many were excluded rather than quietly dropping them.
So a bad night at our end shows up on your overview as partly checked, not as a client site in trouble, and shows up in the report as a stated gap rather than as a worse-looking number for your client.
Scheduled work
Deployments are rolling and do not stop checks. Database migrations run before a new version serves anything, as their own step, so two versions never race to change the schema during a restart.
If we ever need a window where checks genuinely stop, we will tell affected agencies by email beforehand, and the report covering that period will say so.
What we do not claim
We publish no uptime target for our own service, and we do not offer an availability SLA. Both would be numbers we have no operating history to support. When we have that history, we will publish what actually happened rather than what we promised.
That is the same rule we apply to your clients’ sites, and it would be strange to apply it in one direction only. The longer argument is here.
Telling us something is wrong
If Plumbline looks wrong to you — a stale heartbeat, an alert that makes no sense, a report that does not match what you saw — write to hello@plumbline-lb.com. An alert you did not believe is a bug report, and we want it.