Update - 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.
Mar 02, 2026 - 16:17 UTC
Update - 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.
Mar 02, 2026 - 02:17 UTC
Update - 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.
Mar 01, 2026 - 19:30 UTC
Update - 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.
Mar 01, 2026 - 14:55 UTC
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.
Mar 01, 2026 - 13:48 UTC
MongoDB Cloud
Operational
MongoDB Support Portal
Operational
MongoDB Atlas App Services and Device Sync
Operational
MongoDB Atlas Data Federation and Online Archive
Operational
Please note that this is courtesy notice and no action is required from you if you do not pin intermediate certificates from Let's Encrypt (LE) and/or Google Trust Services (GTS) in your environment when connecting to Atlas dedicated clusters.
Let's Encrypt (LE) and Google Trust Services (GTS) have issued additional intermediate certificates to their services. Intermediate certificates act as a secure bridge between root CAs (e.g. LE/GTS) and end entities to streamline management and reduce risk. We want to emphasize that the changes mentioned below related to intermediate certificate authority are not made by MongoDB but by LE and GTS sometime in 2026 which are the Certificate Authority (CA) providers for TLS certificates for all MongoDB Atlas clusters.
Resolved -
This incident has been resolved. Email notifications are being sent successfully.
Mar 2, 16:28 UTC
Investigating -
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.
Mar 2, 15:50 UTC
Resolved -
This incident has been resolved.
Mar 2, 03:05 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 1, 05:37 UTC
Investigating -
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.
Feb 28, 19:53 UTC
Resolved -
The issue has been resolved
Feb 26, 20:04 UTC
Monitoring -
A fix has been implemented and we're monitoring the results.
Feb 26, 19:51 UTC
Investigating -
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.
Feb 26, 19:21 UTC