MongoDB had 56 outages in the last 2 years totaling 635h 18m of downtime — averaging 2.3 incidents per month.
There were 56 MongoDB outages since August 18, 2025 totaling 635h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring the results
This incident has been resolved.
We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions
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.
All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.
Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.
Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration. We are investigating this issue.
The issue has been resolved.
We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.
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.
We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.
This incident has been resolved.
The data plane node logs (mongod, audit logs, etc.) are unavailable since May 14th 4am UTC for clusters in Azure, GCP, and AWS gov-cloud regions. We have identified the root cause and are actively working on a fix.
We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.
The data plane node log download has recovered.
Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.
Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state.
This incident has been resolved.
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.
AWS Availability Zone use1-az4 in US-EAST-1 region is still impaired and AWS is working to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
AWS continues to make progress to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
AWS continues to work towards full recovery. The Atlas system has been successfully taking healing actions on impacted nodes to restore node health and using healthy availability zones for provisioning new nodes. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
This incident has been resolved.
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.
We are still seeing cases where new cluster update requests are failing to go through due to ACME related DNS issues. We are actively investigating this issue.
We've identified a bad piece of metadata causing DNS issues. We've since patched this metadata and are seeing recovery in ACME updates for cluster topology changes. We will continue to monitor recovery.
We are continuing to monitor for any further issues.
DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.
Identified - We have identified an issue causing failures for a subset of Atlas backup export jobs. We are actively working on a fix. Your cluster health and data are unaffected. We will provide another update by May 7 01:30 UTC
We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are observing widespread issues in in Azure West Europe. Customers may see nodes reporting as "down" and delayed cluster modifications for Azure clusters in West Europe. There are three total AZs in Azure West Europe, and primary failover will be handled by MongoDB.
We're starting to see instances recover. We will continue to monitor the region's status in Azure and ensure Atlas takes any available steps to maintain cluster health.
We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational.
We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 24 at 22:00 UTC.
We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.
We are currently investigating reports in MongoDB Atlas for Government that the Business Intelligence Connector (BI Connector) is failing. Affected users will have issues connecting to and querying their BI Connectors. No workaround has been identified at this time. Underlying cluster health is not affected.
We have identified the issue affecting the Business Intelligence (BI) Connector in MongoDB Atlas for Government. We are working on a fix. While no workaround exists, data remains accessible to MongoDB clients. Affected users will not be able to connect to their clusters' BI Connectors. Cluster health is unaffected.
A fix has been implemented and we are monitoring the results. The launch of the fix should be complete by approximately 13:00 UTC 21 April 2026.
This incident has been resolved.
Some Atlas users may be unable to access Charts and the Visualization page due to repeated login prompts or unauthorized errors when attempting to sign in. Our engineers have identified a recent change as the likely cause, have rolled it back, and are monitoring the service to confirm that normal access has been restored.
Identified: Some clusters in the Azure East US 2 region will see delays provisioning new clusters or adding additional nodes to their existing clusters due to Azure capacity constraints. What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region. User action: As a workaround, users can provision clusters in other Azure regions.
We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.
We are currently investigating intermittent spikes of HTTP 503 errors affecting Atlas control plane operations performed via the Atlas Admin API and automation tooling such as Terraform. Impacted requests typically fail for a short period and succeed on retry. Atlas database connectivity and data plane operations remain healthy. Our engineering teams are working to resolve the issue with high urgency and to prevent recurrence. Customers encountering 503 responses are advised to retry failed Admin API and Terraform operations with appropriate retry logic and backoff while we continue our investigation.
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
We continue to monitor our systems for intermittent spikes in 503 HTTP errors following our deployed fix. We will provide another update tomorrow by 3 PM UTC.
We are no longer seeing intermittent spikes in HTTP 503 errors.
We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.
The issue has been identified and we are working on a fix.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified an issue affecting the Clusters page in MongoDB Atlas. Affected users may see a blank page when trying to view their Clusters page. Cluster health is unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At approximately 10:30 AM CT, we identified an issue affecting stream processing within the AWS US-EAST-1 region. As of now, normal operations have resumed. We have initiated a full investigation to determine the root cause and prevent future recurrence.
Atlas cluster snapshots are failing. We are actively investigating.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue. Some users may not be receiving emails from MongoDB. We are looking into the cause and will provide an update as soon as we know more.
This incident has been resolved. Email notifications are being sent successfully.
We are currently investigating an issue with Atlas App Services Device Sync. Affected users of this deprecated service may see SSL validation errors. We will update this post with more details as they become available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing degraded service with our DataDog integration for several DataDog regions. This may result in incomplete metrics, or issues with alerting for customers using the DataDog integration. We are investigating this issue.
A fix has been implemented and we're monitoring the results.
The issue has been resolved
We are investigating reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh
We are continuing to investigate reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh It appears to affect only a very small number of users, but we will keep this alert open until the issue is resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.