Platform status
Check the live status board first: status.stasho.xyz. It runs independent uptime checks against the Stasho app, the Stasho API, and the underlying Aleph Cloud network, and it is hosted off Stasho's own infrastructure so it stays reachable even when Stasho does not. It shows the current state of each signal plus uptime history and a timeline of past incidents.
The status pill in the dashboard header is a complementary, real-time signal. It is a live check, not a marketing badge: your browser probes the Stasho backend's health endpoint every 60 seconds and shows what it finds right now.
| Pill | Meaning | What still works |
|---|---|---|
| All systems normal | The backend is responding | Everything |
| Degraded | The backend responds but reports a problem | Your deployed sites keep serving (they're on IPFS, not on our backend); dashboard actions may fail |
| Outage | The backend is unreachable from your browser | Your deployed sites keep serving; the dashboard can't load or change anything until it recovers |
You can run the same check yourself: api.stasho.xyz/api/health.
The part the pill can't see
Your sites are served by Aleph's IPFS gateway, not by the Stasho backend, so a backend outage never takes your site down, and conversely a gateway problem won't show in the pill. The status board covers this gap: it checks the app's public URL directly, which exercises the same gateway the pill cannot reach. If your site is unreachable but the pill says normal, check the status board and the custom domains guide (DNS and gateway states) first.
During the alpha
Check the status board first: it tells you whether a known incident is in progress and carries the uptime history. For anything the board does not explain, email hello@stasho.xyz, which during alpha reaches a human who can actually restart things.
Worth restating because it's the design, not bravado: even if Stasho disappeared entirely, your deployed sites stay pinned on IPFS and your data remains recoverable with your wallet key.