Quick answer
MongoDB Atlas documents idle pause threshold as 30 days with zero connections. Atlas can automatically pause an idle free cluster.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| idle pause thresholdAtlas can automatically pause an idle free cluster. | 30 days with zero connections | Free cluster | MongoDBAug 22, 2026 |
Why does this limit matter?
Rarely used demos can surprise users with resume latency or restoration constraints.
This value is scoped to Free cluster; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Export important data and monitor connection activity before extended inactivity.
- 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
- A cluster on an obsolete version might not be restorable to the current version after a long pause.
- 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