Service status
This page asks our server two questions from your browser, right now, and shows the answer as it came. It keeps no record of past checks.
Right now, from your browser
Your browser sends two requests to kaeris.dev and shows what came back. If it gets no usable answer, it says so; it never fills a gap with "ok".
-
/api/health Checking…
Asks whether the server process answers at all.
-
/api/health/ready Checking…
Asks whether the product can do its job: translation, payments and key email.
What each check means
/api/health
Answers {"status":"ok"} for as long as the server process can reply. It says the process is alive and nothing more.
/api/health/ready
Answers {"status":"ok"} when the product can do its job, and HTTP 503 with "degraded" when it cannot: for example when our translation provider is failing, or when payment or key email is not configured. We do not publish the reasons on this page.
An "ok" here means these two addresses answered as described. It does not mean every file, language or feature works for you, and it says nothing about services we depend on beyond what the second check covers.
Check it yourself
Any terminal with curl. The first command prints the HTTP status code, 200 when the check passes; the second prints the full answer.
curl -s -o /dev/null -w "%{http_code}\n" https://kaeris.dev/api/health
curl -s -w "\nHTTP %{http_code}\n" https://kaeris.dev/api/health/ready
History
There is no history yet: the history will start after an external monitor is connected. Until then this page shows no past data, no uptime figure and no chart, because we do not have real numbers to show.
What this page is not
It is a live look, not a promise and not a guarantee of availability. If something is wrong for you, write to [email protected] and say what you did and what you saw. More on how we handle your data is on the security page.