MongoDB Atlas

Affected: MongoDB Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. identified 2026-10-20 07:32 UTC

   Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP europe-west2-b. Atlas clusters are distributed across multiple AZs and 3-node clusters can continue to serve reads and writes from nodes in the other 2 Availability Zones...

2. identified 2026-10-20 08:38 UTC

   The Google Cloud status page has been updated to report further information, follow this link for details https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj

3. monitoring 2026-10-20 11:43 UTC

   We are seeing signs of Availability Zone connectivity improving and are continuing to monitor.

4. resolved 2026-10-20 20:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Search

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 16:29 UTC

   Ongoing Atlas Search incident known to cause mongot crashes, potential search and vector search outage, impacting a subset of search and vector search users in the Atlas fleet. We have identified the issue and are working on a fix.

2. identified 2026-10-09 16:30 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-09 17:09 UTC

   A fix has been deployed and we are monitoring.

4. resolved 2026-10-09 18:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 13:11 UTC

   We are seeing elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. Users may experience intermittent failures when making API calls. We are investigating the root cause and will share another update as our investigation continues.

2. monitoring 2026-10-09 14:43 UTC

   We have deployed a mitigation for the elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. We are seeing signs of recovery and are monitoring the service to confirm the issue does not recur before resolving this incident.

3. resolved 2026-10-09 15:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Charts

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-02 00:01 UTC

   Since approximately 23:30 UTC on 2026-10-01, users creating new Charts projects by clicking on the "Visualization" tab will repeatedly be prompted to login and will not be able to view the Charts interface. While these Charts projects will be created, we cannot guarantee the...

2. resolved 2026-10-02 05:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas App Services and Device Sync

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 15:41 UTC

   As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.

2. investigating 2026-10-01 18:21 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-01 19:51 UTC

   Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.

4. monitoring 2026-10-01 19:59 UTC

   Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.

5. resolved 2026-10-01 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-30 18:51 UTC

   We are investigating an issue with Atlas metrics ingestion that may delay cluster management operations, including cluster creation and modification.

2. identified 2026-09-30 19:01 UTC

   We've identified an issue with metric ingestion that is causing delays to Atlas Cluster management operations for some customers. Clusters may also appear degraded in the Atlas UI while metrics ingestion is delayed; however, the cluster health is unaffected.

3. monitoring 2026-09-30 19:26 UTC

   The team has implemented a fix and latency of Atlas Cluster management operations are returning to normal. Clusters that incorrectly appeared as degraded in the Atlas UI are also beginning to correctly update their status.

4. resolved 2026-09-30 21:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Support Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 09:06 UTC

   MongoDB customers are currently experiencing degraded or limited access to the MongoDB Customer Support Portal (https://support.mongodb.com/). If you require assistance with a critical MongoDB Technical Support issue and are unable to access the Customer Support Portal, please...

2. investigating 2026-09-16 09:09 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-16 15:31 UTC

   The MongoDB Support Portal experienced service degradation issues between approximately 2026-09-16 09:00 UTC and 2026-09-16 15:15 UTC. These platform issues have been resolved. We apologize for the service interruption and greatly appreciate your patience. Regards, The MongoDB...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-11 01:28 UTC

   We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.

2. monitoring 2026-09-11 02:01 UTC

   Atlas is seeing elevated errors rates of certificate issuance due to a Let's Encrypt outage (https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/6aa35c1d892d7304f2747e01). Free and flex tier cluster provisioning may be delayed.

3. resolved 2026-09-11 03:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Names an upstream provider: AWS.

1. monitoring 2026-09-03 16:44 UTC

   Please follow the original status post for updates on AWS me-central-1 and AWS me-south-1 issues.

2. monitoring 2026-09-03 16:47 UTC

   We are continuing to monitor for any further issues.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-28 14:30 UTC

   Between approximately 14:29 UTC and 15:42 UTC on August 28, 2026, log delivery via Atlas Log Integration was impacted due to an internal service issue. Some users may have encountered delayed or missing logs during this window. Log delivery has since returned to normal. We are...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-19 20:45 UTC

   We have identified an issue impacting certain projects containing only Free or Flex clusters. For those clusters, TLS certificates are not being rotated correctly. This could lead to an inability to connect to your Free or Flex cluster. We are working on remediation steps.

2. monitoring 2026-08-19 21:50 UTC

   We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.

3. monitoring 2026-08-19 21:57 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-08-19 21:58 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-08-19 22:00 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2026-08-20 21:39 UTC

   We have deployed fix, continuing the monitor for any further issues.

7. resolved 2026-08-20 22:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Traffic surge or denial-of-service attack. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-18 14:10 UTC

   We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.

2. identified 2026-08-18 14:57 UTC

   We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.

3. monitoring 2026-08-18 15:04 UTC

   We have disabled the workload and are monitoring the situation

4. resolved 2026-08-18 15:17 UTC

   This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-05 05:17 UTC

   We are investigating an issue with Google Cloud Platform (GCP) capacity that is affecting some MongoDB Atlas customers across multiple GCP regions and geographies. We expect the scope of this issue to continue to expand as our investigation progresses. It currently includes, but...

2. resolved 2026-08-05 12:14 UTC

   We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information as we get it, but for now resolving this incident as Atlas is fully operational.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: VoyageAI Embedding and Reranking Models

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-03 18:47 UTC

   VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.

2. monitoring 2026-08-03 19:02 UTC

   A fix has been applied and we are monitoring the system.

3. resolved 2026-08-03 21:18 UTC

   The system has returned to normal operation.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 18:55 UTC

   We are investigating an issue with cluster configuration updates getting delayed for a subset of users on free and flex tiers. Cluster access is unaffected.

2. identified 2026-07-29 19:06 UTC

   We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.

3. monitoring 2026-07-29 19:31 UTC

   We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.

4. resolved 2026-07-29 19:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Stream Processing

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-07-29 18:11 UTC

   We are investigating an issue affecting Atlas Stream Processing in Azure West Europe. Some users may see processors in this region encounter internal errors. We are actively investigating and will share another update as soon as we have more information.

2. monitoring 2026-07-29 22:35 UTC

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

3. resolved 2026-07-29 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: VoyageAI Embedding and Reranking Models

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 23:37 UTC

   All VoyageAI models are experiencing elevated errors. We are investigating the issue.

2. investigating 2026-07-27 23:47 UTC

   We have fully recovered as of 16:41 PST.

3. resolved 2026-07-27 23:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network connectivity – Issues accessing resources in West US.

1. investigating 2026-07-23 16:21 UTC

   We are currently investigating an issue with Azure clusters in westus region. Please refer to the azure status post here for more information https://azure.status.microsoft/en-us/status.

2. identified 2026-07-23 16:38 UTC

   Azure has confirmed that there are networking issues in the westus region. Please follow the official azure status post for more detailed updates https://azure.status.microsoft/en-us/status

3. identified 2026-07-23 18:26 UTC

   We are aware of an ongoing Azure networking incident affecting the West US region. Some Atlas clusters hosted in Azure West US may experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes...

4. identified 2026-07-23 18:54 UTC

   Azure is rolling out a mitigation for the ongoing networking incident affecting the West US region, and we are seeing signs of recovery. Some Atlas clusters hosted in Azure West US may continue to experience intermittent connectivity issues, including failures connecting to...

5. resolved 2026-07-23 20:28 UTC

   Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-07-17 16:14 UTC

   Due to an ongoing incident with AWS's billing data, MongoDB Atlas and Atlas for Government will not be updating AWS network or backup consumption data over this weekend, 2026-07-17 through 2026-07-20. The products themselves will remain fully available. When the upstream issue...

2. monitoring 2026-07-20 15:06 UTC

   The upstream issue has been corrected. After approximately 0400 UTC on 2026-07-21, most, if not all, of the updated backup and network consumption on AWS will be reflected in MongoDB Atlas and Atlas for Government. Thank you for your patience during this incident.

3. resolved 2026-07-21 13:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Stream Processing

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-07-09 23:03 UTC

   We are currently investigating an issue affecting Stream Processing Azure West Europe. User initiated commands & workloads may see intermittent failures.

2. monitoring 2026-07-10 00:32 UTC

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

3. resolved 2026-07-10 01:11 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-09 19:37 UTC

   We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.

2. monitoring 2026-07-09 21:22 UTC

   We are no longer seeing failures with cert issuance from Lets Encrypt. We are still investigating the root cause of the original errors and will continue to monitor.

3. resolved 2026-07-10 14:56 UTC

   Let's Encrypt service has returned to normal.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Data Federation and Online Archive

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-09 10:23 UTC

   Users of Atlas Data Federation and Online Archive using cloud-provider IAM authentication may see pipelines fail with an error when querying backing Atlas clusters. Other authentication methods are unaffected. As a temporary workaround, users can use SCRAM authentication.

2. identified 2026-07-09 10:57 UTC

   We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.

3. monitoring 2026-07-09 11:01 UTC

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

4. resolved 2026-07-09 11:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-02 23:09 UTC

   We are currently monitoring the status of Lets Encrypt after an issue with their API. Tenant clusters and Atlas for Government clusters will experience delays in provisioning due to Lets Encrypt service degradation.

2. resolved 2026-07-02 23:36 UTC

   Let's Encrypt services have returned back to normal. Cluster operations have now returned to normal.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-02 19:34 UTC

   We are currently monitoring the status of Lets Encrypt. Tenant clusters and Atlas for Government clusters will experience delays in provisioning due to Lets Encrypt service degradation.

2. resolved 2026-07-02 21:06 UTC

   We've confirmed that Lets Encrypt has returned to normal operations. Cluster operations are now back to normal.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-02 10:45 UTC

   We are currently investigating the issue where AWS cluster backup and restores are failing. This includes exports and manual downloads as well as restoring to another cluster. We are also investigation potential impact to other operations on AWS clusters such as modifying...

2. monitoring 2026-07-02 10:50 UTC

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

3. resolved 2026-07-02 11:09 UTC

   This incident has been resolved. AWS clusters should no longer encounter errors during backup and restore.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-25 10:16 UTC

   From 2026-06-25 06:55 UTC to 2026-06-25 07:10 UTC, some users may have experienced intermittent Atlas UI loading failures. We identified elevated traffic to a number of endpoints that increased latency in the Atlas UI service. This caused internal health checks to fail and...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-04 15:33 UTC

   A fix has been implemented and we are monitoring the results

2. resolved 2026-06-04 17:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Data Federation and Online Archive

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-02 23:00 UTC

   We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions

2. identified 2026-06-02 23:42 UTC

   We've identified an issue with networking in GCP regions and are working on fix

3. identified 2026-06-03 00:01 UTC

   Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.

4. monitoring 2026-06-03 00:05 UTC

   All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.

5. resolved 2026-06-03 00:11 UTC

   Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas for Government

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 22:02 UTC

   Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration. We are investigating this issue.

2. resolved 2026-05-28 23:15 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas Search

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-23 19:48 UTC

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

2. identified 2026-05-23 20:14 UTC

   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.

3. monitoring 2026-05-24 00:14 UTC

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

4. resolved 2026-05-24 02:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas for Government

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS, Google Cloud.

1. investigating 2026-05-22 20:32 UTC

   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.

2. monitoring 2026-05-22 21:17 UTC

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

3. resolved 2026-05-22 22:17 UTC

   The data plane node log download has recovered.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-05-08 19:33 UTC

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

2. monitoring 2026-05-08 21:39 UTC

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

3. resolved 2026-05-08 22:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-08 02:24 UTC

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

2. monitoring 2026-05-08 03:12 UTC

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

3. monitoring 2026-05-08 12:34 UTC

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

4. monitoring 2026-05-08 20:41 UTC

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

5. resolved 2026-05-09 14:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas for Government

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-07 15:17 UTC

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

2. identified 2026-05-07 15:20 UTC

   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.

3. identified 2026-05-07 16:58 UTC

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

4. investigating 2026-05-07 17:50 UTC

   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.

5. monitoring 2026-05-07 19:47 UTC

   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.

6. monitoring 2026-05-07 19:47 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-05-07 22:15 UTC

   DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud, MongoDB Atlas for Government

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-06 21:48 UTC

   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

2. identified 2026-05-07 01:20 UTC

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

3. monitoring 2026-05-07 20:02 UTC

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

4. resolved 2026-05-07 20:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-03 17:33 UTC

   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.

2. monitoring 2026-05-03 20:19 UTC

   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.

3. resolved 2026-05-05 17:28 UTC

   We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-27 17:16 UTC

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

2. resolved 2026-04-27 20:50 UTC

   We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas for Government

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-17 17:03 UTC

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

2. identified 2026-04-17 20:24 UTC

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

3. monitoring 2026-04-20 19:17 UTC

   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.

4. resolved 2026-04-21 13:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Charts

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-01 12:55 UTC

   Some Atlas users may be unable to access Charts and the Visualization page due to repeated login prompts or unauthorized errors when attempting to sign in. Our engineers have identified a recent change as the likely cause, have rolled it back, and are monitoring the service to...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-03-30 21:47 UTC

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

2. resolved 2026-03-30 23:10 UTC

   We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-25 21:31 UTC

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

2. monitoring 2026-03-25 23:39 UTC

   The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.

3. monitoring 2026-03-26 19:12 UTC

   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.

4. resolved 2026-03-27 13:21 UTC

   We are no longer seeing intermittent spikes in HTTP 503 errors.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Data Federation and Online Archive

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-03-19 18:11 UTC

   We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.

2. identified 2026-03-19 18:25 UTC

   The issue has been identified and we are working on a fix.

3. monitoring 2026-03-19 19:01 UTC

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

4. monitoring 2026-03-19 19:14 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-03-19 19:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-19 14:42 UTC

   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.

2. monitoring 2026-03-19 15:17 UTC

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

3. resolved 2026-03-19 15:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas for Government

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-19 00:24 UTC

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

2. monitoring 2026-03-19 22:15 UTC

   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.

3. resolved 2026-03-31 21:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas Stream Processing

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-03-11 20:10 UTC

   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.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-10 23:18 UTC

   Atlas cluster snapshots are failing. We are actively investigating.

2. identified 2026-03-11 00:45 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-03-11 02:21 UTC

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

4. resolved 2026-03-11 02:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 15:50 UTC

   We are currently investigating this issue. Some users may not be receiving emails from MongoDB. We are looking into the cause and will provide an update as soon as we know more.

2. resolved 2026-03-02 16:28 UTC

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

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-02 12:00 UTC

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

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. identified 2026-03-01 13:48 UTC

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

2. identified 2026-03-01 14:55 UTC

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

3. identified 2026-03-01 19:30 UTC

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

4. identified 2026-03-02 02:17 UTC

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

5. identified 2026-03-02 16:17 UTC

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

6. identified 2026-03-02 19:58 UTC

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

7. identified 2026-03-03 17:20 UTC

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

8. identified 2026-03-03 22:54 UTC

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

9. identified 2026-03-04 06:03 UTC

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

10. identified 2026-03-04 16:33 UTC

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

11. identified 2026-03-05 14:59 UTC

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

12. identified 2026-03-06 14:24 UTC

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

13. identified 2026-03-07 15:28 UTC

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

14. identified 2026-03-08 15:42 UTC

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

15. identified 2026-03-09 16:02 UTC

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

16. identified 2026-03-10 15:59 UTC

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

17. identified 2026-03-11 15:48 UTC

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

18. monitoring 2026-03-18 15:51 UTC

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

19. monitoring 2026-03-25 15:33 UTC

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

20. monitoring 2026-03-26 21:35 UTC

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

21. monitoring 2026-04-01 16:02 UTC

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

22. monitoring 2026-04-08 15:33 UTC

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

23. monitoring 2026-05-06 16:02 UTC

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

24. monitoring 2026-06-03 15:46 UTC

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

25. resolved 2026-09-03 16:47 UTC

    While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status We will update...

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.

Affected: MongoDB Atlas App Services and Device Sync

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-28 19:53 UTC

   We are currently investigating an issue with Atlas App Services Device Sync. Affected users of this deprecated service may see SSL validation errors. We will update this post with more details as they become available.

2. monitoring 2026-03-01 05:37 UTC

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

3. resolved 2026-03-02 03:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on MongoDB Atlas's status page.