MongoDB Atlas Status
Last incident: 8/22/2025
Recent Incidents
Aug 22, 16:44 UTC
Resolved - This incident has been resolved.
Aug 22, 15:22 UTC
Update - We have identified an issue connecting AWS Marketplace as a payment method for MongoDB Atlas since approximately August 19, 2025. Affected users will see a form and then a confirmation screen, but the addition of the payment method will not succeed.
Existing connections and cluster health is unaffected.
Aug 22, 15:06 UTC
Identified - We have identified an issue connecting AWS Marketplace as a payment method for MongoDB Atlas. Affected users will see a form and then a confirmation screen, but the addition of the payment method will not succeed.
Existing connections and cluster health is unaffected.
Aug 21, 00:35 UTC
Resolved - This incident has been resolved.
Aug 21, 00:03 UTC
Investigating - We're investigating an issue impacting Atlas Azure cluster snapshot creation (EUROPE_WEST region only). This only affects new snapshot creation. Existing snapshots are not affected.
Aug 19, 00:25 UTC
Resolved - This incident has been resolved.
Aug 18, 23:31 UTC
Monitoring - Impacted free tier M0 AWS us-east-1 clusters are now healthy. Customers that attempted an upgrade of their M0 cluster to a dedicated instance tier can now retry their request.
Aug 18, 19:38 UTC
Update - We continue to work on a fix for the impacted M0 clusters. No additional AWS us-east-1 M0 clusters have been impacted since the original post.
Aug 18, 12:46 UTC
Update - We continue to work on a fix for impacted M0 clusters.
Aug 18, 07:53 UTC
Identified - We've identified the issue causing some AWS us-east-1 free tier M0 clusters to be in a degraded state. The team is working on a fix.
Aug 18, 07:27 UTC
Investigating - We're investigating an issue impacting some AWS us-east-1 free tier (M0 instance size) clusters. These clusters are experiencing connection issues and a failure to upgrade to dedicated instance sizes. This issue impacts <1% of AWS us-east-1 M0 clusters.
Aug 11, 17:22 UTC
Resolved - This incident has been resolved.
Aug 11, 17:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 11, 16:26 UTC
Update - Infrastructure rollback has completed and affected Azure clusters are recovering. The previously suggested firewall update is no longer necessary.
Aug 11, 16:09 UTC
Update - We are rolling back an infrastructure change that should allow Azure clusters with KeyVault to recover but affected customers can restore access more quickly by updating their KeyVault firewall with the latest Atlas control plane IP addresses: https://www.mongodb.com/docs/atlas/setup-cluster-security/#allow-access-to-or-from-the-service-control-plane
Aug 11, 15:58 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 11, 15:53 UTC
Investigating - We are currently investigating an issue affecting Azure clusters with KeyVault enabled.
Aug 11, 16:28 UTC
Resolved - This incident has been resolved.
Aug 11, 15:30 UTC
Investigating - We are currently investigating an issue with viewing existing charts and creating new ones. Chart configurations are unaffected.