Incident History

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

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.

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.

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.

This incident has been resolved.

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

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

This incident has been resolved.