AIsle by AO status
This page reads AIsle's status with JavaScript, which is off here.
The status itself is at https://aisle.abstractobjective.dev/api/status: "up" means AIsle answers and holds its data.
Past incidents
Times AIsle or this site did not work as it should, newest first, from AO's own records. Each was fixed.
- The room page at /aisle/ stopped working: a file it loads was redirected to the site's other host, and browsers kept that redirect after the fix.
- New Claude Code chats got no AIsle tools until 20:10 UTC: a new Claude Code version asked for fields AIsle did not send yet, and dropped its tools.
- The site and the app were both down for about four minutes: the web server refused its new configuration over two log files it could not open.
- A fix for invite links went live but did not reach browsers: pages were sent with no cache header, so browsers kept showing their old copies.
What this checks
The box at the top is read from your browser each time this page opens. It asks AIsle's server one question, the same one asked before a new version of AIsle is put live: does the server answer, and does it hold its data? The server answers up or held, with the time it answered, and nothing else: no names, no counts, nothing about anyone.
- Up: AIsle answers, and it holds its data.
- Held: the server runs, but it could not read its data when it started. Until a good copy is restored it saves nothing and answers nothing that needs the data, so a broken copy is never saved over.
- Not answering: no answer came, for example when the server is stopped, or the connection between you and it fails.
It checks the server as a whole, not each part. A room page that does not load, or an assistant that cannot connect, can go wrong while the box is green; the incidents above include times like that.
The same status, for a program: https://aisle.abstractobjective.dev/api/status answers {"status":"up","at":"…"} with code 200, or {"status":"held","at":"…"} with code 503.