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
May 2026	0%	25	25
April 2026	0%	30	30
March 2026	22.6%	31	24
February 2026	60%	5	2

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today

Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026

Authentication failures when running search queries for some clusters

minor

Started: May 23, 7:48 PM

monitoring

We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.

May 24, 12:14 AM

identified

We have identified the root cause of the search query failures and are working on a mitigation for impacted clusters. Clusters with dedicated search nodes are unaffected. Some clusters with colocated search nodes may see search query failures.

May 23, 8:14 PM

investigating

We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.

May 23, 7:48 PM

[Atlas for Government] Data plane node logs unavailable for last 6 days

minor

Started: May 22, 8:32 PM

monitoring

We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.

May 22, 9:17 PM

investigating

The data plane node logs (mongod, audit logs, etc.) are unavailable since May 14th 4am UTC for clusters in GCP and AWS gov-cloud regions. We have identified the root cause and are actively working on a fix.

May 22, 8:32 PM

Impaired Cluster Operations due to Lets Encrypt Outage

minor

Started: May 8, 7:33 PM

monitoring

Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state.

May 8, 9:39 PM

monitoring

Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.

May 8, 7:33 PM

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

minor

Started: May 8, 2:24 AM

monitoring

AWS continues to work towards full recovery. The Atlas system has been successfully taking healing actions on impacted nodes to restore node health and using healthy availability zones for provisioning new nodes. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.

May 8, 8:41 PM

monitoring

AWS continues to make progress to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.

May 8, 12:34 PM

monitoring

AWS Availability Zone use1-az4 in US-EAST-1 region is still impaired and AWS is working to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.

May 8, 3:12 AM

identified

AWS Availability Zone use1-az4 in US-EAST-1 region is impaired. For some clusters in AWS US-EAST-1 region, cluster nodes in that availability zone may have impaired health. Some Atlas operations, including instance scaling and cluster configuration changes, may also be delayed for clusters in AWS US-EAST-1. Please see https://health.aws.amazon.com/health/status for more information.

May 8, 2:24 AM

AWS Cluster DNS Changes Degraded Performance

major

Started: May 7, 3:17 PM

monitoring

We are continuing to monitor for any further issues.

May 7, 7:47 PM

monitoring

We've identified a bad piece of metadata causing DNS issues. We've since patched this metadata and are seeing recovery in ACME updates for cluster topology changes. We will continue to monitor recovery.

May 7, 7:47 PM

investigating

We are still seeing cases where new cluster update requests are failing to go through due to ACME related DNS issues. We are actively investigating this issue.

May 7, 5:50 PM

identified

Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.

May 7, 4:58 PM

identified

DNS changes for AWS clusters are currently degraded. Cluster topology modifications may be delayed or not able to complete successfully. We've identified the issue and are pushing out a patch.

May 7, 3:20 PM

identified

DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.

May 7, 3:17 PM

Atlas Backup Export Jobs Degraded Performance

minor

Started: May 6, 9:48 PM

monitoring

A fix has been implemented and we are monitoring the results.

May 7, 8:02 PM

identified

We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.

May 7, 1:20 AM

identified

Identified - We have identified an issue causing failures for a subset of Atlas backup export jobs. We are actively working on a fix. Your cluster health and data are unaffected. We will provide another update by May 7 01:30 UTC

May 6, 9:48 PM

Partial outage in Azure West Europe

Started: May 3, 5:33 PM

monitoring

We're starting to see instances recover. We will continue to monitor the region's status in Azure and ensure Atlas takes any available steps to maintain cluster health.

May 3, 8:19 PM

investigating

We are observing widespread issues in in Azure West Europe. Customers may see nodes reporting as "down" and delayed cluster modifications for Azure clusters in West Europe. There are three total AZs in Azure West Europe, and primary failover will be handled by MongoDB.

May 3, 5:33 PM

April 2026

Increase in Billing for Backup Usage

major

Started: Apr 27, 5:16 PM

identified

We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 27 a...

Apr 27, 5:16 PM

MongoDB Atlas BI Connector: Connections and queries fail

major

Started: Apr 17, 5:03 PM

monitoring

A fix has been implemented and we are monitoring the results. The launch of the fix should be complete by approximately 13:00 UTC 21 April 2026.

Apr 20, 7:17 PM

identified

We have identified the issue affecting the Business Intelligence (BI) Connector in MongoDB Atlas for Government. We are working on a fix. While no workaround exists, data remains accessible to MongoDB clients. Affected users will not be able to connect to their clusters' BI Connectors. Cluster health is unaffected.

Apr 17, 8:24 PM

investigating

We are currently investigating reports in MongoDB Atlas for Government that the Business Intelligence Connector (BI Connector) is failing. Affected users will have issues connecting to and querying their BI Connectors. No workaround has been identified at this time. Underlying cluster health is not affected.

Apr 17, 5:03 PM

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

major

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

major

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

major

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

minor

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)

major

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)

major

Started: Mar 1, 7:30 PM

monitoring

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. T...

May 6, 4:02 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

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

Mar 11, 3:48 PM

identified

Mar 10, 3:59 PM

identified

Mar 9, 4:02 PM

identified

Mar 8, 3:42 PM

identified

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

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

View live status for MongoDB Atlas Browse all services