Minor impactResolvedDatabases

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

MongoDB Atlas reported this minor-impact incident on its official status page on Jul 29, 2026, 18:55 UTC. It was resolved after 42 min.

Right now MongoDB Atlas is operational. Live MongoDB Atlas status →

🔔 Get alerted when MongoDB Atlas has issuesFree · email alerts · no credit card
Jul 29, 2026, 18:55 UTC
started
Jul 29, 2026, 19:37 UTC
resolved
42 min
duration
Minor
impact

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.

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 9 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 5h. See MongoDB Atlas's uptime and incident history