MongoDB Cloud Status

Monitoring: 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

Monitoring: 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

Monitoring: 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

Monitoring: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Resolved: This incident has been resolved.

Monitoring: 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.

Identified: 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.

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

Identified: 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.