Measured, not asserted. The API times a real graph read and a cache round trip once every 60 seconds, and this page prints whatever those readings are.
The probe query is a real read against the real dataset, counting the controls of a framework through its domains, not a round trip that measures the driver and nothing else. Cache round trip is 0.5 ms at the median.
What this does not tell you
The API timing its own dependencies once a minute. This is not external monitoring: a probe running inside the API cannot observe an outage that takes the API down with it, so read the sample count as the coverage. A 24 hour window holds 1440 samples when nothing restarted.
Same data, without the page:
curl -s https://api.theartofservice.com/api/public/status
Security states what is and is not in place, including our own ISO 27001 gap report.