MongoDB Cloud

All Systems Operational

MongoDB Cloud ? Operational
MongoDB Support Portal ? Operational
MongoDB Atlas App Services and Device Sync ? Operational
MongoDB Atlas Data Federation and Online Archive ? Operational
MongoDB Atlas Search ? Operational
MongoDB Charts ? Operational
MongoDB Atlas Stream Processing ? Operational
MongoDB Atlas for Government ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Notification of EOL of TLS 1.0 and TLS 1.1 in MongoDB Atlas Dec 1, 2025 00:00-01:00 UTC

As we previously communicated early this year, MongoDB is enhancing our security posture by discontinuing support for older, less secure versions of Transport Layer Security (TLS) within Atlas. This decision aligns with industry best practices.

We have begun disallowing new use of TLS 1.0 and TLS 1.1 in Atlas and these versions of TLS will be completely removed from MongoDB Atlas on or shortly after 1 December, 2025.

This may have the following impact on our customers:

API Usage: If you utilize the MongoDB API (e.g., via Terraform or similar automation tools) to programmatically create or manage clusters, API calls attempting to provision or configure a cluster with TLS 1.0 or TLS 1.1 will fail after 1 December 2025. This applies to both new cluster creations and modifications to existing clusters.

Public API: For the endpoints POST /api/atlas/v2/groups/{groupId}/clusters and PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}, advancedConfiguration.minimumEnabledTlsProtocol should specify “TLS1_2” (and NOT “TLS1_0” or “TLS1_1”)

Terraform: For mongodbatlas_cluster and mongodbatlas_advanced_cluster resource, advanced_configuration.minimum_enabled_tls_protocol must be “TLS1_2”; older standards “TLS1_0” and “TLS1_1” will fail to update the cluster or deploy.

Application Connectivity: Any applications, services, or tools that connect to your MongoDB Atlas clusters and are still relying on TLS 1.0 or TLS 1.1 will experience connection failures after 1 December 2025.

Recommended Actions:
Our systems are unable to distinguish between connections originating from production applications, non-production applications, or other traffic such as security scanners that customers may employ. Consequently, we cannot offer specific recommendations based on the source of residual TLS 1.0 and 1.1 connections. We encourage customers to consult our documentation (https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-advancedSettings-update/) for guidance on configuring TLS 1.2 and to reach out to our support team if you require assistance with this transition.

At MongoDB, we want you to have full confidence in the security and resiliency of our systems and products, which are designed to enable your company’s secure growth and innovation. If you have any questions or need assistance, please use the chat (https://www.mongodb.com/company/contact) in the Atlas UI or contact Support (https://support.mongodb.com/welcome) to talk to someone on our team.

Posted on Oct 31, 2025 - 22:05 UTC
Nov 7, 2025

No incidents reported today.

Nov 6, 2025
Resolved - We are resolving the status post as we expect our system to remediate any lingering issues. Please follow the Azure status post for further updates on the availability zone remediation efforts from their end.
Nov 6, 00:54 UTC
Update - Many nodes have recovered in the impacted Availability Zone, however there are still some impacted nodes that are recovering. Azure's latest update at 22:49 UTC on 05 November 2025 indicated recovery efforts remain in progress and they anticipate seeing signs of recovery in approximately on these storage scale units in approximately 90 minutes. We will continue to monitor and provide updates.
Nov 5, 23:53 UTC
Update - Azure updated their public status post at 21:13 UTC on 05 November 2025 to indicate they anticipate seeing signs of recovery for their services in approximately 3 hours. We will continue to monitor and provide updates.
Nov 5, 21:31 UTC
Monitoring - We are seeing nodes in the impacted Azure West Europe Availability Zone coming online. We expect full zone recovery to take a few more hours, and will continue to monitor and provide updates.
Nov 5, 20:47 UTC
Update - Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status

Thermal event in West Europe region

Impact Statement: Starting at approximately 17:00 UTC on 05 November 2025, a subset of customers using Virtual Machine, Azure Databricks, Azure Database for PostgreSQL flexible servers, MySQL flexible servers, Azure Kubernetes Service, Storage, Service Bus and Virtual Machine Scale Sets, among other affected services in the West Europe region may experience service disruptions or degraded performance due to a subset of storage scale units going offline due to a thermal event impacting data center cooling systems in a single availability zone. Resources in other availability zones reliant on these storage scale units may be impacted.

Current Status: We detected this issue via our automated service monitoring, which identified a spike in hardware temperatures and service incidents affecting multiple storage scale units. Cooling has been restored, and teams are working to recover the impacted storage scale units. The next update will be provided within 60 minutes, or as events warrant.

This message was last updated at 20:07 UTC on 05 November 2025

Nov 5, 20:13 UTC
Identified - Azure has posted to their Service Health dashboard indicating Virtual Machines in the West Europe region may experience service disruptions or degraded performance due to a thermal event impacting data center cooling systems in the region. Please refer to the Azure Service Health dashboard for their service issue updates.
Nov 5, 19:08 UTC
Investigating - We are observing widespread issues in a single AZ in Azure West Europe. Customers may see nodes reporting as "down" and delayed cluster modifications for Azure clusters in West Europe. There are three total AZs in Azure West Europe, and primary failover will be handled by MongoDB.
Nov 5, 18:57 UTC
Nov 5, 2025
Nov 4, 2025

No incidents reported.

Nov 3, 2025
Resolved - This incident has been resolved.
Nov 3, 21:13 UTC
Monitoring - We've identified the root cause which is an Azure outage: https://azure.status.microsoft/en-us/status. Will continue to monitor.
Nov 3, 20:03 UTC
Identified - The issue has been identified and a fix is being implemented.
Nov 3, 19:27 UTC
Investigating - 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.
Nov 3, 19:00 UTC
Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025

No incidents reported.

Oct 29, 2025
Resolved - Atlas is unaffected by the Azure network availability issue.
Oct 29, 18:33 UTC
Monitoring - 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.

Oct 29, 17:41 UTC
Resolved - This incident has been resolved.
Oct 29, 02:38 UTC
Monitoring - The fix has been deployed and Atlas cluster management operations are no longer delayed.
Oct 29, 02:34 UTC
Identified - 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.
Oct 29, 02:30 UTC
Oct 28, 2025

No incidents reported.

Oct 27, 2025

No incidents reported.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.