MongoDB Outage History

MongoDB is up right now

MongoDB had 56 outages in the last 2 years totaling 215h 52m of downtime — averaging 2.3 incidents per month.

There were 56 MongoDB outages since August 18, 2025 totaling 215h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.cloud.mongodb.com

Minor February 13, 2026

DNS Resolution failures for public IP addresses within 31.89.0.0/24

Detected by Pingoru
Feb 13, 2026, 04:11 PM UTC
Resolved
Feb 13, 2026, 05:57 PM UTC
Duration
1h 46m
Affected: MongoDB Cloud
Timeline · 3 updates
  1. investigating Feb 13, 2026, 04:11 PM UTC

    We are investigating an issue with DNS resolution for public IP addresses within 31.89.0.0/24. We are engaging with AWS support to remediate the situation.

  2. identified Feb 13, 2026, 04:42 PM UTC

    We have identified the root cause and are working on backfilling those records with AWS support. We have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.

  3. resolved Feb 13, 2026, 05:57 PM UTC

    The DNS records have been backfilled and clusters that had these IP addresses should be recovered.

Read the full incident report →

Minor February 13, 2026

MongoDB Atlas: Atlas UI loading slowly

Detected by Pingoru
Feb 13, 2026, 07:20 AM UTC
Resolved
Feb 13, 2026, 07:55 AM UTC
Duration
34m
Affected: MongoDB Cloud
Timeline · 2 updates
  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 →

Critical February 12, 2026

Elevated errors for cluster creation on AWS

Detected by Pingoru
Feb 12, 2026, 10:10 PM UTC
Resolved
Feb 12, 2026, 11:10 PM UTC
Duration
59m
Affected: MongoDB Cloud
Timeline · 4 updates
  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 →

Major February 7, 2026

Partial outage in Azure West US

Detected by Pingoru
Feb 07, 2026, 09:07 AM UTC
Resolved
Feb 07, 2026, 11:43 AM UTC
Duration
2h 35m
Affected: MongoDB Cloud
Timeline · 4 updates
  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 →

Major February 3, 2026

Triggers UI and Admin API authentication issues

Detected by Pingoru
Feb 03, 2026, 06:49 PM UTC
Resolved
Feb 03, 2026, 07:15 PM UTC
Duration
26m
Affected: MongoDB Atlas App Services and Device SyncMongoDB Charts
Timeline · 3 updates
  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 →

Minor January 29, 2026

Activity Feed is experiencing degraded performance

Detected by Pingoru
Jan 29, 2026, 10:30 PM UTC
Resolved
Jan 29, 2026, 11:55 PM UTC
Duration
1h 25m
Affected: MongoDB Cloud
Timeline · 5 updates
  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 →

Major December 19, 2025

Issue connecting to Atlas Data Federation and Online Archive

Detected by Pingoru
Dec 19, 2025, 09:45 PM UTC
Resolved
Dec 20, 2025, 12:28 AM UTC
Duration
2h 43m
Affected: MongoDB CloudMongoDB Atlas Data Federation and Online ArchiveMongoDB ChartsMongoDB Atlas Stream Processing
Timeline · 6 updates
  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 →

Notice December 10, 2025

Action Needed for Vercel Marketplace Integration Users

Detected by Pingoru
Dec 10, 2025, 01:51 AM UTC
Resolved
Dec 16, 2025, 12:30 AM UTC
Duration
5d 22h
Affected: MongoDB Cloud
Timeline · 2 updates
  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 →

Minor November 19, 2025

MongoDB Atlas: Activation Code redemptions may fail

Detected by Pingoru
Nov 19, 2025, 05:55 PM UTC
Resolved
Nov 19, 2025, 06:54 PM UTC
Duration
59m
Affected: MongoDB CloudMongoDB Atlas for Government
Timeline · 3 updates
  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 →

Notice November 3, 2025

Atlas Azure cluster new snapshot creation failure (australiaeast)

Detected by Pingoru
Nov 03, 2025, 07:00 PM UTC
Resolved
Nov 03, 2025, 09:13 PM UTC
Duration
2h 13m
Affected: MongoDB Cloud
Timeline · 4 updates
  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 →

Notice October 29, 2025

Azure Network Availability Issues

Detected by Pingoru
Oct 29, 2025, 05:41 PM UTC
Resolved
Oct 29, 2025, 06:33 PM UTC
Duration
52m
Affected: MongoDB Cloud
Timeline · 2 updates
  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 →

Minor October 29, 2025

Delayed Cluster Management Operations

Detected by Pingoru
Oct 29, 2025, 02:30 AM UTC
Resolved
Oct 29, 2025, 02:38 AM UTC
Duration
8m
Affected: MongoDB Cloud
Timeline · 3 updates
  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 →

Minor October 23, 2025

MongoDB Atlas and Support Portal: Browser-initiated Federated logins fail

Detected by Pingoru
Oct 23, 2025, 09:08 PM UTC
Resolved
Oct 23, 2025, 10:50 PM UTC
Duration
1h 42m
Affected: MongoDB CloudMongoDB Support PortalMongoDB Atlas for Government
Timeline · 4 updates
  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 →

Minor October 23, 2025

MongoDB Atlas: Clusters with nodes in GCP slow to recover

Detected by Pingoru
Oct 23, 2025, 03:49 PM UTC
Resolved
Oct 23, 2025, 08:52 PM UTC
Duration
5h 3m
Affected: MongoDB Cloud
Timeline · 2 updates
  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 →

Notice October 8, 2025

Elevated Azure Capacity Errors

Detected by Pingoru
Oct 08, 2025, 04:43 PM UTC
Resolved
Oct 08, 2025, 09:56 PM UTC
Duration
5h 13m
Affected: MongoDB Cloud
Timeline · 2 updates
  1. identified Oct 08, 2025, 04:43 PM UTC

    We have identified escalating Azure capacity issues in the eastus region for M10 and M20s. We recommend scaling up to another instance tier or moving it to a different region.

  2. resolved Oct 08, 2025, 09:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 6, 2025

Some Atlas Cluster Operations Delayed

Detected by Pingoru
Oct 06, 2025, 07:33 PM UTC
Resolved
Oct 06, 2025, 11:19 PM UTC
Duration
3h 45m
Affected: MongoDB Cloud
Timeline · 5 updates
  1. investigating Oct 06, 2025, 07:33 PM UTC

    Some Atlas cluster operations are delayed. This includes cluster operations and metrics ingestion. We are currently investigating the issue.

  2. investigating Oct 06, 2025, 08:48 PM UTC

    We are continuing to investigate the issue. Atlas Cluster operations (including metrics ingestion) are delayed but underlying cluster health is unaffected.

  3. identified Oct 06, 2025, 09:42 PM UTC

    The system had unusually high load causing delays in operations. The issue has been identified and we are working on fix.

  4. monitoring Oct 06, 2025, 10:12 PM UTC

    The system is in healthy state and cluster operations are no longer delayed. We are monitoring for any residual effects.

  5. resolved Oct 06, 2025, 11:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 2, 2025

Flex to Dedicated upgrades are currently failing and resulting in the Dedicated cluster having no monitoring

Detected by Pingoru
Oct 02, 2025, 06:13 PM UTC
Resolved
Oct 02, 2025, 09:46 PM UTC
Duration
3h 32m
Affected: MongoDB Cloud
Timeline · 3 updates
  1. identified Oct 02, 2025, 06:13 PM UTC

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

  2. monitoring Oct 02, 2025, 09:45 PM UTC

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

  3. resolved Oct 02, 2025, 09:46 PM UTC

    This incident has been resolved. Upgrades should complete normally. Any affected clusters should be returned to healthy.

Read the full incident report →

Minor October 1, 2025

Atlas UI Project Overview Page Infinite Loading

Detected by Pingoru
Oct 01, 2025, 06:12 PM UTC
Resolved
Oct 01, 2025, 09:51 PM UTC
Duration
3h 39m
Affected: MongoDB Cloud
Timeline · 4 updates
  1. investigating Oct 01, 2025, 06:12 PM UTC

    We are investigating an issue where the project overview page appears to be loading infinitely.

  2. identified Oct 01, 2025, 06:30 PM UTC

    A new component in the Project Overview page is infinitely loading. The rest of the Overview page is unaffected, and cluster health is unaffected. A fix is being worked on.

  3. monitoring Oct 01, 2025, 09:19 PM UTC

    A fix has been deployed and is being monitored.

  4. resolved Oct 01, 2025, 09:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 23, 2025

MongoDB Atlas

Detected by Pingoru
Sep 23, 2025, 05:14 PM UTC
Resolved
Sep 23, 2025, 07:36 PM UTC
Duration
2h 22m
Affected: MongoDB CloudMongoDB Support Portal
Timeline · 3 updates
  1. identified Sep 23, 2025, 05:14 PM UTC

    We have identified an issue with an upstream provider that is interfering with our ability to respond to chat messages from users. Affected users will be able to send chat messages to MongoDB, but may not see replies in a timely manner. Users with support subscriptions are encouraged to file support cases at this time either through the Atlas UI or directly at support.mongodb.com Thanks in advance for your patience.

  2. monitoring Sep 23, 2025, 06:11 PM UTC

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

  3. resolved Sep 23, 2025, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 19, 2025

MongoDB Atlas Stream Processing and Query Shape metrics gap

Detected by Pingoru
Sep 19, 2025, 01:48 PM UTC
Resolved
Sep 17, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 19, 2025, 01:48 PM UTC

    From approximately 07:00 to 08:45 UTC on 2025-09-17, metrics for Atlas Stream Processing were not being processed. This affected viewing the metrics in the Atlas UI, querying them via the Admin API, or viewing them in Datadog. Additionally, Query Shape metrics were not provided during this time. Affected users will see gaps in their metric data during those times. We will not be backfilling this metric data.

Read the full incident report →

Minor September 10, 2025

Delayed cluster modifications in Azure East US 2

Detected by Pingoru
Sep 10, 2025, 12:34 PM UTC
Resolved
Sep 10, 2025, 08:23 PM UTC
Duration
7h 49m
Affected: MongoDB Cloud
Timeline · 4 updates
  1. identified Sep 10, 2025, 12:34 PM UTC

    We are observing elevated error when provisioning resources due to an Azure service issue. Customers may see delayed cluster modifications for Azure clusters in East US 2. Please refer to the Azure dashboard for their service issue updates.

  2. identified Sep 10, 2025, 05:50 PM UTC

    Azure Eastus2 continues to experience elevated errors. Azure has now published it on their public status page here https://azure.status.microsoft/en-us/status

  3. monitoring Sep 10, 2025, 08:06 PM UTC

    We're seeing capacity errors come down in Azure Eastus2. We will continue monitoring the situation.

  4. resolved Sep 10, 2025, 08:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 31, 2025

Excessive Project Maintenance Notifications in some Atlas projects

Detected by Pingoru
Aug 31, 2025, 12:55 AM UTC
Resolved
Aug 31, 2025, 09:05 AM UTC
Duration
8h 9m
Affected: MongoDB Cloud
Timeline · 2 updates
  1. monitoring Aug 31, 2025, 12:55 AM UTC

    Some MongoDB Atlas Customers have received duplicate maintenance notifications in projects with Maintenance Windows[0] configured. We have implemented a mitigation and are monitoring results. [0] https://www.mongodb.com/docs/atlas/tutorial/cluster-maintenance-window/

  2. resolved Aug 31, 2025, 09:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 29, 2025

Atlas for Government Partial Outage

Detected by Pingoru
Aug 29, 2025, 12:13 AM UTC
Resolved
Aug 29, 2025, 12:40 AM UTC
Duration
27m
Affected: MongoDB Atlas for Government
Timeline · 3 updates
  1. investigating Aug 29, 2025, 12:13 AM UTC

    The Atlas for Government control plane (cloud.mongodbgov.com) is currently inaccessible. We are currently investigating Commercial Atlas is unaffected. Cluster access and performance in gov is unaffected.

  2. monitoring Aug 29, 2025, 12:34 AM UTC

    We've implemented a mitigation and are now actively monitoring

  3. resolved Aug 29, 2025, 12:40 AM UTC

    This incident has been resolved.

Read the full incident report →