Atlas Clusters Snapshot Failures
This incident has been resolved.
This incident has been resolved.
This incident has been resolved. Email notifications are being sent successfully.
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:
This incident has been resolved.
The issue has been resolved
This incident has been resolved.
The DNS records have been backfilled and clusters that had these IP addresses should be recovered.
We have identified and resolved the issue. Atlas UI will load without a delay now.
This incident has been resolved.
Many nodes have recovered in the impacted region, however there are still some impacted nodes that are recovering. Azure's latest update at 11:05 UTC on 07 February 2026 indicates they are observing signs of partial recovery and that recovery efforts remain in progress.
We are resolving the status post as we expect our system to automatically remediate any lingering issues. Please follow the Azure status post for further updates on the regional outage remediation efforts from their end.