MongoDB Outage History

MongoDB is up right now

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

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

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

Minor August 28, 2025

MongoDB Atlas: Cluster metrics page not visible to Read Only users

Detected by Pingoru
Aug 28, 2025, 02:50 PM UTC
Resolved
Aug 28, 2025, 05:04 PM UTC
Duration
2h 13m
Affected: MongoDB CloudMongoDB Atlas for Government
Timeline · 3 updates
  1. identified Aug 28, 2025, 02:50 PM UTC

    We have identified an issue where Atlas users with either Organization, Project Read Only, or Observability Viewer permissions may be unable to view any cluster metrics pages. Affected users will see a 404 error page. As a workaround, Project Owners are still able to view metrics. This affects both Atlas and Atlas for Government environments. Cluster health is unaffected.

  2. monitoring Aug 28, 2025, 04:47 PM UTC

    A fix has been implemented and we are monitoring the results in Atlas. Atlas for Government is still affected, but assuming the fix is successful, we will roll it out to Atlas for Government shortly.

  3. resolved Aug 28, 2025, 05:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2025

Capacity Constrained Azure regions eastus, eastus2, germanywestcentral and more

Detected by Pingoru
Aug 27, 2025, 10:23 PM UTC
Resolved
Aug 29, 2025, 07:43 PM UTC
Duration
1d 21h
Affected: MongoDB Cloud
Timeline · 7 updates
  1. identified Aug 27, 2025, 10:23 PM UTC

    We are experiencing elevated capacity errors on Azure regions eastus, eastus2, germanywestcentral, westus2 and more. Azure cluster instance tier modifications and cluster creation may experiencing delays due to this issue. We are working on a mitigation to help alleviate the situation

  2. identified Aug 27, 2025, 10:59 PM UTC

    We've engaged with the Azure support team to assist with the capacity constrained regions.

  3. identified Aug 28, 2025, 02:36 AM UTC

    We are still implementing an overall fleet-wide mitigation. In the meantime, we are working with our support team to apply case-by-case mitigations to unblock customers. These interim solutions may restore service but are not permanent fixes and may have some operational constraints. The next update will happen at 12pm UTC

  4. identified Aug 28, 2025, 12:27 PM UTC

    We've seen capacity improve in germanywestcentral and have applied mitigations for eastus2. We're still actively working on the a fleet-wide mitigation and expect to deploy today

  5. identified Aug 28, 2025, 07:48 PM UTC

    We've implemented a code mitigation and are testing the change before deploying to production

  6. monitoring Aug 29, 2025, 04:31 PM UTC

    We have deployed the mitigation for M30+ instance sizes, however M10 and M20 may still experience capacity constraints. We recommend customers upgrade to M30+ if they are continuing to experience issues.

  7. resolved Aug 29, 2025, 07:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2025

MongoDB Atlas: Atlas Streams Metrics to Datadog delayed

Detected by Pingoru
Aug 26, 2025, 06:50 PM UTC
Resolved
Aug 27, 2025, 12:27 AM UTC
Duration
5h 37m
Affected: MongoDB Atlas Stream Processing
Timeline · 6 updates
  1. identified Aug 26, 2025, 06:50 PM UTC

    We have identified an issue for MongoDB Atlas Streams metrics being reported to Datadog. In particular, Atlas Streams metrics have been delayed since approximately 15:20 UTC on 26 August 2025. This may cause metrics to not be received by Datadog in a timely manner or missed entirely. Affected users may see gaps in their metric data in Datadog and this may cause alerting in some circumstances. Users can check the Atlas web UI for current metrics values. Cluster health is unaffected.

  2. identified Aug 26, 2025, 06:58 PM UTC

    We have identified an issue for MongoDB Atlas Streams metrics being reported to Datadog. In particular, Atlas Streams metrics have been delayed since approximately 15:20 UTC on 26 August 2025. This may cause metrics to not be received by Datadog in a timely manner or missed entirely. Affected users may see gaps in their metric data in Datadog and this may cause alerting in some circumstances. Users can check the Atlas web UI for current metrics values. Cluster health is unaffected.

  3. identified Aug 26, 2025, 08:26 PM UTC

    We are continuing to debug an issue for MongoDB Atlas Streams metrics being reported to Datadog. Atlas Streams metrics have been delayed since approximately 15:20 UTC on 26 August 2025. We are working hard on restoring these metrics and will continue to make status updates.

  4. identified Aug 26, 2025, 08:59 PM UTC

    We have stabilized the system and are working through a backlog of MongoDB Atlas Streams metrics for Datadog. We will move to monitoring once we have worked through the entire backlog.

  5. monitoring Aug 26, 2025, 09:43 PM UTC

    We have worked through the entire backlog of MongoDB Atlas Streams metrics for Datadog. We are now monitoring for any additional issues, and are configuring alerting in case we see another delay.

  6. resolved Aug 27, 2025, 12:27 AM UTC

    We have been monitoring the incident since 21:43 UTC, and see no evidence that it will recur. At this point, our metrics delay from MongoDB Atlas Streams to Datadog is within tolerances, and so we are treating this incident as Resolved.

Read the full incident report →

Minor August 22, 2025

MongoDB Atlas: Signing up for AWS Marketplace failing

Detected by Pingoru
Aug 22, 2025, 03:06 PM UTC
Resolved
Aug 22, 2025, 04:44 PM UTC
Duration
1h 38m
Affected: MongoDB Cloud
Timeline · 3 updates
  1. identified Aug 22, 2025, 03:06 PM UTC

    We have identified an issue connecting AWS Marketplace as a payment method for MongoDB Atlas. Affected users will see a form and then a confirmation screen, but the addition of the payment method will not succeed. Existing connections and cluster health is unaffected.

  2. identified Aug 22, 2025, 03:22 PM UTC

    We have identified an issue connecting AWS Marketplace as a payment method for MongoDB Atlas since approximately August 19, 2025. Affected users will see a form and then a confirmation screen, but the addition of the payment method will not succeed. Existing connections and cluster health is unaffected.

  3. resolved Aug 22, 2025, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 21, 2025

Atlas Azure cluster new snapshot creation failure (EUROPE_WEST)

Detected by Pingoru
Aug 21, 2025, 12:03 AM UTC
Resolved
Aug 21, 2025, 12:35 AM UTC
Duration
31m
Affected: MongoDB Cloud
Timeline · 2 updates
  1. investigating Aug 21, 2025, 12:03 AM UTC

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

  2. resolved Aug 21, 2025, 12:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 18, 2025

Some AWS us-east-1 free tier (M0 instance size) clusters in degraded state

Detected by Pingoru
Aug 18, 2025, 07:27 AM UTC
Resolved
Aug 19, 2025, 12:25 AM UTC
Duration
16h 57m
Affected: MongoDB Cloud
Timeline · 6 updates
  1. investigating Aug 18, 2025, 07:27 AM UTC

    We're investigating an issue impacting some AWS us-east-1 free tier (M0 instance size) clusters. These clusters are experiencing connection issues and a failure to upgrade to dedicated instance sizes. This issue impacts <1% of AWS us-east-1 M0 clusters.

  2. identified Aug 18, 2025, 07:53 AM UTC

    We've identified the issue causing some AWS us-east-1 free tier M0 clusters to be in a degraded state. The team is working on a fix.

  3. identified Aug 18, 2025, 12:46 PM UTC

    We continue to work on a fix for impacted M0 clusters.

  4. identified Aug 18, 2025, 07:38 PM UTC

    We continue to work on a fix for the impacted M0 clusters. No additional AWS us-east-1 M0 clusters have been impacted since the original post.

  5. monitoring Aug 18, 2025, 11:31 PM UTC

    Impacted free tier M0 AWS us-east-1 clusters are now healthy. Customers that attempted an upgrade of their M0 cluster to a dedicated instance tier can now retry their request.

  6. resolved Aug 19, 2025, 12:25 AM UTC

    This incident has been resolved.

Read the full incident report →