Butterfly Security system status
Real-time health of every subsystem behind the recovery platform. Probes run server-side every 15 seconds and this page polls every 30. For architecture and security controls, see /security.
All systems operational
Every subsystem responded within expected bounds.
Subsystems
| Subsystem | Detail | Last checked | Status |
|---|---|---|---|
| Loading subsystem health… | |||
We publish current state only. We do not advertise SLAs we have not yet measured – historical uptime numbers will be added once we have at least 90 days of probe data.
Uptime & SLA
- Target SLA
- 99.95%
- 90-day measured uptime
- TBD
Monthly availability target across customer-facing subsystems.
First measurement window closes 2026-09-01. We do not publish a percentage until we have probe data covering the full window.
Recent incidents
No incidents reported. When an incident occurs, a post-mortem will appear here with detection time, root cause, customer impact, and remediation.
Security incidents are also disclosed in the product changelog and notified to affected customers within 72 hours per GDPR Article 33 timing.
Subscribe to status updates
Get notified when subsystem health changes or a post-mortem is published.
RSS feed will publish each status change as an item – currently a placeholder URL while we wire the generator.
Upstream providers
Butterfly runs on Cloudflare Workers + R2 (compute, edge, object storage) and Supabase Postgres (metadata, accounts, activity logs). When an upstream provider has an incident, ours follows.
Status data sourced from /api/observability/status (server-side probes against each subsystem) plus the Cloudflare and Supabase public status pages. Subsystem probes run every 15s server-side and this page polls every 60s.