Quick answer
Fly.io documents snapshot retention as 5 days default; configurable 1–60 days. Snapshots are a recovery feature and remain tied to volume behavior.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| snapshot retentionSnapshots are a recovery feature and remain tied to volume behavior. | 5 days default; configurable 1–60 days | Fly Volumes | Fly.ioAug 22, 2026 |
Why does this limit matter?
The default window may be shorter than the time needed to discover silent data corruption.
This value is scoped to Fly Volumes; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Verify retention, backup frequency, restore procedure, and recovery-point objective.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Snapshots do not replace application-consistent backups and restore testing.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related