MongoDB Outage History

Started Jun 02, 2026, 11:00 PM UTC· resolved Jun 03, 2026, 12:11 AM UTC

1. investigating Jun 02, 2026, 11:00 PM UTC

   We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions

2. identified Jun 02, 2026, 11:42 PM UTC

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

3. identified Jun 03, 2026, 12:01 AM UTC

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

4. monitoring Jun 03, 2026, 12:05 AM UTC

   All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.

5. resolved Jun 03, 2026, 12:11 AM UTC

   Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.

Read the full incident report →

Started May 28, 2026, 10:02 PM UTC· resolved May 28, 2026, 11:15 PM UTC

1. investigating May 28, 2026, 10:02 PM UTC

   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.

2. resolved May 28, 2026, 11:15 PM UTC

   The issue has been resolved.

Read the full incident report →

Started May 23, 2026, 07:48 PM UTC· resolved May 24, 2026, 02:05 AM UTC

1. investigating May 23, 2026, 07:48 PM UTC

   We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.

2. identified May 23, 2026, 08:14 PM UTC

   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.

3. monitoring May 24, 2026, 12:14 AM UTC

   We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.

4. resolved May 24, 2026, 02:05 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 22, 2026, 08:32 PM UTC· resolved May 22, 2026, 10:17 PM UTC

1. investigating May 22, 2026, 08:32 PM UTC

   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.

2. monitoring May 22, 2026, 09:17 PM UTC

   We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.

3. resolved May 22, 2026, 10:17 PM UTC

   The data plane node log download has recovered.

Read the full incident report →

Started May 08, 2026, 02:24 AM UTC· resolved May 09, 2026, 02:24 PM UTC

1. identified May 08, 2026, 02:24 AM UTC

   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.

2. monitoring May 08, 2026, 03:12 AM UTC

   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.

3. monitoring May 08, 2026, 12:34 PM UTC

   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.

4. monitoring May 08, 2026, 08:41 PM UTC

   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.

5. resolved May 09, 2026, 02:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2026, 03:17 PM UTC· resolved May 07, 2026, 10:15 PM UTC

1. identified May 07, 2026, 03:17 PM UTC

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

2. identified May 07, 2026, 03:20 PM UTC

   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.

3. identified May 07, 2026, 04:58 PM UTC

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

4. investigating May 07, 2026, 05:50 PM UTC

   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.

5. monitoring May 07, 2026, 07:47 PM UTC

   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.

6. monitoring May 07, 2026, 07:47 PM UTC

   We are continuing to monitor for any further issues.

7. resolved May 07, 2026, 10:15 PM UTC

   DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.

Read the full incident report →

Started May 06, 2026, 09:48 PM UTC· resolved May 07, 2026, 08:55 PM UTC

1. identified May 06, 2026, 09:48 PM UTC

   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

2. identified May 07, 2026, 01:20 AM UTC

   We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.

3. monitoring May 07, 2026, 08:02 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved May 07, 2026, 08:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 03, 2026, 05:33 PM UTC· resolved May 05, 2026, 05:28 PM UTC

1. investigating May 03, 2026, 05:33 PM UTC

   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.

2. monitoring May 03, 2026, 08:19 PM UTC

   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.

3. resolved May 05, 2026, 05:28 PM UTC

   We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational.

Read the full incident report →

Started Apr 27, 2026, 05:16 PM UTC· resolved Apr 27, 2026, 08:50 PM UTC

1. identified Apr 27, 2026, 05:16 PM UTC

   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.

2. resolved Apr 27, 2026, 08:50 PM 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.

Read the full incident report →

Started Apr 17, 2026, 05:03 PM UTC· resolved Apr 21, 2026, 01:45 PM UTC

1. investigating Apr 17, 2026, 05:03 PM UTC

   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.

2. identified Apr 17, 2026, 08:24 PM UTC

   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.

3. monitoring Apr 20, 2026, 07:17 PM UTC

   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.

4. resolved Apr 21, 2026, 01:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 01, 2026, 12:55 PM UTC· resolved Apr 01, 2026, 12:55 PM UTC

1. resolved Apr 01, 2026, 12:55 PM UTC

   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.

Read the full incident report →

Started Mar 30, 2026, 09:47 PM UTC· resolved Mar 30, 2026, 11:10 PM UTC

1. identified Mar 30, 2026, 09:47 PM UTC

   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.

2. resolved Mar 30, 2026, 11:10 PM UTC

   We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.

Read the full incident report →

Started Mar 25, 2026, 09:31 PM UTC· resolved Mar 27, 2026, 01:21 PM UTC

1. investigating Mar 25, 2026, 09:31 PM UTC

   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.

2. monitoring Mar 25, 2026, 11:39 PM UTC

   The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.

3. monitoring Mar 26, 2026, 07:12 PM UTC

   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.

4. resolved Mar 27, 2026, 01:21 PM UTC

   We are no longer seeing intermittent spikes in HTTP 503 errors.

Read the full incident report →

Started Mar 19, 2026, 06:11 PM UTC· resolved Mar 19, 2026, 07:19 PM UTC

1. investigating Mar 19, 2026, 06:11 PM UTC

   We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.

2. identified Mar 19, 2026, 06:25 PM UTC

   The issue has been identified and we are working on a fix.

3. monitoring Mar 19, 2026, 07:01 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Mar 19, 2026, 07:14 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 19, 2026, 07:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 19, 2026, 02:42 PM UTC· resolved Mar 19, 2026, 03:28 PM UTC

1. identified Mar 19, 2026, 02:42 PM UTC

   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.

2. monitoring Mar 19, 2026, 03:17 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 19, 2026, 03:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 19, 2026, 12:24 AM UTC· resolved Mar 31, 2026, 09:19 PM UTC

1. identified Mar 19, 2026, 12:24 AM UTC

   Impact: Some users may be unable to log into the Atlas for Government UI using SSO. Specifically, users accessing Atlas for Government via a saved SSO login URL may receive an error, and users attempting to log in via a federated identity provider link may be unable to complete authentication. Root cause: We have identified an issue with SSO routing that is preventing some federated login flows from completing successfully. These issues started around 2026-03-18 2:30 UTC. What you might see: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User action: As a workaround, users can log in by entering their email address directly at https://account.mongodbgov.com and following the standard prompts. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as we progress toward resolution, or if we observe any change in impact to Atlas for Government.

2. monitoring Mar 19, 2026, 10:15 PM UTC

   A fix has been implemented and we are monitoring the results. Users who were previously unable to log in via SSO should now be able to authenticate successfully.

3. resolved Mar 31, 2026, 09:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 08:10 PM UTC· resolved Mar 11, 2026, 08:10 PM UTC

1. resolved Mar 11, 2026, 08:10 PM UTC

   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.

Read the full incident report →

Started Mar 10, 2026, 11:18 PM UTC· resolved Mar 11, 2026, 02:30 AM UTC

1. investigating Mar 10, 2026, 11:18 PM UTC

   Atlas cluster snapshots are failing. We are actively investigating.

2. identified Mar 11, 2026, 12:45 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Mar 11, 2026, 02:21 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Mar 11, 2026, 02:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 03:50 PM UTC· resolved Mar 02, 2026, 04:28 PM UTC

1. investigating Mar 02, 2026, 03:50 PM UTC

   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.

2. resolved Mar 02, 2026, 04:28 PM UTC

   This incident has been resolved. Email notifications are being sent successfully.

Read the full incident report →

Started Mar 02, 2026, 12:00 AM UTC· resolved Mar 02, 2026, 12:01 PM UTC

1. resolved Mar 11, 2026, 10:00 AM UTC

   Users may have seen tools and integrations that rely on older MongoDB Atlas Admin API versions (for example, 2023-01-01 and 2023-02-01) start failing with HTTP 410 responses indicating that the requested version was no longer available. This affected workflows using the MongoDB Atlas Admin API through the Terraform provider, the Atlas CLI, and custom automation. This behavior was triggered by our planned retirement process for older API versions, but the resulting user impact was unintended because these versions were still in active use. We have extended the end-of-life date for the affected API versions to mid-2027 (tentative date 2027-07-01) and deployed a configuration change to restore compatibility for these workflows. All affected tools and integrations should now be operating normally & will be updated prior to the modified end-of-life-date. From 2026-03-01 00:00 UTC to 2026-03-02 12:01 UTC, users relying on these older API versions may have experienced failed requests and associated automation errors. No user action is required. Previously failed operations can be retried and should now succeed.

Read the full incident report →

Started Mar 01, 2026, 01:48 PM UTC· resolved Sep 03, 2026, 04:47 PM UTC

1. identified Mar 01, 2026, 01:48 PM UTC

   Impact: Some Atlas customers with deployments in the AWS me-central-1 (United Arab Emirates) region may experience delays in cluster operations (for example, creating, scaling, or modifying clusters and infrastructure-level maintenance tasks). Root cause: AWS is reporting connectivity and power issues affecting APIs and instances in a single Availability Zone in the me-central-1 Region, which can cause increased errors and latency for some AWS services and workflows. For the latest details from AWS, see the AWS Health Dashboard. What you might see: - Cluster create/scale/modify operations remaining in a pending or in-progress state longer than usual - Slower completion of some maintenance and infrastructure operations in the affected region Our actions: - Monitoring the AWS incident and Atlas fleet behavior in me-central-1 Customer action: No action is required at this time. We expect delayed operations to complete as AWS resolves the underlying issue. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as AWS progresses mitigation or if we observe any change in impact to Atlas customers.

2. identified Mar 01, 2026, 02:55 PM UTC

   Update: One or more instances backing MongoDB Atlas clusters in the AWS ME-CENTRAL-1 (United Arab Emirates) region may have been temporarily unavailable due to an underlying AWS issue in a single Availability Zone . According to AWS, a localized power issue in this Availability Zone has affected connectivity and power for some APIs and instances, and may have caused increased errors, latency, or unavailability for certain workloads. For the latest information from AWS, see the AWS Health Dashboard. We continue to closely monitor Atlas deployments in ME-CENTRAL-1 and will provide additional updates if we observe any further impact to Atlas customers.

3. identified Mar 01, 2026, 07:30 PM UTC

   Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status). If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.

4. identified Mar 02, 2026, 02:17 AM UTC

   Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status). If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.

5. identified Mar 02, 2026, 09:20 AM UTC

   According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience outages. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. CURRENT IMPACT Atlas clusters deployed only in me-central-1 may be fully unavailable. For clusters operating solely in me-central-1, backup operations in this region are impaired. Clusters and backups should remain operational in me-south-1 at this time. Clusters in me-south-1 may be running at reduced capacity due to zonal constraints. AWS has indicated an extended resolution timeline for service in the impacted Regions and Availability Zones. RECOMMENDED CUSTOMER ACTIONS If you have a multi-region configuration that includes a healthy secondary region, we recommend routing application traffic to that secondary region. If you have clusters in me-south-1 taking backups, we recommend enabling "Additional Snapshot Copies Policy" to a different region. If you have time-sensitive production changes or operations that are blocked and need urgent assistance, please contact MongoDB Support via the Support Portal, Support Chat or in-product support. WHAT WE ARE DOING We recognize the severity of this situation and the impact it may have on your workloads. The situation continues to evolve, and we are closely monitoring AWS status and regional health signals. We are validating Atlas behavior across affected and unaffected regions, and working to mitigate customer impact where possible. We will provide further updates as circumstances continue to change.

6. identified Mar 02, 2026, 07:58 PM UTC

   CURRENT IMPACT According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. AWS is currently experiencing infrastructure impairments in two Middle East regions: * ME-CENTRAL-1 (Middle East – Central): Two Availability Zones are impaired due to an underlying power and facilities issue. This is resulting in elevated error rates and latency across several AWS services. Recovery is currently expected to take at least a day, per AWS. * ME-SOUTH-1 (Middle East – Bahrain): A single Availability Zone is experiencing a localized power issue. While some services have shifted traffic to unaffected Availability Zones, resources deployed in the impacted zone may continue to experience availability issues, elevated error rates, or extended recovery timelines. Recovery is also currently expected to take at least a day. Because MongoDB Atlas runs on AWS infrastructure, Atlas clusters deployed in the affected Availability Zones may be unavailable or experience operational impact, and certain Atlas management operations (including the Atlas UI, API, and CLI) may show increased error rates during this time. The impact of these events depends on your Atlas cluster topology and configuration: * Customers using multi–region deployments, global clusters, or replicas located in unaffected Availability Zones or regions may see little to no impact. * Customers with clusters or workloads primarily located in the affected Availability Zones may experience reduced availability or degraded performance. * Clusters deployed entirely in unaffected Availability Zones or outside the impacted regions are operating normally. AVAILABLE OPTIONS Depending on your application requirements and cluster configuration, you may consider the following options: 1. Move the cluster to another region that is not impacted. 2. Add electable nodes in another region, which can enable the cluster to establish a minimum viable topology and restore database operations. 3. Take no action and wait for the affected Availability Zones to be fully recovered. HOW TO GET HELP If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

7. identified Mar 03, 2026, 05:20 PM UTC

   According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 00:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

8. identified Mar 03, 2026, 10:54 PM UTC

   According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 06:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

9. identified Mar 04, 2026, 06:03 AM UTC

   According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 12:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

10. identified Mar 04, 2026, 04:33 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 5 at 12:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

11. identified Mar 05, 2026, 02:59 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 6 at 14:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

12. identified Mar 06, 2026, 02:24 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 7 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

13. identified Mar 07, 2026, 03:28 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 8 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

14. identified Mar 08, 2026, 03:42 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 9 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

15. identified Mar 09, 2026, 04:02 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 10 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

16. identified Mar 10, 2026, 03:59 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 11 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

17. identified Mar 11, 2026, 03:48 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We expect our guidance to remain unchanged for the immediate future. We will move to a weekly status post update cadence, and provide another update by March 18 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

18. monitoring Mar 18, 2026, 03:51 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We expect our guidance to remain unchanged for the immediate future. We will continue with a weekly status post update cadence, and provide another update by March 25 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

19. monitoring Mar 25, 2026, 03:33 PM UTC

    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We expect our guidance to remain unchanged for the immediate future. We will continue with a weekly status post update cadence, and provide another update by April 1 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

20. monitoring Mar 26, 2026, 09:35 PM UTC

    Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, clusters in me-south-1 cannot be modified and may be unable to process normal operations. We strongly recommend that customers with workloads in the affected regions act now to move their clusters to alternate regions instead of waiting for full availability to be restored. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 and me-south-1 as needed. We will continue with a weekly status post update cadence, and provide another update by April 1 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

21. monitoring Apr 01, 2026, 04:02 PM UTC

    Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will continue with a weekly status post update cadence, and provide another update by April 8 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

22. monitoring Apr 08, 2026, 03:33 PM UTC

    Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will continue with a monthly status post update cadence, and provide another update by May 6 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

23. monitoring May 06, 2026, 04:02 PM UTC

    AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will continue with a monthly status post update cadence, and provide another update by June 3 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

24. monitoring Jun 03, 2026, 03:46 PM UTC

    AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will move to an as-needed status post update cadence as new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

25. resolved Sep 03, 2026, 04:47 PM UTC

    While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status We will update this post as necessary. Thanks in advance for your understanding.

Read the full incident report →

Started Feb 28, 2026, 07:53 PM UTC· resolved Mar 02, 2026, 03:05 AM UTC

1. investigating Feb 28, 2026, 07:53 PM UTC

   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.

2. monitoring Mar 01, 2026, 05:37 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 02, 2026, 03:05 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 07:21 PM UTC· resolved Feb 26, 2026, 08:04 PM UTC

1. investigating Feb 26, 2026, 07:21 PM UTC

   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.

2. monitoring Feb 26, 2026, 07:51 PM UTC

   A fix has been implemented and we're monitoring the results.

3. resolved Feb 26, 2026, 08:04 PM UTC

   The issue has been resolved

Read the full incident report →

Started Feb 19, 2026, 06:50 PM UTC· resolved Feb 20, 2026, 04:59 PM UTC

1. investigating Feb 19, 2026, 06:50 PM UTC

   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

2. investigating Feb 19, 2026, 09:35 PM UTC

   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.

3. monitoring Feb 20, 2026, 04:54 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 20, 2026, 04:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 13, 2026, 04:11 PM UTC· resolved Feb 13, 2026, 05:57 PM UTC

1. investigating Feb 13, 2026, 04:11 PM UTC

   We are investigating an issue with DNS resolution for public IP addresses within 31.89.0.0/24. We are engaging with AWS support to remediate the situation.

2. identified Feb 13, 2026, 04:42 PM UTC

   We have identified the root cause and are working on backfilling those records with AWS support. We have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.

3. resolved Feb 13, 2026, 05:57 PM UTC

   The DNS records have been backfilled and clusters that had these IP addresses should be recovered.

Read the full incident report →