MongoDB Outage History

We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 24 at 22:00 UTC.

We have identified the issue affecting the Business Intelligence (BI) Connector in MongoDB Atlas for Government. We are working on a fix. While no workaround exists, data remains accessible to MongoDB clients. Affected users will not be able to connect to their clusters' BI Connectors. Cluster health is unaffected.

Identified: Some clusters in the Azure East US 2 region will see delays provisioning new clusters or adding additional nodes to their existing clusters due to Azure capacity constraints. What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region. User action: As a workaround, users can provision clusters in other Azure regions.

The issue has been identified and we are working on a fix.

We have identified an issue affecting the Clusters page in MongoDB Atlas. Affected users may see a blank page when trying to view their Clusters page. Cluster health is unaffected.

Impact: Some users may be unable to log into the Atlas for Government UI using SSO. Specifically, users accessing Atlas for Government via a saved SSO login URL may receive an error, and users attempting to log in via a federated identity provider link may be unable to complete authentication. Root cause: We have identified an issue with SSO routing that is preventing some federated login flows from completing successfully. These issues started around 2026-03-18 2:30 UTC. What you might see: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User action: As a workaround, users can log in by entering their email address directly at https://account.mongodbgov.com and following the standard prompts. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as we progress toward resolution, or if we observe any change in impact to Atlas for Government.

The issue has been identified and a fix is being implemented.

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.

We have identified the root cause and are implementing a fix to remediate the situation

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

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.

We are continuing to work on a fix for this issue.