Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean MongoDB Atlas has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 5 scoped observations for MongoDB Atlas. The baseline covers free cluster data storage, concurrent connections, read and write operations, database and collection counts, idle pause threshold. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| free cluster data storageStored BSON documents and their indexes count toward the hard cap. | 0.5 GB | Free cluster | MongoDBAug 22, 2026 |
| concurrent connectionsAtlas connection limits apply per node or mongos depending on topology. | 500 | Free cluster | MongoDBAug 22, 2026 |
| read and write operationsAtlas throttles and applies a one-second cooldown when the limit is exceeded. | 100 operations per second | Free cluster | MongoDBAug 22, 2026 |
| database and collection countsThe collection count is aggregate across all databases in the cluster. | 100 databases and 500 collections total | Free cluster | MongoDBAug 22, 2026 |
| idle pause thresholdAtlas can automatically pause an idle free cluster. | 30 days with zero connections | Free cluster | MongoDBAug 22, 2026 |
Tracked constraints and impact
Managed cluster connections, storage, throughput, collections, and project limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
MongoDB Atlas Free Storage Limit
MongoDB Atlas Free Storage Limit, verified against MongoDB Atlas's official documentation with scope, implementation impact, caveats, and a direct check.
MongoDB Atlas Free Connection Limit
MongoDB Atlas Free Connection Limit, verified against MongoDB Atlas's official documentation with scope, implementation impact, caveats, and a direct check.
MongoDB Atlas Free Throughput Limit
MongoDB Atlas Free Throughput Limit, verified against MongoDB Atlas's official documentation with scope, implementation impact, caveats, and a direct check.
MongoDB Atlas Free Database & Collection Limits
MongoDB Atlas Free Database & Collection Limits, verified against MongoDB Atlas's official documentation with scope, implementation impact, caveats, and a direct check.
MongoDB Atlas Free Cluster Auto-Pause
MongoDB Atlas Free Cluster Auto-Pause, verified against MongoDB Atlas's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current MongoDB Atlas baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Storage, connections, throughput, databases, collections, and pause rules