MongoDB Outage History

We have identified an issue impacting groups containing only Flex or Free clusters. For those clusters, TLS certificates are incorrectly not being rotated. We are working on remediation steps.

We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.

We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.

Azure has confirmed that there are networking issues in the westus region. Please follow the official azure status post for more detailed updates https://azure.status.microsoft/en-us/status

We are aware of an ongoing Azure networking incident affecting the West US region. Some Atlas clusters hosted in Azure West US may experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. Azure is investigating the issue and evaluating mitigation options. We will provide additional updates as more information becomes available.

Azure is rolling out a mitigation for the ongoing networking incident affecting the West US region, and we are seeing signs of recovery. Some Atlas clusters hosted in Azure West US may continue to experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. We are monitoring recovery closely and will provide additional updates as more information becomes available.

Due to an ongoing incident with AWS's billing data, MongoDB Atlas and Atlas for Government will not be updating AWS network or backup consumption data over this weekend, 2026-07-17 through 2026-07-20. The products themselves will remain fully available. When the upstream issue has been resolved, we intend to display and bill for the correct amounts. Charges will have usage dates that correctly express the usage, but will have the billed date of when this is corrected. Cluster and backup health are unaffected. Other cloud providers' billing data is unaffected. You can follow the upstream incident at https://health.aws.amazon.com/health/status

We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.

We've identify an issue with networking in GCP regions and are working on fix

Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.

We have identified the root cause of the search query failures and are working on a mitigation for impacted clusters. Clusters with dedicated search nodes are unaffected. Some clusters with colocated search nodes may see search query failures.

AWS Availability Zone use1-az4 in US-EAST-1 region is impaired. For some clusters in AWS US-EAST-1 region, cluster nodes in that availability zone may have impaired health. Some Atlas operations, including instance scaling and cluster configuration changes, may also be delayed for clusters in AWS US-EAST-1. Please see https://health.aws.amazon.com/health/status for more information.

DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.

DNS changes for AWS clusters are currently degraded. Cluster topology modifications may be delayed or not able to complete successfully. We've identified the issue and are pushing out a patch.

Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.