Start free

How quietstats checks it is up

A check every 10 minutes that quietstats.co.uk and its ops page answer, published as a small status file.

Alerts & monitoring

What it does

quietstats’ own uptime monitor. It watches quietstats itself, not your website.

Why it matters

If the collector were down, your visits would be lost. Watching it every 10 minutes means a problem is spotted fast.

How to use it

  1. Nothing to set up.
  2. Developers can read the latest result at /status/uptime.json (cached for 60 seconds).

How it works

How quietstats checks it is up1. Every 10 minutes a scheduled job fetches quietstats.co.uk and the ops page. 2. It saves the latest state per address and a count per day. Days older than 90 are removed. 3. A single failed check is not counted as down. (otherwise: 1 failure: still up) 4. Two failed checks in a row = down. 5. The result is published at /status/uptime.json (cached for 60 seconds) and on the ops page.1Every 10 minutes a scheduledjob fetches quietstats.co.ukand the ops page.2It saves the latest state peraddress and a count per day.Days older than 90 areremoved.3A single failed check is notcounted as down.1 failure: stillup4Two failed checks in a row =down.5The result is published at/status/uptime.json (cachedfor 60 seconds) and on the opspage.
From the uptime monitor. It watches quietstats itself, not your website. Outage alerts are not switched on.

Privacy

Plans

Not a plan feature: this describes how quietstats monitors its own service. See pricing.

Questions

Can it watch my site?

Not yet. It only checks quietstats. A dropped-traffic alert is the closest thing for your site: a sudden drop often means your script stopped loading.

Related