Mongodb

Jun 10, 23:00 UTC
Completed - The scheduled maintenance has been completed.

Jun 10, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 9, 17:28 UTC
Update - We will be undergoing scheduled maintenance during this time.

Jun 9, 17:28 UTC
Scheduled - We will perform scheduled internal maintenance on Wednesday, June 10, 2026. During this maintenance window, some users may experience 5–10 minutes of elevated latency or intermittent request issues for a subset of MongoDB Atlas API functionality, including authentication, Atlas API, and …

Jun 8, 23:00 UTC
Completed - The scheduled maintenance has been completed.

Jun 8, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 8, 13:41 UTC
Update - We will be undergoing scheduled maintenance during this time.

Jun 8, 13:40 UTC
Scheduled - We will perform scheduled internal maintenance on Monday, June 8, 2026. During this maintenance window, some users may experience 5–10 minutes of elevated latency or intermittent request issues for a subset of MongoDB Atlas API functionality, including authentication, Atlas API, and …

Jun 4, 17:39 UTC
Resolved - This incident has been resolved.

Jun 4, 15:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results

Jun 3, 15:46 UTC
Update - AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.

We strongly recommend that customers with workloads in AWS me-central-1 act now to …

Jun 3, 00:11 UTC
Resolved - Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.

Jun 3, 00:05 UTC
Monitoring - All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.

Jun 3, 00:01 UTC
Update - Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.

Jun 2, 23:42 UTC
Identified - We've identified an issue with networking in GCP regions and are working on fix …

May 28, 23:15 UTC
Resolved - The issue has been resolved.

May 28, 22:02 UTC
Investigating - Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration.

We are investigating this issue.

May 24, 02:05 UTC
Resolved - This incident has been resolved.

May 24, 00:14 UTC
Monitoring - We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.

May 23, 20:14 UTC
Identified - We have identified the root cause of the search query failures and are working on a mitigation for impacted clusters. Clusters with dedicated search nodes are unaffected. Some clusters with colocated search nodes may see search query failures.

May 23, 19:48 UTC
Investigating - We are investigating an issue impacting some …

May 22, 22:17 UTC
Resolved - The data plane node log download has recovered.

May 22, 21:17 UTC
Monitoring - We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.

May 22, 20:32 UTC
Investigating - The data plane node logs (mongod, audit logs, etc.) are unavailable since May 14th 4am UTC for clusters in GCP and AWS gov-cloud regions. We have identified the root cause and are actively working on a fix.