Checking our service
Checking now, then rechecks every 30 s
Relay Carries the encrypted session between your machines checking
API and accounts Sign in, devices, billing checking
Dashboard and viewer termuna.com/app and shared session links checking
Push notifications Attention nudges and pattern watch alerts. Delivery runs through Apple and Google and is not measured from here. not probed
One request from your browser to /v1/config, repeated every 30 seconds. The relay, the API and the dashboard's backend are one service, so that one answer speaks for the first three rows. It does not speak for push delivery, and the fourth row says so rather than borrowing it.
Uptime history
We do not publish uptime history yet. Nothing records this service day by day: the outside monitor probes it every five minutes and opens an issue when it fails, but it keeps no ledger a bar strip could be drawn from. The strip appears here when there is a measured day to draw, never before.
What an outage here costs you
- Your terminal keeps running. The app and the daemon are on your machine. Panes, splits, scrollback, running commands and your SSH connections never pass through us.
- Your vault keeps working. Hosts, keys and snippets are decrypted on your machine and readable offline.
- What pauses: handoff to another device, the dashboard at /app, shared session links, push notifications, command history between machines, sign-in and billing. The daemon keeps retrying the relay on its own, one second apart at first and a minute apart at most. When we are back, a session resumes from its last acknowledged frame and replays the gap, or resyncs in full when the gap is too old to replay.
Incident history
None recorded. This page started keeping the list on 2026-09-06; anything before that was not written down, so it is not claimed here either.