Continuous
Measurement at a 15-minute cadence. Never a stale snapshot.
Anti-gaming
Verdict = minimum over a rolling 24 hours. No one can game the signal.
Integrity proof
SHA-256 hash-chain + anchoring + RFC 3161 timestamping via a qualified eIDAS TSA. Verifiable by a third party.
Neutral
Paid by the buyer, never by the measured party. No conflict of interest.
Illustrative example — timestamped verdict
Service "API-228" · availability 99.98% sealed continuously · 0 declared/measured gap · report verifiable in one link.
How do I prove the real uptime of my service to my client?
Through continuous availability measurement, sealed at a 15-minute cadence, eIDAS-timestamped and anchored on Hedera. You provide a verifiable uptime history, independent of your own dashboard.
In a dispute over an incident, what technical proof can I produce?
A timestamped, anchored availability journal, hash-chained (SHA-256). The incident timeline is fixed and verifiable by a third party, without relying on your monitoring tool.
Is your availability measurement independent of my infrastructure?
Yes. The measurement is external to your infrastructure: it does not come from your own logs, which makes it credible to a client or an arbitrator in an SLA dispute.
Can I verify the uptime history without going through my own dashboard?
Yes. The hash of each check is anchored on Hedera: your client verifies the history by recomputing the hash, without accessing your dashboard or your data.
What measurement granularity do you offer (1 min, 5 min)?
The standard cadence is 15 minutes, adjustable per contract. The verdict is computed on a rolling 24-hour window to reflect real availability, not a favorable snapshot.
Is the measurement timestamped and verifiable by a third party in an SLA dispute?
Yes. eIDAS timestamping and Hedera anchoring: the anteriority and integrity of each availability measurement are verifiable independently of both parties.