Bstrapr currently runs a single primary production control plane. That is a real availability trade-off we disclose rather than hide. This page is the public status surface while we build richer uptime history.
Current: Operational (no open incident)
We do not yet publish a multi-month automated uptime chart. When a customer-impacting incident occurs, we will note start/end time and impact summary here and notify affected accounts when appropriate.
Availability model
- Shared platform: one primary control plane (API, dashboard, enrollment, grants/revoke).
- Already-established VPN peer paths may keep working if the control plane is briefly unreachable; new enrollments, invites, grants, and revokes will not complete until it is back.
- Your Sites and workloads keep running on your infrastructure regardless of Bstrapr control-plane state.
- Dedicated deployments can define stronger isolation and recovery objectives when the shared model is not enough.
Recovery practices
- Detect via monitoring and customer reports
- Restore the control plane and Headscale enrollment path; verify health checks
- Confirm database backups and configuration restores if the failure required them
- Communicate impact and resolution on this page and by email when needed
- Follow up with hardening so the same class of issue is less likely to recur
Recent incidents
None published.