MongoDB Atlas Outage History
Uptime record, past incidents, and downtime history for MongoDB Atlas.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 0% | 10 | 10 |
| March 2026 | 22.6% | 31 | 24 |
| February 2026 | 69.6% | 23 | 7 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 64 Days)
Feb 6
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
March 2026
Delays in cluster creation and adding new cluster nodes in Azure East US 2 region
Started: Mar 30, 9:47 PM
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.
Mar 30, 9:47 PM
Intermittent 503 Errors on Atlas Admin API and Automation Tooling
Started: Mar 25, 9:31 PM
monitoring
We continue to monitor our systems for intermittent spikes in 503 HTTP errors following our deployed fix. We will provide another update tomorrow by 3 PM UTC.
Mar 26, 7:12 PM
monitoring
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
Mar 25, 11:39 PM
investigating
We are currently investigating intermittent spikes of HTTP 503 errors affecting Atlas control plane operations performed via the Atlas Admin API and automation tooling such as Terraform. Impacted requests typically fail for a short period and succeed on retry. Atlas database connectivity and data plane operations remain healthy.
Our engineering teams are working to resolve the issue with high urgency and to prevent recurrence. Customers encountering 503 responses are advised to retry failed ...
Mar 25, 9:31 PM
Issue querying Azure blob storage containers in Atlas Data Federation
Started: Mar 19, 6:11 PM
monitoring
We are continuing to monitor for any further issues.
Mar 19, 7:14 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 19, 7:01 PM
identified
The issue has been identified and we are working on a fix.
Mar 19, 6:25 PM
investigating
We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.
Mar 19, 6:11 PM
MongoDB Atlas: Clusters page failing to load
Started: Mar 19, 2:42 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 19, 3:17 PM
identified
We have identified an issue affecting the Clusters page in MongoDB Atlas. Affected users may see a blank page when trying to view their Clusters page.
Cluster health is unaffected.
Mar 19, 2:42 PM
MongoDB Atlas for Government: SSO login failures for some users
Started: Mar 19, 12:24 AM
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.
Mar 19, 10:15 PM
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...
Mar 19, 12:24 AM
Cluster Provisioning Impaired in Azure Virginia-East2 (eastus2)
Started: Mar 14, 1:50 AM
identified
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 miti...
Mar 14, 1:59 AM
investigating
We are experiencing high failure rates when provisioning clusters in Azure Virginia-East2 (eastus2). Please note that cluster creation in this region will likely experience delays until the issue is resolved.
Mar 14, 1:50 AM
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
Started: Mar 1, 7:30 PM
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. Ther...
Apr 8, 3:33 PM
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. Ther...
Apr 1, 4:02 PM
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 wor...
Mar 26, 9:35 PM
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 appropr...
Mar 25, 3:33 PM
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 ...
Mar 18, 3:51 PM
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 ...
Mar 11, 3:48 PM
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 ...
Mar 10, 3:59 PM
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 ...
Mar 9, 4:02 PM
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 ...
Mar 8, 3:42 PM
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 Marc...
Mar 7, 3:28 PM
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 ...
Mar 6, 2:24 PM
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 ...
Mar 5, 2:59 PM
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 app...
Mar 4, 4:33 PM
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 app...
Mar 4, 6:03 AM
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 app...
Mar 3, 10:54 PM
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 app...
Mar 3, 5:20 PM
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 elev...
Mar 2, 7:58 PM
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....
Mar 2, 9:20 AM
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.
Mar 2, 2:17 AM
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.
Mar 1, 7:30 PM
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 Dash...
Mar 1, 2:55 PM
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 f...
Mar 1, 1:48 PM