MongoDB Atlas incident: Delayed cluster configuration affecting free and flex users

Affected components

• MongoDB Cloud

1. resolvedJul 29, 2026, 19:37 UTC

   This incident has been resolved.

2. monitoringJul 29, 2026, 19:31 UTC

   We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.

3. identifiedJul 29, 2026, 19:06 UTC

   We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.

4. investigatingJul 29, 2026, 18:55 UTC

   We are investigating an issue with cluster configuration updates getting delayed for a subset of users on free and flex tiers. Cluster access is unaffected.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• HashiCorp Vault: HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider UpgradeMajor · Jul 29, 2026, 12:36 UTC
• RevenueCat: Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"Minor · Jul 27, 2026, 10:14 UTC
• DigitalOcean: Response Degradation Impacting Kimi-K3Minor · Jul 29, 2026, 17:56 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history