MongoDB Cloud Status

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

Please note that this is courtesy notice and no action is required from you if you do not pin intermediate certificates from Let's Encrypt (LE) and/or Google Trust Services (GTS) in your environment when connecting to Atlas dedicated clusters.

Let's Encrypt (LE) and Google Trust Services (GTS) have issued additional intermediate certificates to their services. Intermediate certificates act as a secure bridge between root CAs (e.g. LE/GTS) and end entities to streamline management and reduce risk. We want to emphasize that the changes mentioned below related to intermediate certificate authority are not made by MongoDB but by LE and GTS sometime in 2026 which are the Certificate Authority (CA) providers for TLS certificates for all MongoDB Atlas clusters.

Let’s Encrypt: https://letsencrypt.org/2025/11/24/gen-y-hierarchy
Google Trust Service: https://pki.goog/updates/august2025-intermediate-update.html

MongoDB does not recommend hardcoding or pinning intermediate CAs in your application; please refer to the best practices recommended by MongoDB here.

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.

Resolved - The DNS records have been backfilled and clusters that had these IP addresses should be recovered.
Feb 13, 17:57 UTC

Identified - We have identified the root cause and are working on backfilling those records with AWS support.

We have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.

Investigating - We are investigating an issue with DNS resolution for public IP addresses within 31.89.0.0/24. We are engaging with AWS support to remediate the situation.
Feb 13, 16:11 UTC

Resolved - We have identified and resolved the issue. Atlas UI will load without a delay now.
Feb 13, 07:55 UTC

Investigating - We are currently investigating reports of the slow loading of the Atlas web UI.
Feb 13, 07:20 UTC

Resolved - This incident has been resolved.
Feb 12, 23:10 UTC

Monitoring - We have implemented the fix. Customers will now be able to create new clusters on AWS.
Feb 12, 23:08 UTC

Identified - We have identified the root cause and are implementing a fix to remediate the situation
Feb 12, 23:00 UTC

Investigating - We are currently investigating elevated errors for customers attempting to create a cluster on AWS
Feb 12, 22:10 UTC

Resolved - Many nodes have recovered in the impacted region, however there are still some impacted nodes that are recovering. Azure's latest update at 11:05 UTC on 07 February 2026 indicates they are observing signs of partial recovery and that recovery efforts remain in progress.

We are resolving the status post as we expect our system to automatically remediate any lingering issues. Please follow the Azure status post for further updates on the regional outage remediation efforts from their end.

Monitoring - We are seeing some nodes in the impacted Azure West US region recovering. We will continue to monitor and provide updates.
Feb 7, 10:11 UTC

Identified - Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status

Ongoing Service Degradation in West US

We are aware of an issue impacting a subset of customers in West US, Our Engineering team is actively investigating and working on mitigation. We will provide more information shortly.

This message was last updated at 09:10 UTC on 07 February 2026

Investigating - We are observing widespread issues in Azure West US. Customers may see nodes reporting as “down” and delayed cluster modifications for Azure clusters in West US.
Feb 7, 09:07 UTC

Resolved - The root cause has been identified and the issue is now resolved.
Feb 4, 21:06 UTC

Update - We are continuing to investigate the issue. A subset of customers may experience incomplete metric data in their DataDog integration. We'll share updates as more information becomes available.
Feb 3, 16:12 UTC

Investigating - We are currently experiencing degraded service with our DataDog integration for several DataDog regions. This may result in incomplete metrics, or issues with alerting for customers using the DataDog integration.

We are investigating this issue.

Resolved - This incident has been resolved.
Feb 3, 19:15 UTC

Update - We are continuing to work on a fix for this issue.
Feb 3, 18:50 UTC

Identified - Users may be unable to access the MongoDB Atlas App Services triggers page and may see authentication failures when using the Admin API. As a result, some users may be unable to create, update, or manage App Services resources. We have identified an issue with a recent change to authentication and are working to revert those changes.
Feb 3, 18:49 UTC