The two cards below are not a picture. Your browser calls our API the moment this page loads and prints what came back. If we are down, this page says we are down.
Liveness touches nothing — no database, no storage. It proves the process is running. On 19 October 2026 we had an hour in which this endpoint answered 200 in milliseconds while no customer could load a single screen, because a missing file broke the database model on first use. Any uptime monitor pointed at it would have recorded that hour as perfect availability.
Readiness exists because of that hour. It resolves the services that actually broke and touches the database and the document store, so it can genuinely fail. If you are monitoring us from your own tools, point them at the readiness URL, not the liveness one.
We are not publishing an uptime percentage yet, and you should distrust the ones that appear on new products' websites. Until 20 October 2026 this site carried “99.97% uptime (last 12 months)” on its customers page. Nobody could produce the measurement behind it, so it is gone rather than rounded down.
A real figure needs independent monitoring from outside our own network, running for a known period, with the incidents listed. When that has run long enough to mean something, the number and the monitor that produced it will both be on this page.
If you need a measured availability figure for a tender or a contract, ask us and we will set up independent monitoring for your account and share what it records, rather than publishing a number we cannot stand behind.
AI & your data · Privacy policy · Terms · Refund policy · Contact & grievance officer