Is MongoDB Cloud Down Right Now? Check if there is a current outage ongoing.

We are investigating a situation where backup restores are intermittently failing.

We've identified an issue with increased 503's coming from GCP. We are working directly with the cloud provider to identify the root cause. Cluster health is unaffected. GCP Cluster modification will be delayed at this time.

We've identified an issue where the system will send maintenance notifications too frequently. Cluster health is unaffected. We're actively working to remediate the situation

We have identified an issue preventing newly-added users (users added since approximately 1400 UTC 6 June 2025) to MongoDB Atlas for Government projects from creating, modifying, or viewing support cases. Affected users will get various authorization failed errors. We encourage them to contact their colleagues to file cases on their behalf.

We have identified an issue with MongoDB Atlas cluster operations and the web UI. Affected users may see timeouts when accessing the control panel or delays in creating or modifying clusters. Existing cluster health is unaffected.

### **Incident Summary** Between May 28th 2025 16:00 UTC and May 28th 2025 19:36 UTC, emails were sent out to users on affected orgs notifying them that they have been moved into the locked status and users from all affected orgs were restricted from performing any actions on their organization. ### **Root Cause** The root cause of this incident was an outdated internal process that was inadvertently re-enabled during a database migration. ### **MongoDB Actions** The MongoDB Atlas Billing team has deleted the outdated process and increased alerting on changes in dunning statuses. ### **Recommended Customer Actions** This issue was fully addressed by the MongoDB Atlas Billing team and does not require customer action.

This incident has been resolved.

All locked organizations have been unlocked. A small number of organizations still have some repairs being performed to their support plans. Regardless, all affected organizations should have full access to their Atlas UI/API.

Virtually all locked organizations have been unlocked. Clusters in organizations that were locked were not terminated, and neither was their IP access list deleted.

Some locked organizations have been unlocked. We are continuing to unlock affected organizations. Clusters in affected organizations have not been terminated.

We have identified the issue and are working towards a resolution. Networks Access Lists have not been removed from affected accounts. Clusters from locked accounts have not been terminated.

We're aware that a small number of accounts have been temporarily locked out. Our team is actively working to resolve the issue. Clusters from locked out accounts have not been terminated.

From approximately 13:40 to 17:20 UTC on 3 June 2025, MongoDB Atlas was unable to send metrics via Datadog's EU region for some Atlas Projects. Affected users may find gaps during this time in less than half of their metrics if they use Datadog's EU servers. These gaps will not be backfilled. Cluster health was unaffected, however, alerts may have fired within Datadog – we do not have visibility to this.

From approximately 13:40 to 17:20 UTC on 3 June 2025, MongoDB Atlas was unable to send metrics via Datadog's EU region for some Atlas Projects. Affected users may find gaps during this time in less than half of their metrics if they use Datadog's EU servers. These gaps will not be backfilled.Cluster health was unaffected, however, alerts may have fired within Datadog – we do not have visibility to this.

We're aware that a small number of accounts have been temporarily locked out. Our team is actively working to resolve the issue. Clusters from locked out accounts have not been terminated.

This incident has been resolved.

The system has returned to normal operations. We continue to monitor.

We have identified and mitigated the cause of the delays. System is returning to normal operations.

We continue to see delays in Atlas cluster creation, modification, and scheduled backup actions. These operations are completing but with delays. We continue to investigate the issue.

We are seeing delays in Atlas cluster creation, modification, and scheduled backup actions. We are investigating the issue.

We are seeing delays in Atlas cluster creation, modification, and scheduled backup actions. We are investigating the issue.

Between 18:37 and 21:17 UTC on 16 May 2025, MongoDB Atlas sent out false Host Down alerts to a small portion of our users. Cluster health was unaffected during this time and we sincerely apologize for the confusion.

On or around 18:37 UTC on 16 May 2025, MongoDB Atlas sent out false Host Down alerts to a small portion of our users. Cluster health was unaffected during this time and we sincerely apologize for the confusion.

This incident has been resolved.

Affected clusters have remained reachable since the upstream configuration change was deployed. We will continue to monitor for regressions.

Azure and ISP partners have applied a configuration change and we are observing connectivity restoration in South Africa West and South Africa North. Atlas engineers are continuing to monitor the situation.

Azure has identified the root cause of the issue and has escalated the issue to the ISP impacting connectivity. At this point in time there is no ETA to resolution.

Due to ongoing issues, Atlas Clusters in Azure South Africa West and Azure South Africa North may experience delays creating, modifying, or executing scheduled actions such as backups. Atlas Clusters will continue to show degraded status in the UI.

We are continuing to actively investigate the IP accessibility issues with Azure support. We will provide another status update in at most 8 hours. We will provide a status update earlier if possible as our investigation progresses.

Some Azure external IP address ranges used in the Azure South Africa West and Azure South Africa North regions are currently inaccessible from certain segments of the internet. These networking issues can cause specific Azure public IP ranges to be unreachable from select networks, even though they should be globally routable. We are escalating the issue with Azure and continue to investigate.

Atlas Clusters in Azure South Africa West and Azure South Africa North are still reporting degraded status and we continue to investigate the issue.

Atlas Clusters in Azure South Africa West and Azure South Africa North are reporting degraded status as of 2025-05-13 23:50:00 UTC. We are investigating the issue.

Atlas Clusters in Azure South Africa West and Azure South Africa North are reporting degraded status as of 2025-05-13 23:50:00 UTC. We are investigating the issue.

This incident has been resolved.

We've identified the issue and fixed it. Monitoring now.

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

We are investigating failures of backup restores for Atlas Clusters.

This incident has been resolved.

We've identified the issue and fixed it. Monitoring now.

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

We are investigating failures of backup restores for Atlas Clusters.

The incident is now resolved. Since May 1st 2025 at 04:52 UTC we falsely reported a limited number of Atlas Clusters as down in the UI and alerted as such.

We have identified the root cause for the delays in Atlas metrics processing and have mitigated the issue. Atlas metrics processing is no longer delayed. Clusters are still operational.

We are investigating delayed Atlas metrics processing that can result in host down alerts for Atlas clusters. Clusters are still operational.

We are investigating delayed Atlas metrics processing that can result in host down alerts for Atlas clusters. Clusters are still operational.

Alerting latency is back within expected thresholds.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring results.

We have identified an issue with Cloud Manager and Atlas that is causing alerts to be delayed. Underlying cluster health is unaffected.

We have identified an issue with Cloud Manager and Atlas that is causing alerts to be delayed. Underlying cluster health is unaffected.

This incident has been resolved.

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

We've identified the issue and are working towards a resolution.

We are investigating an issue affecting Cloud Manager and Atlas. Metrics data is delayed and alerting is paused. Cluster health is unaffected, but we may have sent false host down alerts for some clusters.

We are investigating an issue affecting Cloud Manager and Atlas. Metrics data is delayed and alerting is paused. Cluster health is unaffected, but we may have sent false host down alerts for some clusters.

We have confirmed sustained recovery. All systems continue to operate normally.

Our systems have automatically recovered from a transient network connectivity issue. Metrics data is current and alerting is functional. All systems are operating normally. We are continuing to monitor.

We are continuing to investigate this issue.

We are investigating an issue affecting Cloud Manager and Atlas. Metrics data is delayed and alerting is paused. Cluster health is unaffected, but we may have sent false host down alerts for some clusters.

This incident has been resolved.

Alerts processing is enabled and metrics data is being ingested normally. We are continuing to monitor closely to ensure the issue has been successfully mitigated.

We have identified an issue with Cloud Manager and Atlas that is causing alerts to be paused and metrics data to be delayed. Underlying cluster health is unaffected, but we may have sent false host down alerts for some clusters.

We have identified an issue with Cloud Manager and Atlas that is causing alerts to be paused and metrics data to be delayed. Underlying cluster health is unaffected, but we may have sent false host down alerts for some clusters.

(This maintenance was originally scheduled for 2PM UTC but was forced to be delayed due to unforeseen circumstances.)MongoDB Atlas will be undergoing planned maintenance on April 5th at 8 PM UTC, 2025. During this 30-minute maintenance window, certain internal Atlas and cluster management operations will be delayed.*FAQ*- Will my clusters be affected during the maintenance?No customer clusters will be affected during this time and they will be functioning as normal during the maintenance. Only Atlas Admin functionality will be impacted.- Will my data be affected during the maintenance?No customer data will be affected.- Will the Admin APIs be down during the maintenance?Admin API side effects may be delayed.- Do I have to take any actions on my account?No action is required. However, if you plan to perform cluster modifications, we recommend scheduling them before or after the maintenance window.- I need to perform a change as soon as possible, what can I do?If possible, please try and perform the change before or after the maintenance window.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We have received confirmation that this issue has been resolved by taking a host offline in the AWS network that was causing the DNS resolution issues. We also continue to confirm with customers that they are not seeing any residual impacts of this issue. This issue is now resolved.

We are getting confirmation from customers that they have now seen the issue resolve after a host causing DNS resolution issues was taken offline. We continue to work to ensure the issue is fully resolved and monitor the situation.

A host has been taken offline that was suspected to be causing the DNS resolution issues. The issue continues to be looked into to ensure it is fully mitigated. A reproduction of the issue is no longer exhibiting DNS resolution issues. We will be checking in with customers to ensure their intermittent connection issues are fully resolved.

A fix to the issue with the resolver host within the AWS network continues to be worked on. We will provide the next update before 2025/04/02 14UTC.

A resolver host within the AWS network has been identified as the root cause of the failed DNS resolutions. A fix to the issue is being worked on.

DNS Resolution issues at Cloud Provider level resulting in intermittent resolution issues of the Atlas Resources to their Hostname/IP. High Severity case has been filed and additional updates to follow.

We have successfully reproduced the failed DNS resolution from an ec2 instance in Frankfurt (eu-central-1). We are in communication with AWS on the issue.

Our investigation has found an issue with resolving DNS records from certain geographies. We are continuing to investigate to identify which geographies are impacted

We are investigating intermittent connection issues for some clusters in the AWS Frankfurt (eu-central-1) region.

We are investigating intermittent connection issues for some clusters in the AWS Frankfurt (eu-central-1) region.

On 31 March 2025, Atlas will be undergoing maintenance for approximately 10 minutes at 3:30PM UTC. During this time, various operations throughout Atlas will fail, including but not limited to:- Users will be unable to login or sign up to all MongoDB Applications (Cloud, Support, University, etc)- Users will not be able to create Organizations or Projects- Users will not be able to create or edit API Keys- Users are unable to change the roles of existing users or API keys- Push Migrations might encounter errors- Users will not be able to create a Charts ApplicationUsers who are already logged in will remain logged in, but the UI will have issues and might display a maintenance error page.*FAQ*- Will my clusters be affected during the maintenance?No customer clusters will be affected during this time and they will be functioning as normal during the maintenance. Only Atlas functionality will be impacted- Will my data be affected during the maintenance?No customer data will be affected.- Will the Admin APIs be down during the maintenance?Admin APIs will be down, though some operations might still work.- Do I have to take any actions on my account?No actions need to be taken. But, if there needs to be any changes, please do it before or after the maintenance period.- I need to perform a change as soon as possible, what can I do?If possible, please try and perform the change prior to the maintenance window. Once the maintenance is over, you’d also be able to make the change.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This incident has been resolved.

The GCP incident is still ongoing and we continue to see delays in creating and modifying Atlas clusters hosted in the us-east5 region. GCP estimated full recovery may take several hours. For details on the incident, please visit your GCP support cases page.

GCP confirmed there is connectivity issues with multiple Google Cloud services in zone us-east5-c starting at March 29, 2025 at 8:26:32 PM UTC. Due to this customers may experience delays creating and modifying Atlas clusters hosted in this region. For details, please visit your GCP support page.

GCP is not successfully completing request in the us-east5-c zone and we are investigating the issue.

This incident has been resolved.

The GCP incident is still ongoing and we continue to see delays in creating and modifying Atlas clusters hosted in the us-east5 region.GCP estimated full recovery may take several hours. For details on the incident, please visit your GCP support cases page.

GCP confirmed there is connectivity issues with multiple Google Cloud services in zone us-east5-c starting at March 29, 2025 at 8:26:32 PM UTC.Due to this customers may experience delays creating and modifying Atlas clusters hosted in this region.For details, please visit your GCP support page.

GCP is not successfully completing request in the us-east5-c zone and we are investigating the issue.

This incident has been resolved.

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

We are investigating reports of sharded clusters metrics pages resulting in a 404 error in both Cloud Manager and Atlas. This does not affect replica sets, Flex clusters, Serverless, or shared tier clusters. Cluster health is unaffected. As a workaround, users can navigate to their individual shards' metrics pages.

This incident has been resolved.

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

We are investigating reports of sharded clusters metrics pages resulting in a 404 error in both Cloud Manager and Atlas. This does not affect replica sets, Flex clusters, Serverless, or shared tier clusters. Cluster health is unaffected.As a workaround, users can navigate to their individual shards' metrics pages.

This incident has been resolved.

We're seeing the errors subsiding from our TLS provider. We will continue monitoring for any side effects.

We are seeing delays in provisioning new and reconfigured Atlas Cluster nodes as a result of maintenance at our TLS certificate provider. Running clusters should experience no impact from this event. Refer to https://letsencrypt.status.io/ for more information.

This incident has been resolved.

We're seeing the errors subsiding from our TLS provider. We will continue monitoring for any side effects.

We are seeing delays in provisioning new and reconfigured Atlas Cluster nodes as a result of maintenance at our TLS certificate provider. Running clusters should experience no impact from this event. Refer to https://letsencrypt.status.io/ for more information.

This incident has been resolved.

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

We are currently investigating an issue affecting logins for MongoDB properties. This includes Atlas, University, Cloud Manager, and the Support Portal. Atlas clusters and apps are unaffected, as are currently logged-in users.

This incident has been resolved.

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

We are currently investigating an issue affecting logins for MongoDB properties. This includes Atlas, University, Cloud Manager, and the Support Portal.Atlas clusters and apps are unaffected, as are currently logged-in users.

This incident has been resolved.

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

We have identified an issue making cluster configuration changes to M0/M2/M5, Flex, and Serverless clusters. Affected Projects will see the "blue bar" for an extended period of time. This is also impacting the creation of new clusters of those types as well as restores to them. Clusters without changes pending are not affected.

We have identified an issue modifying IP access lists for M0/M2/M5, Flex, and Serverless clusters. Affected Projects will see the "blue bar" for an extended period of time. Clusters without changes pending are not affected.

This incident has been resolved.

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

We have identified an issue making cluster configuration changes to M0/M2/M5, Flex, and Serverless clusters. Affected Projects will see the "blue bar" for an extended period of time. This is also impacting the creation of new clusters of those types as well as restores to them. Clusters without changes pending are not affected.

We have identified an issue modifying IP access lists for M0/M2/M5, Flex, and Serverless clusters. Affected Projects will see the "blue bar" for an extended period of time. Clusters without changes pending are not affected.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

MongoDB Atlas and Cloud Manager will be undergoing planned maintenance on March 20, 2025 at 18:00 UTC. The duration of the maintenance is not expected to exceed thirty minutes. During this time, alerts will not be sent.Your existing Database Deployments, Federated Database Instances, and Online Archives will be queryable throughout the entire duration of the maintenance.

The issue has been resolved.

Atlas for Government control plane is back online. Monitoring.

Existing Atlas database clusters are unaffected. We're continuing to work on control plane remediation.

We have identified the issue with our infrastructure and are working on remediation.

We are currently investigating the issue. The Atlas for Government UI, API, and batch processing services are currently offline. Existing databases should be unaffected.

The issue has been resolved.

Atlas for Government control plane is back online. Monitoring.

Existing Atlas database clusters are unaffected. We're continuing to work on control plane remediation.

We have identified the issue with our infrastructure and are working on remediation.

We are currently investigating the issue. The Atlas for Government UI, API, and batch processing services are currently offline. Existing databases should be unaffected.

Our internal canaries were alerting us to a problem but we are unable to find any customer impact. We are going to continue to investigate but close this as an customer facing event

Users may intermittently be unable to connect to "global" Atlas Data Federation Endpoints. Retrying to connect is advised

A fix has been implemented and deployed

The issue has been identified and a fix is being implemented

We are aware of some pages in the Cloud Manager UI for managing clusters being unavailable. We've identified a fix and are working on restoring access. Cloud Manager Admin API is unaffected Backing cluster health and operations are unaffected.

This incident has been resolved.

We are seeing errors subside from our TLS provider and we will continue monitoring.

We are again seeing delays in provisioning new and reconfigured Atlas Cluster nodes as a result of maintenance at our TLS certificate provider. Running clusters should experience no impact from this event. Refer to https://letsencrypt.status.io/ for more information.

This incident has been resolved.

We're seeing the errors subsiding from our TLS provider. We will continue monitoring for any side effects

We are observing delays in provisioning new and reconfigured Atlas Cluster nodes as a result of maintenance at our TLS certificate provider. Running clusters should experience no impact from this event. Refer to https://letsencrypt.status.io/ for more information.

This incident has been resolved.

We are seeing signs of recovery and continuing active monitoring

Users may see failures when logging into the Atlas web portal (cloud.mongodb.com). We are actively investigating the root cause Programmatic access to the Admin API, and access to backing clusters are unaffected.

This incident has been resolved.

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

We have identified an issue where some users cannot access the MongoDB Atlas App Services and Device Sync UI. Affected users will see many redirects, and their browser may eventually give them the error "Too Many Redirects". The underlying Atlas App Services and Atlas Device Sync are unaffected and continue to work as normal. Users who urgently need to manage their Atlas App Services and Atlas Device Sync settings are encouraged to use the admin API until this is resolved.

We are currently investigating an issue where some customers cannot access the MongoDB Atlas App Services and Device Sync UI due to continuous redirects.

This incident has been resolved.

We have identified the issue and the cluster page in the Atlas UI is now available. We continue to monitor the system and ensure there are no residual issues.

We are investigating an issue with loading the clusters page in the Atlas UI

This incident has been resolved.

We are seeing impacted Atlas nodes in the Azure Italy North region begin to heal. Azure's service health status post remains live. We continue to monitor the situation closely while the Azure status post is live. Please sign into your Azure portal and refer to the internal status page for more information.

We are seeing cluster nodes in Azure Italy North experiencing issues. Please sign into your Azure portal and refer to the internal status page for more information

This incident has been resolved.

The cluster nodes in AWS Stockholm seem to be recovering. We are continuing to monitor that situation as well.

Cluster modifications are no longer delayed. We have implemented a fix and are monitoring

We have identified the cause for the delays in cluster modifications. We are in the process of implementing a fix.

We're continuing to investigate the delays to cluster modification. AWS Stockholm also continues to experience issues and more information on that can be found here https://health.aws.amazon.com/health/status

We are seeing increased errors from AWS Stockholm. Please refer to https://health.aws.amazon.com/health/status for more information

We are currently investigating an issue where we are seeing delayed cluster operations.

This incident has been resolved.

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

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

We are currently investigating this issue.

The root cause was a temporary configuration mismatch that has since been resolved. We expect the system to be fully operational at this time.

We are continuing to investigate this issue.

We are currently investigating an issue that can cause delay to create/delete/modification of MongoDB Atlas Free/M2/M5/Flex/Serverless clusters. The cluster themselves are unaffected and should still be accessible. We will provide more information as they are available.

This incident has been resolved. No user interaction is required to fix the issue. Users who were trying to use Charts may have to refresh the page. Triggers may have been missed during this time for exceptionally busy clusters.

We are continuing to work on a fix for this issue.

We have identified an issue with Database Triggers and Data APIs being unable to connect to their backing cluster. Affected users will find errors in the Charts UI during this time as well as triggers did not complete during this time.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. Some clusters may be missing metrics data, which will not be refilled. Alerts have been re-enabled.

While the Atlas UI and API have returned, metrics data is delayed. Alerts remain paused.

We have identified an issue that is affecting the availability of cloud.mongodb.com, the Atlas Administration API, and alerts. Affected users may see an error page or may take an excessive amount of time to login. Atlas clusters themselves are unaffected, although it might not be possible to create or modify clusters and certain healing operations may be delayed.

We have received reports and can reproduce cloud.mongodb.com failing to load for many users. Atlas Administrative API requests are also failing. Alerts have been paused. We are investigating and will post updates shortly.

We have received reports and can reproduce cloud.mongodb.com failing to load for many users. Atlas Administrative API requests are also failing. We are investigating and will post updates shortly.

We have received reports and can reproduce cloud.mongodb.com failing to load for some users. We are investigating and will post updates shortly.

This incident has been resolved.

We've identified and corrected the issue. Cloud.mongodb.com is no longer returning 500 errors.

We are investigating cloud.mongodb.com returning 500 errors when users navigate to the page. Clusters are not impacted.

Starting at 2025-01-15T01:02:00 UTC some Atlas Serverless instances in AWS Singapore region (ap-southeast-1) experienced downtime. The issue was due to unexpected memory exhaustion of the system that caused outage for a subset of the Atlas infrastructure in that region. A small number of serverless instances running on those infrastructure would have experienced downtime. Our engineers were alerted and the system was restored to health around 2025-01-15T01:44:00 UTC.

Microsoft Azure has updated their status post and indicated that impacted services are now recovered. Atlas cluster operations are no longer experiencing delays. This incident has been resolved.

We continue to keep a close eye on Atlas operations for clusters in the Azure East US2 region while Azure fully mitigates impact from their incident. For details on the Azure incident, please visit your Azure Service Health Dashboard.

The Azure incident is still ongoing and we are seeing delays in creating and modifying Atlas clusters hosted in the East US2 region once again.

The Azure incident is still ongoing. Atlas is operating normally at this time, but we are monitoring the situation closely. For details, please visit your Azure Service Health Dashboard.

Due to Azure networking issues in the East US2 region, customers may experience delays creating and modifying Atlas clusters hosted in this region. For details, please visit your Azure Service Health Dashboard.

This incident has been resolved.

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

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

We are currently investigating an issue where customers cannot access the MongoDB Atlas for Government website.

This incident has been resolved.

We have implemented a fix and are currently monitoring. Alert processing is no longer delayed.

We have implemented a fix and are currently monitoring. Alert processing is still delayed.

We are currently investigating an issue with metrics ingestion. Alerts processing is also delayed.

The fix has been deployed across the fleet and Online Archiving is operating normally.

The fix is being rolled out incrementally over our fleet and we are monitoring the reduction in error rates. We'll provide an update on November 22 at 15:00 UTC. Affected archive runs will appear stuck, with qualifying documents archived and queryable, but not yet purged from the source collection.

We are working to deploy a fix by or before Friday, November 22. We'll provide an update on November 22 at 15:00 UTC. Affected archive runs will appear stuck, with qualifying documents archived and queryable, but not yet purged from the source collection.

We are working to deploy a fix by or before Friday, November 22. We'll provide an update on November 21 at 15:00 UTC. Affected archive runs will appear stuck, with qualifying documents archived and queryable, but not yet purged from the source collection.

We are testing the fix for this issue, but do not yet have an ETA for when it will be resolved. Less than 1% of customer online archives are affected.

We have identified the issue and are implementing a fix.

We are continuing to investigate this issue.

We are currently investigating an issue that may result in interrupted archiving for Online Archive users.

This incident has been resolved.

A fix has been deployed. We are monitoring to confirm the issue is resolved.

We are currently experiencing degraded performance with our Datadog integration and have identified its source. During this time we expect customers will experience missing metrics and issues with alerting for customers using the Datadog integration. A fix is in development and will be released shortly.

This incident has been resolved.

The issue has been identified as a momentary slowdown in an internal Atlas system. Atlas operations are now recovering.

Atlas is seeing elevated errors from our certificate authority Let's Encrypt. Customers may see delayed operations when provisioning new nodes.

This incident has been resolved.

The issue has been identified as a momentary slowdown in an internal Atlas system. Atlas operations are now recovering.

Atlas is seeing elevated errors from our certificate authority Let's Encrypt. Customers may see delayed operations when provisioning new nodes.

This incident has been resolved.

Let's Encrypt is now fully operational (https://letsencrypt.status.io/pages/55957a99e800baa4470002da). Atlas operations are recovering.

Let's Encrypt has identified an issue with their infrastructure causing elevated error rates. Please see the Let's Encrypt status page https://letsencrypt.status.io/pages/55957a99e800baa4470002da for more information.

Atlas is seeing elevated errors from our certificate authority Let's Encrypt (see their status post: https://letsencrypt.status.io/pages/55957a99e800baa4470002da). Customers may see delayed operations when provisioning new nodes.

This incident has been resolved

Login availability has been restored and we are continuing to monitor

We’ve identified the root cause as timeouts from an upstream service provider and are actively working on a mitigation

We have detected issues for customers connecting to account.mongodb.com and are actively investigating. Customers may experience issues logging into Atlas. Atlas Clusters are not impacted

This incident has been resolved.

We have identified a fix and are monitoring.

We are currently experiencing degraded performance with our Datadog integration. This may result in delayed metrics, incomplete metrics, or issues with alerting for customers using the Datadog integration.

This incident has been resolved.

Atlas is seeing errors rates from LetsEncrypt subsiding. Please see LetsEncrypt status page https://letsencrypt.status.io/pages/55957a99e800baa4470002da for more information. Cluster operations should return to normal.

Atlas is seeing elevated errors from our certificate authority LetsEncrypt. Customers will see delayed operations when provisioning new nodes.

This incident has been resolved.

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

The issue has been identified and a fix is being deployed. Users of Atlas Triggers and Atlas Device Sync may experience delays in processing events.

We are currently investigating an issue affecting customers using Atlas Triggers and Atlas Device Sync.

The issue has been resolved.

A fix has been implemented and we are monitoring results. Cluster operations should begin to succeed again.

Some types of cluster operations have been delayed as of 17:15 UTC, 2024-10-09, including cluster provisioning. We are working on a fix.

A bug fix to eliminate duplicate alert notifications and notification delays has been successfully deployed. Alerting is now functioning as expected.

We have started deploying a fix that will eliminate duplicate alert notifications and notification delays. We are monitoring recovery.

We are validating a bug fix that will eliminate duplicate notifications and notification delays for alerts. We expect to deploy this fix by ~23:00 UTC.

We have identified the root cause of duplicate notifications and notification delays for alerts and are currently working on a bug fix.

We are currently investigating an issue that results in sending duplicate notifications for alerts, as well as delays in alert notifications.

This incident has been resolved.

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

We are currently investigating query timeouts when connecting to Azure westeurope Atlas Data Federation instances.

The issue has been resolved.

We are continuing to monitor for any further issues.

Cluster provisioning should now proceed as planned.

We are currently investigating an issue that may result in some customers experiencing delayed cluster provisioning operations.