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

Update - We have sent direct email notifications to organizations with detected TLS 1.0/1.1 usage; if you did not receive a notification, no action is required at this time.
Nov 19, 2025 - 16:39 UTC
Scheduled - 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 who do have TLS 1.0/1.1 usage:

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.

Oct 31, 2025 - 22:05 UTC
Nov 24, 2025

No incidents reported today.

Nov 23, 2025

No incidents reported.

Nov 22, 2025

No incidents reported.

Nov 21, 2025

No incidents reported.

Nov 20, 2025

No incidents reported.

Nov 19, 2025
Resolved - 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.
Nov 19, 18:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 19, 18:22 UTC
Identified - 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.

Nov 19, 17:55 UTC
Nov 18, 2025

No incidents reported.

Nov 17, 2025

No incidents reported.

Nov 16, 2025

No incidents reported.

Nov 15, 2025

No incidents reported.

Nov 14, 2025

No incidents reported.

Nov 13, 2025

No incidents reported.

Nov 12, 2025
Resolved - The fix was successful and we are no longer seeing degraded performance within our DataDog integration.
Nov 12, 13:19 UTC
Monitoring - We have identified the cause and have implemented a fix. We are monitoring its impact.
Nov 12, 03:08 UTC
Investigating - We are currently experiencing degraded performance with our DataDog integration. This may result in delayed metrics, incomplete metrics, or issues with alerting for customers using the DataDog integration.

We are currently investigating this issue.

Nov 11, 23:32 UTC
Nov 11, 2025
Nov 10, 2025

No incidents reported.