MongoDB Outage History

Started Feb 13, 2026, 07:20 AM UTC· resolved Feb 13, 2026, 07:55 AM UTC

1. investigating Feb 13, 2026, 07:20 AM UTC

   We are currently investigating reports of the slow loading of the Atlas web UI.

2. resolved Feb 13, 2026, 07:55 AM UTC

   We have identified and resolved the issue. Atlas UI will load without a delay now.

Read the full incident report →

Started Feb 12, 2026, 10:10 PM UTC· resolved Feb 12, 2026, 11:10 PM UTC

1. investigating Feb 12, 2026, 10:10 PM UTC

   We are currently investigating elevated errors for customers attempting to create a cluster on AWS

2. identified Feb 12, 2026, 11:00 PM UTC

   We have identified the root cause and are implementing a fix to remediate the situation

3. monitoring Feb 12, 2026, 11:08 PM UTC

   We have implemented the fix. Customers will now be able to create new clusters on AWS.

4. resolved Feb 12, 2026, 11:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 07, 2026, 09:07 AM UTC· resolved Feb 07, 2026, 11:43 AM UTC

1. investigating Feb 07, 2026, 09:07 AM UTC

   We are observing widespread issues in Azure West US. Customers may see nodes reporting as “down” and delayed cluster modifications for Azure clusters in West US.

2. identified Feb 07, 2026, 09:15 AM UTC

   Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status Ongoing Service Degradation in West US We are aware of an issue impacting a subset of customers in West US, Our Engineering team is actively investigating and working on mitigation. We will provide more information shortly. This message was last updated at 09:10 UTC on 07 February 2026

3. monitoring Feb 07, 2026, 10:11 AM UTC

   We are seeing some nodes in the impacted Azure West US region recovering. We will continue to monitor and provide updates.

4. resolved Feb 07, 2026, 11:43 AM UTC

   Many nodes have recovered in the impacted region, however there are still some impacted nodes that are recovering. Azure's latest update at 11:05 UTC on 07 February 2026 indicates they are observing signs of partial recovery and that recovery efforts remain in progress. We are resolving the status post as we expect our system to automatically remediate any lingering issues. Please follow the Azure status post for further updates on the regional outage remediation efforts from their end.

Read the full incident report →

Started Feb 03, 2026, 06:49 PM UTC· resolved Feb 03, 2026, 07:15 PM UTC

1. identified Feb 03, 2026, 06:49 PM UTC

   Users may be unable to access the MongoDB Atlas App Services triggers page and may see authentication failures when using the Admin API. As a result, some users may be unable to create, update, or manage App Services resources. We have identified an issue with a recent change to authentication and are working to revert those changes.

2. identified Feb 03, 2026, 06:50 PM UTC

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

3. resolved Feb 03, 2026, 07:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 10:30 PM UTC· resolved Jan 29, 2026, 11:55 PM UTC

1. investigating Jan 29, 2026, 10:30 PM UTC

   We are currently investigating an issue with the activity feed. We will update as the we learn more.

2. investigating Jan 29, 2026, 11:24 PM UTC

   We are reverting a recent change in one of the impacted services. We will have an update after that rolls out.

3. investigating Jan 29, 2026, 11:34 PM UTC

   The revert of the recent change did not meaningfully help the situation. However, we have looked into the issue more and have a better idea of the root cause. We will have another update shortly.

4. monitoring Jan 29, 2026, 11:54 PM UTC

   We have deployed a fix and are seeing activity feed pages load again.

5. resolved Jan 29, 2026, 11:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 19, 2025, 09:45 PM UTC· resolved Dec 20, 2025, 12:28 AM UTC

1. investigating Dec 19, 2025, 09:45 PM UTC

   We are investigating report of issues connecting and authenticating to Atlas Data Federation and Online Archive instances.

2. investigating Dec 19, 2025, 09:46 PM UTC

   We are continuing to investigate this issue.

3. identified Dec 19, 2025, 09:51 PM UTC

   We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries.

4. identified Dec 19, 2025, 09:57 PM UTC

   We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing, as well as the creation of new Data Federation or Online Archive instances - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries. Additionally, Vercel users may not be able to get directly to Atlas from within Vercel. As a workaround, users are encouraged to login directly to Atlas at cloud.mongodb.com

5. monitoring Dec 19, 2025, 10:42 PM UTC

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

6. resolved Dec 20, 2025, 12:28 AM UTC

   Issue is resolved, and affected components are confirmed to be operational again.

Read the full incident report →

Started Dec 10, 2025, 01:51 AM UTC· resolved Dec 16, 2025, 12:30 AM UTC

1. monitoring Dec 10, 2025, 01:51 AM UTC

   This status alert only applies to customers who deployed MongoDB Atlas via the Vercel Marketplace. We are asking customers to promptly redeploy their Vercel applications. As part of our response to the React’s CVE-2025-55182 (https://vercel.com/changelog/cve-2025-55182) the critical security advisory affecting React Server Components, some MongoDB customers will need to take action. Specifically, MongoDB Atlas customers who deployed clusters via the Vercel Marketplace will need to ensure their applications are running on an unaffected version of Next.js (instructions here: https://vercel.com/kb/bulletin/react2shell) and redeploy their Vercel applications (instructions here: https://vercel.com/docs/deployments/managing-deployments). This is to avoid a loss of database connectivity from your Vercel deployment. All other Atlas functionality is unaffected. Users who have not deployed MongoDB Atlas via the Vercel Marketplace are not affected.

2. resolved Dec 16, 2025, 12:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 05:55 PM UTC· resolved Nov 19, 2025, 06:54 PM UTC

1. identified Nov 19, 2025, 05:55 PM UTC

   We have identified an issue redeeming Activation Codes in both MongoDB Atlas and MongoDB Atlas for Government. Affected users will have an error when trying to apply their Activation Codes which may show as the "save" button disappearing and the subscription not being applied. There is no workaround at this time. Please try again after this issue clears.

2. monitoring Nov 19, 2025, 06:22 PM UTC

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

3. resolved Nov 19, 2025, 06:54 PM UTC

   This incident has been resolved. During this time, users may have also had issues activating self-service support plans. We encourage any affected users to sign up again.

Read the full incident report →

Started Nov 03, 2025, 07:00 PM UTC· resolved Nov 03, 2025, 09:13 PM UTC

1. investigating Nov 03, 2025, 07:00 PM UTC

   We're investigating an issue impacting Atlas Azure cluster snapshot creation (australiaeast region only). This only affects new snapshot creation. Existing snapshots are not affected.

2. identified Nov 03, 2025, 07:27 PM UTC

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

3. monitoring Nov 03, 2025, 08:03 PM UTC

   We've identified the root cause which is an Azure outage: https://azure.status.microsoft/en-us/status. Will continue to monitor.

4. resolved Nov 03, 2025, 09:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 05:41 PM UTC· resolved Oct 29, 2025, 06:33 PM UTC

1. monitoring Oct 29, 2025, 05:41 PM UTC

   We have been informed that Azure is experiencing network availability issues for some services. We are not observing any customer impact and will continue to monitor the situation closely. Please refer to https://azure.status.microsoft/en-us/status for more information.

2. resolved Oct 29, 2025, 06:33 PM UTC

   Atlas is unaffected by the Azure network availability issue.

Read the full incident report →

Started Oct 29, 2025, 02:30 AM UTC· resolved Oct 29, 2025, 02:38 AM UTC

1. identified Oct 29, 2025, 02:30 AM UTC

   We have identified an issue that is causing delays in Atlas cluster management operations. Cluster health is unaffected. A fix has been deployed and we expect improvement shortly.

2. monitoring Oct 29, 2025, 02:34 AM UTC

   The fix has been deployed and Atlas cluster management operations are no longer delayed.

3. resolved Oct 29, 2025, 02:38 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 09:08 PM UTC· resolved Oct 23, 2025, 10:50 PM UTC

1. identified Oct 23, 2025, 09:08 PM UTC

   We have identified an issue affecting our federated authentication system since approximately 17:30 UTC on 2025-10-23. This affects a small number of federated users. Affected users who attempt to login via their federation will not to be able to login to Atlas or the Support portal and may see errors claiming they are unauthorized. As a workaround, users can login at cloud.mongodb.com or support.mongodb.com depending on whether they would like to use Atlas or Support, respectively. The same issue affects Atlas for Government, so users there could go to cloud.mongodbgov.com to login. Existing logins are unaffected. Cluster health is unaffected.

2. monitoring Oct 23, 2025, 10:43 PM UTC

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

3. monitoring Oct 23, 2025, 10:44 PM UTC

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

4. resolved Oct 23, 2025, 10:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 03:49 PM UTC· resolved Oct 23, 2025, 08:52 PM UTC

1. monitoring Oct 23, 2025, 03:49 PM UTC

   Since approximately 14:00 UTC on 2025-10-22, a small number of Atlas clusters with nodes in GCP were slow to recover from maintenance or other shutdown events. Affected clusters would have had a node down for an extended period of time while the "blue bar" in the Atlas web UI indicated that we are still trying to recover the node. As only a minority of nodes in each cluster could have been affected, underlying cluster health was not affected. While we have corrected all affected clusters, we are still monitoring to ensure the issue does not recur.

2. resolved Oct 23, 2025, 08:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 10:07 AM UTC· resolved Oct 20, 2025, 08:30 PM UTC

1. monitoring Oct 20, 2025, 10:07 AM UTC

   AWS is experiencing an outage in the US-EAST-1 Region which is being handled as a P1 incident. This was first identified at 08:51 UTC. Cloud Operations are delayed with degraded performance. Access to backing clusters is unaffected. We are observing signs of recovery at this point in time and we're closely monitoring the AWS status page. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status

2. monitoring Oct 20, 2025, 03:02 PM UTC

   Cloud Operations remain delayed with degraded performance. Access to backing clusters is unaffected. We are also observing a degradation in monitoring visibility, with approximately 20% of metrics destined for DataDog being dropped. We are observing signs of recovery, with provisioning speeds returning to normal in all regions outside of US-EAST-1. Provisioning within US-EAST-1 remains significantly degraded. Next Steps: We are closely monitoring the situation and the official AWS status page. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status

3. monitoring Oct 20, 2025, 03:05 PM UTC

   We are experiencing delays in provisioning additional resources for Triggers apps and ability to register. Accessing cluster data through the Data Explorer Atlas UI is also degraded. We are closely monitoring the situation and the official AWS status page. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status

4. monitoring Oct 20, 2025, 03:36 PM UTC

   We are experiencing delays in provisioning and starting new Stream processors. We are also observing a slight degradation in login success rate to cloud.mongodb.com. We are closely monitoring the situation and the official AWS status page. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status

5. monitoring Oct 20, 2025, 03:58 PM UTC

   Atlas Data Federation is experiencing issues connecting to downstream atlas clusters. Atlas Charts is also experiencing issues connecting to customer deployments to retrieve data to render Charts. We are continuing to monitor for any further issues.

6. monitoring Oct 20, 2025, 04:47 PM UTC

   Atlas App Services is experiencing increased processing delays in the US-EAST-1 and US-EAST-2 regions along with degraded performance in Triggers updates. We are closely monitoring the situation and the official AWS status page. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status

7. monitoring Oct 20, 2025, 07:30 PM UTC

   Affected services are starting to recover along with AWS.

8. monitoring Oct 20, 2025, 08:15 PM UTC

   We are continuing to monitor for any further issues.

9. resolved Oct 20, 2025, 08:30 PM UTC

   This incident has been resolved.

Read the full incident report →