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

Scheduled Maintenance - Adding additional IP addresses to the MongoDB Control Plane Oct 1, 2025 22:00-23:00 UTC

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.
Posted on Sep 15, 2025 - 15:32 UTC
Sep 17, 2025

No incidents reported today.

Sep 16, 2025

No incidents reported.

Sep 15, 2025

No incidents reported.

Sep 14, 2025

No incidents reported.

Sep 13, 2025

No incidents reported.

Sep 12, 2025

No incidents reported.

Sep 11, 2025

No incidents reported.

Sep 10, 2025
Delayed cluster modifications in Azure East US 2
Resolved - This incident has been resolved.
Sep 10, 20:23 UTC
Monitoring - We're seeing capacity errors come down in Azure Eastus2. We will continue monitoring the situation.
Sep 10, 20:06 UTC
Update - Azure Eastus2 continues to experience elevated errors. Azure has now published it on their public status page here https://azure.status.microsoft/en-us/status
Sep 10, 17:50 UTC
Identified - We are observing elevated error when provisioning resources due to an Azure service issue. Customers may see delayed cluster modifications for Azure clusters in East US 2. Please refer to the Azure dashboard for their service issue updates.
Sep 10, 12:34 UTC
Sep 9, 2025

No incidents reported.

Sep 8, 2025

No incidents reported.

Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

Sep 4, 2025
Elevated Azure Capacity Errors
Resolved - This incident has been resolved.
Sep 4, 20:42 UTC
Identified - We have identified escalating Azure capacity issues in the following regions eastus and germanywestcentral for M30+. We are taking remediation actions on these instance sizes. For M10 and M20s we recommend upgrading to another instance tier or moving it to a different region.
Sep 4, 17:36 UTC
Sep 3, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage