Oct 8, 21:56 UTC
Resolved - This incident has been resolved.

Oct 8, 16:43 UTC
Identified - We have identified escalating Azure capacity issues in the eastus region for M10 and M20s. We recommend scaling up to another instance tier or moving it to a different region.

Oct 7, 20:03 UTC
Resolved - This incident has been resolved.

Oct 7, 19:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 7, 17:44 UTC
Identified - We have identified the cause of the issue and have taken corrective actions. We are monitoring the impact of those mitigations. During this time Host Down alerts, metrics, and some Atlas Cluster Operations may still be delayed or missing.

Oct 7, 15:45 UTC
Update - We are continuing to investigate the issue. During this time Host Down alerts will not fire and metrics may be missing or delayed for Atlas and Cloud Manager Clusters. Cluster operations may also be delayed.

Oct 7, 13:42 UTC
Investigating - We are currently investigating a delay in our metric ingestion pipeline. Customers may see delays in cluster operations.

Oct 6, 23:19 UTC
Resolved - This incident has been resolved.

Oct 6, 22:12 UTC
Monitoring - The system is in healthy state and cluster operations are no longer delayed. We are monitoring for any residual effects.

Oct 6, 21:42 UTC
Identified - The system had unusually high load causing delays in operations. The issue has been identified and we are working on fix.

Oct 6, 20:48 UTC
Update - We are continuing to investigate the issue. Atlas Cluster operations (including metrics ingestion) are delayed but underlying cluster health is unaffected.

Oct 6, 19:33 UTC
Investigating - Some Atlas cluster operations are delayed. This includes cluster operations and metrics ingestion. We are currently investigating the issue.

Oct 2, 21:46 UTC
Resolved - This incident has been resolved. Upgrades should complete normally. Any affected clusters should be returned to healthy.

Oct 2, 21:45 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 2, 18:13 UTC
Identified - The issue has been identified and a fix is being implemented.

Oct 1, 23:00 UTC
Completed - The scheduled maintenance has been completed.

Oct 1, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 15, 15:32 UTC
Scheduled - MongoDB Control Plane will be undergoing planned maintenance at 5 PM ET on Oct 1, 2025. We will be adding additional IP addresses to the MongoDB Control Plane.

We are improving how MongoDB manages the control plane for Atlas clusters and Cloud Manager to ensure high-quality service with improved availability, sustainability and scalability. Please note that this is a follow-up communication to our June 2025 communications titled “Action May Be Required - Upcoming changes to the IP addresses of MongoDB Atlas Control Plane” and “Action May Be Required - Upcoming changes to the IP addresses of MongoDB Cloud Manager Control Plane”.

If your applications have hard-coded dependencies on the Atlas Control Plane, your infrastructure will need to be updated with additional IP addresses before September 30, 2025. If you were affected by the recent issue relating to Azure clusters with KeyVault enabled (https://status.mongodb.com/incidents/nlwkk8xbzjhm), you must take this action.


To ensure uninterrupted service, please use the admin API https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Root/operation/returnAllControlPlaneIpAddresses, which always reflects up to date Atlas Control Plane IP addresses. We advise against hard-coding these IP addresses. Instead, we recommend that you regularly update your rules using the API endpoint to maintain service continuity.

For Atlas customers: This action is required for scenarios (https://www.mongodb.com/docs/atlas/setup-cluster-security/#allow-access-to-or-from-the-service-control-plane) where you have set up firewalls, access control lists, or security groups that allow inbound traffic from these IP addresses.

For Cloud Manager customers: The action may be required for the cloud manager customers for scenarios (https://www.mongodb.com/docs/cloud-manager/reference/firewall-configuration/#ipaddr-addresses-for-alert-webhooks) where you have set up firewalls, access control lists, or security groups on any host that allow inbound traffic from these IP addresses. Your Alert Webhooks may not work properly if the suggested changes are not done in time, however, you will still be able to monitor, backup, and automate any changes as usual.

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.