MongoDB incident

Delayed cluster configuration affecting free and flex users

Minor Resolved View vendor source →

MongoDB experienced a minor incident on July 29, 2026 affecting MongoDB Cloud, lasting 41m. The incident has been resolved; the full update timeline is below.

Started
Jul 29, 2026, 06:55 PM UTC
Resolved
Jul 29, 2026, 07:37 PM UTC
Duration
41m
Detected by Pingoru
Jul 29, 2026, 06:55 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. investigating Jul 29, 2026, 06:55 PM 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.

  2. identified Jul 29, 2026, 07:06 PM UTC

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

  3. monitoring Jul 29, 2026, 07:31 PM UTC

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

  4. resolved Jul 29, 2026, 07:37 PM UTC

    This incident has been resolved.