CompaniesMongoDB AtlasIncidents
MongoDB Atlas: Atlas and Cloud Manager Monitoring Delays
Timeline of updates
- resolved
This incident was resolved. During this time: * Metrics data was collected but with an increased period between data points * From approximately 15:10 through 15:30 UTC requests to create new Atlas clusters or to modify existing Atlas clusters were queued. * From approximately 15:10 through 15:30 UTC some Atlas clusters may have displayed warning icons on in the Clusters page. These warning icons did not indicate any issue with the Atlas clusters themselves - this was a side-effect of the delayed metrics data. * A small number of Atlas clusters skipped a scheduled backup snapshot.
From MongoDB Atlas’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mongodb.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by MongoDB Atlas, started 2020-01-16 14:18 UTC, resolved after 4.2 h, 1 update(s).
- Title
- Atlas and Cloud Manager Monitoring Delays
- Vendor
- MongoDB Atlas
- Date
- URL
- https://rewindex.com/company/mongodb-atlas/incidents/n0kttlxl8c7f
MongoDB Atlas profileRecent MongoDB Atlas incidentsAll outages on January 16, 2020MongoDB Atlas in January 2020MarkdownJSON