Incident History

MongoDB Atlas: False host down alerts were sent

Between 18:37 and 21:17 UTC on 16 May 2025, MongoDB Atlas sent out false Host Down alerts to a small portion of our users. Cluster health was unaffected during this time and we sincerely apologize for the confusion.

1747422959 - 1747422959 Resolved

Atlas Cluster Degraded Status in Azure South Africa West and Azure South Africa North

This incident has been resolved.

1747184563 - 1747229752 Resolved

Atlas Clusters restore failures

This incident has been resolved.

1746732241 - 1746732476 Resolved

Delayed Atlas metrics processing

The incident is now resolved. Since May 1st 2025 at 04:52 UTC we falsely reported a limited number of Atlas Clusters as down in the UI and alerted as such.

1746175074 - 1746188068 Resolved

MongoDB Atlas and Cloud Manager: Alerts Paused

Alerting latency is back within expected thresholds.

1745097279 - 1745104941 Resolved

MongoDB Atlas and Cloud Manager: Metrics Delayed

This incident has been resolved.

1744816196 - 1744821462 Resolved

MongoDB Atlas and Cloud Manager: Alerts paused and metrics delayed

We have confirmed sustained recovery. All systems continue to operate normally.

1744602876 - 1744605561 Resolved

MongoDB Atlas and Cloud Manager: Alerts paused and metrics delayed

This incident has been resolved.

1744209405 - 1744220748 Resolved

Intermittent connection issues for some clusters in the AWS Frankfurt region

We have received confirmation that this issue has been resolved by taking a host offline in the AWS network that was causing the DNS resolution issues. We also continue to confirm with customers that they are not seeing any residual impacts of this issue.

This issue is now resolved.

1743613350 - 1743698453 Resolved

Atlas Cluster Creation and Modification Delays in GCP Ohio (us-east5) region

This incident has been resolved.

1743283336 - 1743303640 Resolved
⮜ Previous Next ⮞