Azure has an active service issue for virtual machines in East US 2. According to their service health page, "customers using Virtual Machines in East US 2 may have encountered errors when performing service management operations - such as create, update, scale, or start - for resources in this region. [...] During peak impact, an unexpected surge in usage caused backend Virtual Machine components to reach operational limits, resulting in deployment failures for some VMs. We are actively mitigating through load balancing and resource reclamation. Capacity constraints for affected SKUs persist, and our teams continue working to restore normal levels."

We are actively engaging with Azure support.

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