+ Service status
Recover.is service
status.
Pre-launch
All systems reserved · no production traffic
Recover.is hasn't onboarded its first paying customer yet. There is no production data plane to report incidents from. The components listed below are provisioned and exercised in our internal pre-launch environment; they will move to live status reporting at general availability.
+ Components
Every layer in the path between you and your data. State today reflects our pre-launch posture; component-level uptime begins reporting at GA.
S3 gateway
API
Public S3-compatible endpoint. Pre-launch: deployed in staging, not exposed publicly.
Object storage
Atlas glacier
Capacity reserved with Atlas. Bytes flow at first paid contract.
Control plane
Tenant + policy
Tenant management, retention policies, audit log emitter. Running on internal Atlas tenancy.
Authentication
Authentik (self-hosted)
OIDC + SAML. Hosted in our Atlas tenancy, not a third-party SaaS.
Key management
OpenBao (self-hosted)
KEKs live here. Audited unwrap is the only path to a usable DEK.
Marketing site
recover.is
This site. The one piece of public infrastructure we run today.
+ Incident history
No incidents to report. There is no production data plane yet — when there is, every P1 and P2 incident lands here within four hours, with a public post-mortem within ten business days.
+ What lands here at GA
- +Per-component availability (last 24h / 7d / 30d / 90d)
- +Open incidents with timestamped updates
- +Resolved incidents archive with linked post-mortems
- +Scheduled maintenance windows announced ≥7 days in advance
- +RSS feed and email subscription
+ Stay informed
We don't have an automated subscription endpoint yet. Until we do, email us and we'll add you to the manual notification list — you'll get the same alerts the on-call team gets, in the same window.
Subscribe via email→