Official incident history

  1. Started: · Duration: 756 min
    Provider updates (3)
    1. Identified “Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP europe-west2-b. Atlas clusters are distributed across multiple AZs and 3-node clusters can continue to serve reads and writes from nodes in the other 2 Availability Zones in this region. We are working with our partners to resolve the cause of the issue and restore service to the affecte…”
    2. Monitoring “We are seeing signs of Availability Zone connectivity improving and are continuing to monitor.”
    3. Resolved “This incident has been resolved.”
    Resolved
  2. Started: · Duration: 108 min
    Provider updates (4)
    1. Investigating “Ongoing Atlas Search incident known to cause mongot crashes, potential search and vector search outage, impacting a subset of search and vector search users in the Atlas fleet. We have identified the issue and are working on a fix.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been deployed and we are monitoring.”
    4. Resolved “This incident has been resolved.”
    Resolved
  3. MongoDB Cloud: API, outage or errors

    Provider's original title: Admin Admin API: Intermittent Increase in 5xx errors

    Started: · Duration: 155 min
    Provider updates (3)
    1. Investigating “We are seeing elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. Users may experience intermittent failures when making API calls. We are investigating the root cause and will share another update as our investigation continues.”
    2. Monitoring “We have deployed a mitigation for the elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. We are seeing signs of recovery and are monitoring the service to confirm the issue does not recur before resolving this incident.”
    3. Resolved “This incident has been resolved.”
    Resolved
  4. Started: · Duration: 300 min
    Provider updates (2)
    1. 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.”
    2. Resolved “This incident has been resolved.”
    Resolved
  5. MongoDB Cloud: MongoDB Atlas App Services and Device Sync, increased latency

    Provider's original title: Trigger processing may be delayed globally

    Started: · Duration: 313 min
    Provider updates (3)
    1. 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.”
    2. 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.”
    3. Resolved “This incident has been resolved.”
    Resolved
  6. MongoDB Cloud: MongoDB Cloud, increased latency

    Provider's original title: Delays in Atlas cluster management operations

    Started: · Duration: 130 min
    Provider updates (4)
    1. Investigating “We are investigating an issue with Atlas metrics ingestion that may delay cluster management operations, including cluster creation and modification.”
    2. 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.”
    3. 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.”
    4. Resolved “This incident has been resolved.”
    Resolved
  7. MongoDB Cloud: MongoDB Support Portal, outage or errors

    Provider's original title: Support Portal Outage

    Started: · Duration: 385 min
    Provider updates (2)
    1. 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…”
    2. 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”
    Resolved
  8. Started: · Duration: 143 min
    Provider updates (3)
    1. Investigating “We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.”
    2. 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.”
    3. Resolved “This incident has been resolved.”
    Resolved
  9. MongoDB Cloud: MongoDB Cloud, outage or errors

    Provider's original title: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

    Started: · Duration: still open
    Provider updates (1)
    1. 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.”
    Open
  10. Started: · Duration: 266209 min
    Provider updates (3)
    1. Identified “CURRENT IMPACT According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. AWS is currently experiencing infrastructure impairments in two Middle East regions: * ME-CENTRAL-1 (Middle East – Central): Two Availabili…”
    2. Monitoring “According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as app…”
    3. Resolved “While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status We will update this post as necessary. Thanks in advance for your understanding.”
    Resolved
  11. MongoDB Cloud: degraded performance

    Provider's original title: MongoDB Atlas Log Integration service degraded

    Started: · Duration: 0 min
    Provider updates (1)
    1. 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.”
    Resolved
  12. Started: · Duration: 1521 min
    Provider updates (3)
    1. 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.”
    2. Monitoring “We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.”
    3. Resolved “This incident has been resolved.”
    Resolved
  13. MongoDB Cloud: API, outage or errors

    Provider's original title: Atlas UI and API Periodic Unavailability

    Started: · Duration: 66 min
    Provider updates (4)
    1. Investigating “We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.”
    2. 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.”
    3. Monitoring “We have disabled the workload and are monitoring the situation”
    4. 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-pla…”
    Resolved
  14. Started: · Duration: 417 min
    Provider updates (2)
    1. 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 S7…”
    2. 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.”
    Resolved
  15. MongoDB Cloud: VoyageAI Embedding and Reranking Models, degraded performance

    Provider's original title: Elevated errors on VoyageAI APIs

    Started: · Duration: 151 min
    Provider updates (3)
    1. Investigating “VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.”
    2. Monitoring “A fix has been applied and we are monitoring the system.”
    3. Resolved “The system has returned to normal operation.”
    Resolved
  16. MongoDB Cloud: MongoDB Atlas Stream Processing, outage or errors

    Provider's original title: Atlas Stream Processing errors in Azure West Europe

    Started: · Duration: 275 min
    Provider updates (3)
    1. 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.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  17. MongoDB Cloud: MongoDB Cloud, increased latency

    Provider's original title: Delayed cluster configuration affecting free and flex users

    Started: · Duration: 42 min
    Provider updates (4)
    1. 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.”
    2. Identified “We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.”
    3. Monitoring “We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.”
    4. Resolved “This incident has been resolved.”
    Resolved
  18. MongoDB Cloud: VoyageAI Embedding and Reranking Models, degraded performance

    Provider's original title: VoyageAI elevated errors

    Started: · Duration: 11 min
    Provider updates (2)
    1. Investigating “All VoyageAI models are experiencing elevated errors. We are investigating the issue.”
    2. Resolved “This incident has been resolved.”
    Resolved
  19. Started: · Duration: 247 min
    Provider updates (3)
    1. 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.”
    2. 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”
    3. Resolved “Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.”
    Resolved
  20. MongoDB Cloud: MongoDB Cloud, MongoDB Atlas for Government, outage or errors

    Provider's original title: MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20

    Started: · Duration: 5574 min
    Provider updates (3)
    1. 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 ex…”
    2. 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.”
    3. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
MongoDB Cloud Status ↗ · All Systems Operational · Nov 18, 10:26 PM UTC

Why this assessment

  • Provider reports no active incident.

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official2 min agoYes, recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗