Clavis Sinica API · Status

Checks run on GitHub's infrastructure, not on the servers being checked. If our machine goes down, this page keeps reporting — that is the whole reason it lives here.

Scheduled every 5 minutes. GitHub's scheduler is best-effort and can be delayed or skipped when it is busy, so a gap in the history means the check did not run, not that the service was down. Gaps are drawn in grey, never as green.

The API health endpoint returns HTTP 200 even when it is degraded and says so in the response body. This probe reads the body, so a degraded engine shows up here as degraded.

No uptime SLA is offered. This page reports what was measured. It is not a commitment, and the numbers cover only the period since measurement began — shown above, so a short history cannot be mistaken for a long one.