Company Logo

Is there an MongoDB outage?

MongoDB status: Systems Active

Last checked: 3 minutes ago

Get notified about any outages, downtime or incidents for MongoDB and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

MongoDB outages and incidents

Outage and incident data over the last 30 days for MongoDB.

There have been 5 outages or incidents for MongoDB in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for MongoDB

Outlogger tracks the status of these components for Xero:

MongoDB Atlas App Services and Device Sync Active
MongoDB Atlas Data Federation and Online Archive Active
MongoDB Atlas for Government Active
MongoDB Atlas Stream Processing Active
MongoDB Charts Active
MongoDB Cloud Active
MongoDB Support Portal Active
Component Status
MongoDB Atlas App Services and Device Sync Active
MongoDB Atlas Data Federation and Online Archive Active
MongoDB Atlas for Government Active
MongoDB Atlas Stream Processing Active
MongoDB Charts Active
MongoDB Cloud Active
MongoDB Support Portal Active

Latest MongoDB outages and incidents.

View the latest incidents for MongoDB and check for official updates:

Updates:

  • Time: Feb. 12, 2024, 11:26 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 12, 2024, 11:15 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 12, 2024, 8:18 p.m.
    Status: Investigating
    Update: Users of Atlas Data Federation and Online Archive may see increased query latency for some queries in us-east-1.

Updates:

  • Time: Feb. 11, 2024, 3:40 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 11, 2024, 2:11 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 9, 2024, 6:18 p.m.
    Status: Identified
    Update: The fix has been identified and we're working with our upstream provider on implementing a fix.
  • Time: Feb. 9, 2024, 2:49 p.m.
    Status: Investigating
    Update: We are currently aware of reports that creating new Identity Providers for Federated Authentication is failing. We are investigating this issue.

Updates:

  • Time: Jan. 26, 2024, 10:28 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 26, 2024, 8:35 p.m.
    Status: Monitoring
    Update: We have implemented a fix and is observing that the system is recovering.
  • Time: Jan. 26, 2024, 6:39 p.m.
    Status: Identified
    Update: We have identified an issue that is causing delays to modification requests to Atlas Serverless instances across multiple regions. This includes creation of new instances and deletion of existing instances. The instances themselves should continue to be fully available and responsive to queries. We are working toward remediation and will provide updates as we have more information.

Updates:

  • Time: Jan. 21, 2024, 12:39 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 21, 2024, 4:37 a.m.
    Status: Identified
    Update: Due to an Azure Resource Manager outage in some regions, customers will experience delays performing operations on Azure Clusters. Please see https://azure.status.microsoft/en-us/status for details.

Updates:

  • Time: Feb. 8, 2024, 6:18 p.m.
    Status: Postmortem
    Update: On 1/9/24, a new version of the "Atlas Proxy" was released. One of the Atlas Proxies's responsibilities is syncing cluster configurations to the Atlas Shared and Atlas Serverless tiers. The new version updated this syncing protocol, but contained a bug where under certain circumstances it would sync cluster configuration much too frequently. On 1/17/24 at 08:00 UTC, this bug was triggered across the fleet, immediately overloading both the Atlas Control Plane application servers that handle requests from the Atlas Data Plane and the database clusters for those application servers. At 13:30 UTC, the Atlas Proxies were identified as the root cause of the increased load, and they were throttled. This stopped Shared/Serverless tier cluster changes from propagating with the intention of taking load off the system so Atlas Dedicated operations could proceed as normal. Unfortunately, the backlog of Atlas Dedicated changes overloaded numerous other internal services. An additional consequence of the Atlas Proxy throttling was that ongoing OS security patching caused some servers to reboot during the incident, and after the reboot, the Proxies were not able to initialize correctly due to being throttled. This left a set of Shared and Serverless Tier customers unable to connect to their clusters. Over the next few hours, internal systems continued to be repaired. The specific bug in the Atlas Proxy was identified, and a plan to roll it back was established. By 17:00 UTC, Atlas Dedicated user driven changes were being processed with only small delays. By 23:30 UTC, all internal systems were operating normally, the Atlas Proxy was rolled back/unthrottled, and there were no longer any delays in processing Atlas cluster changes.
  • Time: Jan. 18, 2024, 2:08 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 18, 2024, 12:05 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Jan. 18, 2024, 12:04 a.m.
    Status: Monitoring
    Update: The system has recovered and we are continuing to monitor.
  • Time: Jan. 17, 2024, 11:56 p.m.
    Status: Investigating
    Update: The system is largely recovered, but we are monitoring closely. Issues experienced by some customers connecting to Atlas Shared Tier or Atlas Serverless clusters were resolved around 23:00 UTC. Connections to Atlas Dedicated clusters and performance of Atlas Dedicated clusters are not and have not been impacted.
  • Time: Jan. 17, 2024, 11:20 p.m.
    Status: Investigating
    Update: The system is starting to recover. - Issues connecting to Atlas Shared Tier and Atlas Serverless Clusters should be resolved. - Metrics for some Atlas Serverless Clusters may still be delayed - Creation of new Atlas clusters is experiencing a delay due to a delay in DNS propagation - User-initiated requests for changes to Atlas clusters are processing in a timely manner with the exception of changes that require new DNS entries (e.g. adding a new node) Connections to Atlas Dedicated clusters and performance of Atlas Dedicated clusters are not and have not been impacted.
  • Time: Jan. 17, 2024, 11:13 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Jan. 17, 2024, 8:46 p.m.
    Status: Investigating
    Update: We are continuing to see delays in metrics for Atlas Shared Tier and Atlas Serverless clusters. Additionally all modifications for the Atlas Clusters are delayed including creation of new clusters/instances, ip access list, and user changes. We have also identified an issue with connections to some Atlas Shared Tier and Atlas Serverless clusters.
  • Time: Jan. 17, 2024, 5:20 p.m.
    Status: Investigating
    Update: We are continuing to delays in metrics for Atlas Shared Tier and Atlas Serverless clusters. Additionally all modifications for the Atlas Shared Tier clusters and Atlas Serverless instances are delayed including creation of new clusters/instances, ip access list, and user changes. For Atlas Dedicated clusters, user requested changes to Atlas clusters (modifying the Network Access list, adding an additional node in a replica set, adding a new Database User, etc.) are being processed in a timely manner. However, scheduled actions such as snapshots are experiencing delays. The delay for scheduled actions is currently decreasing.
  • Time: Jan. 17, 2024, 3:02 p.m.
    Status: Investigating
    Update: Metrics for Atlas Shared Tier and Atlas Serverless clusters are still experiencing delays. User requested changes to Atlas clusters (modifying the Network Access list, adding an additional node in a replica set, adding a new Database User, etc.) are being processed in a timely manner. However, scheduled actions such as snapshots are experiencing delays.
  • Time: Jan. 17, 2024, 1:33 p.m.
    Status: Investigating
    Update: We have partially remediated the issue. However, metrics for Atlas Shared Tier and Atlas Serverless clusters are still experiencing delays. Changes to Atlas clusters (including IP Access List modifications, topology and tier changes, or the creation of new clusters) may still be experiencing some delays.
  • Time: Jan. 17, 2024, 12:07 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue. No root cause or remediation has been reached at this time.
  • Time: Jan. 17, 2024, 11:03 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue. No root cause or remediation has been reached at this time.
  • Time: Jan. 17, 2024, 9:07 a.m.
    Status: Investigating
    Update: Atlas clusters may show as Degraded due to the delayed metrics data - however, there is no impact to the clusters themselves. (This is a false positive.) There may be a delay processing requested changes to Atlas clusters.
  • Time: Jan. 17, 2024, 8:33 a.m.
    Status: Investigating
    Update: We are investigating an issue delaying the processing of metrics points for Atlas and Cloud Manager.

Check the status of similar companies and alternatives to MongoDB

Akamai
Akamai

Systems Active

Nutanix
Nutanix

Systems Active

LogicMonitor
LogicMonitor

Systems Active

Acquia
Acquia

Systems Active

Granicus System
Granicus System

Systems Active

CareCloud
CareCloud

Systems Active

Redis
Redis

Systems Active

integrator.io
integrator.io

Systems Active

NinjaOne Trust

Systems Active

Pantheon Operations
Pantheon Operations

Systems Active

Securiti US
Securiti US

Systems Active

Scaleway
Scaleway

Issues Detected

Frequently Asked Questions - MongoDB

Is there a MongoDB outage?
The current status of MongoDB is: Systems Active
Where can I find the official status page of MongoDB?
The official status page for MongoDB is here
How can I get notified if MongoDB is down or experiencing an outage?
To get notified of any status changes to MongoDB, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of MongoDB every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does MongoDB do?
Accelerate idea-to-market process with a developer data platform powered by MongoDB, a user-friendly modern database.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free