Oct <var data-var='date'> 2</var>, <var data-var='time'>05:02</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>00:01</var> UTC Identified - 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 timing at this moment. Existing Charts projects are not affected.

MongoDB Charts: Infinite login loop when creating new Charts projects

Oct <var data-var='date'> 1</var>, <var data-var='time'>20:54</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 1</var>, <var data-var='time'>19:59</var> UTC Monitoring - 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. Oct <var data-var='date'> 1</var>, <var data-var='time'>19:51</var> UTC Update - 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. Oct <var data-var='date'> 1</var>, <var data-var='time'>18:21</var> UTC Update - We are continuing to investigate this issue. Oct <var data-var='date'> 1</var>, <var data-var='time'>15:41</var> UTC Investigating - 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.

Trigger processing may be delayed globally

Sep <var data-var='date'>30</var>, <var data-var='time'>21:02</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>30</var>, <var data-var='time'>19:26</var> UTC Monitoring - 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. Sep <var data-var='date'>30</var>, <var data-var='time'>19:01</var> UTC Identified - 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. Sep <var data-var='date'>30</var>, <var data-var='time'>18:51</var> UTC Investigating - We are investigating an issue with Atlas metrics ingestion that may delay cluster management operations, including cluster creation and modification.

Delays in Atlas cluster management operations

Sep <var data-var='date'>16</var>, <var data-var='time'>15:31</var> UTC Resolved - 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 Team Sep <var data-var='date'>16</var>, <var data-var='time'>09:09</var> UTC Update - We are continuing to investigate this issue. Sep <var data-var='date'>16</var>, <var data-var='time'>09:06</var> UTC Investigating - 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 contact us using one of the numbers listed below: [These numbers have been removed. Active MongoDB customers can access them at the support portal.] We appreciate your patience.

Support Portal Outage

Sep <var data-var='date'>11</var>, <var data-var='time'>03:51</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>11</var>, <var data-var='time'>02:01</var> UTC Monitoring - 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. Sep <var data-var='date'>11</var>, <var data-var='time'>01:28</var> UTC Investigating - We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.

Atlas is experiencing issues with issuing certificates from Lets Encrypt

Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates)  and AWS me-south-1 (Bahrain)

Sep <var data-var='date'> 3</var>, <var data-var='time'>16:47</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'> 3</var>, <var data-var='time'>16:44</var> UTC Monitoring - Please follow <a href="https://status.mongodb.com/incidents/7g5qmxgkc2y4">the original status post</a> for updates on AWS me-central-1 and AWS me-south-1 issues.

Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

Aug <var data-var='date'>28</var>, <var data-var='time'>14:30</var> UTC Resolved - 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 implementing measures to reduce the risk of this happening again.

MongoDB Atlas Log Integration service degraded

Aug <var data-var='date'>20</var>, <var data-var='time'>22:07</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>21:39</var> UTC Update - We have deployed fix, continuing the monitor for any further issues. Aug <var data-var='date'>19</var>, <var data-var='time'>22:00</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>19</var>, <var data-var='time'>21:58</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>19</var>, <var data-var='time'>21:57</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>19</var>, <var data-var='time'>21:50</var> UTC Monitoring - We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue. Aug <var data-var='date'>19</var>, <var data-var='time'>20:45</var> UTC Identified - 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.

Issues rotating certificates for projects containing only Atlas Free and Flex clusters

Aug <var data-var='date'>18</var>, <var data-var='time'>15:17</var> UTC Resolved - 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 been remediated. Customer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well. Aug <var data-var='date'>18</var>, <var data-var='time'>15:04</var> UTC Monitoring - We have disabled the workload and are monitoring the situation Aug <var data-var='date'>18</var>, <var data-var='time'>14:57</var> UTC Identified - 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. Aug <var data-var='date'>18</var>, <var data-var='time'>14:10</var> UTC Investigating - We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.

Atlas UI and API Periodic Unavailability

Aug <var data-var='date'>12</var>, <var data-var='time'>17:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>12</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'> 6</var>, <var data-var='time'>20:32</var> UTC Scheduled - We will perform planned maintenance on Atlas on August 12th from approximately 14:00 to 17:00 UTC. During this maintenance window, some users may experience slightly elevated latency on operations using the Atlas UI Console and the Atlas Admin API. No impact is expected to customer cluster performance or data. We will post updates when maintenance begins and when it completes.

MongoDB Atlas: Brief elevated latency during scheduled maintenance.

Aug <var data-var='date'> 5</var>, <var data-var='time'>12:14</var> UTC Resolved - 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. Aug <var data-var='date'> 5</var>, <var data-var='time'>05:17</var> UTC Investigating - 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 is not limited to, multiple GCP regions across North America, Europe, and Asia Pacific/Australia, as well as M50 and S70L instance types. Customers may experience errors or delays when creating or modifying Atlas clusters, particularly deployments with search nodes. Some customers may also see host-down alerts while this issue is ongoing. MongoDB is working with GCP to understand the scope of the issue and restore capacity. Customers encountering provisioning issues may retry later or consider using a different GCP region, cloud provider, or instance size. If you are experiencing a time-sensitive production impact, please contact MongoDB Support through the Support Portal or the in-product support chat. We will provide another update as more information becomes available.

GCP capacity constraints affecting Atlas deployments

Aug <var data-var='date'> 3</var>, <var data-var='time'>21:18</var> UTC Resolved - The system has returned to normal operation. Aug <var data-var='date'> 3</var>, <var data-var='time'>19:02</var> UTC Monitoring - A fix has been applied and we are monitoring the system. Aug <var data-var='date'> 3</var>, <var data-var='time'>18:47</var> UTC Investigating - VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.

Elevated errors on VoyageAI APIs

Jul <var data-var='date'>29</var>, <var data-var='time'>22:47</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>29</var>, <var data-var='time'>22:35</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>29</var>, <var data-var='time'>18:11</var> UTC Investigating - 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.

Atlas Stream Processing errors in Azure West Europe

Jul <var data-var='date'>29</var>, <var data-var='time'>19:37</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>29</var>, <var data-var='time'>19:31</var> UTC Monitoring - We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again. Jul <var data-var='date'>29</var>, <var data-var='time'>19:06</var> UTC Identified - We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes. Jul <var data-var='date'>29</var>, <var data-var='time'>18:55</var> UTC Investigating - 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.

Delayed cluster configuration affecting free and flex users

Jul <var data-var='date'>27</var>, <var data-var='time'>23:48</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>27</var>, <var data-var='time'>23:47</var> UTC Update - We have fully recovered as of 16:41 PST. Jul <var data-var='date'>27</var>, <var data-var='time'>23:37</var> UTC Investigating - All VoyageAI models are experiencing elevated errors. We are investigating the issue.

VoyageAI elevated errors

Jul <var data-var='date'>23</var>, <var data-var='time'>20:28</var> UTC Resolved - Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete. Jul <var data-var='date'>23</var>, <var data-var='time'>18:54</var> UTC Update - 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 clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. We are monitoring recovery closely and will provide additional updates as more information becomes available. Jul <var data-var='date'>23</var>, <var data-var='time'>18:26</var> UTC Update - 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 appearing down, and delays to cluster modifications. Azure is investigating the issue and evaluating mitigation options. We will provide additional updates as more information becomes available. Jul <var data-var='date'>23</var>, <var data-var='time'>16:38</var> UTC Identified - 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 Jul <var data-var='date'>23</var>, <var data-var='time'>16:21</var> UTC Investigating - 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.

Cluster connectivity issues in Azure westus

Jul <var data-var='date'>21</var>, <var data-var='time'>13:08</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>20</var>, <var data-var='time'>15:06</var> UTC Monitoring - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>16:14</var> UTC Identified - 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 has been resolved, we intend to display and bill for the correct amounts. Charges will have usage dates that correctly express the usage, but will have the billed date of when this is corrected. Cluster and backup health are unaffected. Other cloud providers' billing data is unaffected. You can follow the upstream incident at https://health.aws.amazon.com/health/status

MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20

Jul <var data-var='date'>10</var>, <var data-var='time'>14:56</var> UTC Resolved - Let's Encrypt service has returned to normal. Jul <var data-var='date'> 9</var>, <var data-var='time'>21:22</var> UTC Monitoring - 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. Jul <var data-var='date'> 9</var>, <var data-var='time'>19:37</var> UTC Investigating - We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.

Jul <var data-var='date'>10</var>, <var data-var='time'>01:11</var> UTC Resolved - The issue has been resolved. Jul <var data-var='date'>10</var>, <var data-var='time'>00:32</var> UTC Monitoring - A fix has been implemented and we are monitoring the region. Jul <var data-var='date'> 9</var>, <var data-var='time'>23:03</var> UTC Investigating - We are currently investigating an issue affecting Stream Processing Azure West Europe. User initiated commands & workloads may see intermittent failures.

Atlas Stream Processing is experiencing issues in Azure - West Europe

Jul <var data-var='date'> 9</var>, <var data-var='time'>11:06</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 9</var>, <var data-var='time'>11:01</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 9</var>, <var data-var='time'>10:57</var> UTC Identified - We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix. Jul <var data-var='date'> 9</var>, <var data-var='time'>10:23</var> UTC Investigating - 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.

Atlas Data Federation and Online Archive cloud-provider IAM authentication error

Jul <var data-var='date'> 2</var>, <var data-var='time'>23:36</var> UTC Resolved - Let's Encrypt services have returned back to normal. Cluster operations have now returned to normal. Jul <var data-var='date'> 2</var>, <var data-var='time'>23:09</var> UTC Monitoring - 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.

Impaired Cluster Operations due to Lets Encrypt Service Degradation

Jul <var data-var='date'> 2</var>, <var data-var='time'>21:06</var> UTC Resolved - We've confirmed that Lets Encrypt has returned to normal operations. Cluster operations are now back to normal. Jul <var data-var='date'> 2</var>, <var data-var='time'>19:34</var> UTC Monitoring - 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.

Impaired Cluster Operations due to Lets Encrypt Outage

Jul <var data-var='date'> 2</var>, <var data-var='time'>11:09</var> UTC Resolved - This incident has been resolved. AWS clusters should no longer encounter errors during backup and restore. Jul <var data-var='date'> 2</var>, <var data-var='time'>10:50</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 2</var>, <var data-var='time'>10:45</var> UTC Investigating - 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 instance size.

AWS cluster backup and restore operations are failing

Jun <var data-var='date'>25</var>, <var data-var='time'>16:24</var> UTC Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>28</var>, <var data-var='time'>19:41</var> UTC Scheduled - Please note that this is courtesy notice and no action is required from you if you do not pin intermediate certificates from Let's Encrypt (LE) and/or Google Trust Services (GTS) in your environment when connecting to Atlas dedicated clusters. Let's Encrypt (LE) and Google Trust Services (GTS) have issued additional intermediate certificates to their services. Intermediate certificates act as a secure bridge between root CAs (e.g. LE/GTS) and end entities to streamline management and reduce risk. We want to emphasize that the changes mentioned below related to intermediate certificate authority are not made by MongoDB but by LE and GTS sometime in 2026 which are the Certificate Authority (CA) providers for TLS certificates for all MongoDB Atlas clusters. Let’s Encrypt: https://letsencrypt.org/2025/11/24/gen-y-hierarchy Google Trust Service: https://pki.goog/updates/august2025-intermediate-update.html MongoDB does not recommend hardcoding or pinning intermediate CAs in your application; please refer to the best practices recommended by MongoDB here. If you have any questions or need assistance, please use the chat (https://www.mongodb.com/company/contact) in the Atlas UI or contact Support (https://support.mongodb.com/welcome) to talk to someone on our team.

Is Mongo DB Atlas down?

Mongo DB Atlas status is UP

Lastest published events

MongoDB Charts: Infinite login loop when creating new Charts projects

Trigger processing may be delayed globally

Delays in Atlas cluster management operations

Mongo DB Atlas Services, Components and Regions

Recent Mongo DB Atlas events

MongoDB Charts: Infinite login loop when creating new Charts projects

Trigger processing may be delayed globally

Delays in Atlas cluster management operations

Support Portal Outage

Atlas is experiencing issues with issuing certificates from Lets Encrypt

Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)