Public status page showing live platform health and uptime history
· v0.5.0
When something feels off — a slow login, a file that won't load — there was no quick way to check whether the issue was on our end or yours. You had to email support and wait.

There is now a public status page at /status that shows the live health of each platform capability, a 90-day uptime history, and a derived incident log for the past 14 days. No account required — you can bookmark it and check it any time, or send the link to a teammate who is trying to figure out whether to wait or escalate.
What the page shows
Each capability appears as a row with a current status indicator (Operational, Degraded, or Disrupted) and a bar chart covering the last 90 days. Status is checked every five minutes. To avoid false alarms from a single blip, a capability only moves out of Operational after two consecutive bad checks. If checks go stale — for example, if our monitoring itself has a problem — the indicator shows Unknown rather than a misleading Operational or Down. A global banner at the top summarizes overall health so you get the picture at a glance without reading every row. The page refreshes automatically every two minutes.
Incident history
Below the capability list, a 14-day incident log surfaces events derived from the same probe data. Because incidents are tied to the same two-consecutive-check rule, the history matches what you would have seen in the live indicators at the time.
What's covered at launch
The page currently covers: Platform, Authentication, Database, Sync, and Hosting. Additional capabilities — including the BIM viewer, model processing, payments, and storage — will appear as we finish verifying their probes. Rows with no reliable probe data are not shown rather than shown as Unknown, so everything visible on the page reflects a real check.
A note on full-outage scenarios
The status page runs inside the same infrastructure it monitors. If there is a complete platform outage, the page itself may be unreachable and probes will stop running — affected capabilities will surface as Unknown via the stale guard once checks lapse, rather than showing a specific Down state. We are adding an independent external monitor as a follow-up to cover this gap.