Resources
The public status page and status.json, what they show, and how incidents are reported.
kiste.run/status shows whether Kiste is working:
- the state of each component: kiste.run itself (sign-in, console and API), each compute service that runs Kisten, the storage of Kisten, and off-site checkpoints;
- uptime over the last seven days;
- incidents of the last 90 days, with what happened, when it started and when it was resolved;
- planned maintenance windows;
- server errors per hour, as measured on kiste.run.
The same information is available as JSON at
kiste.run/status.json, without a sign-in, for
your own monitoring. See GET /status.json.
kiste doctor checks the status from the command line, together with your
sign-in:
During an incident that affects the compute service, the API answers N01 ("kiste.run can't reach the compute service right now. Your Kisten are safe."). Your Kisten keep running or stay stopped as they were; the error means kiste.run can't reach them for the moment.