MongoDB incident

AWS Cluster DNS Changes Degraded Performance

Major Resolved View vendor source →

MongoDB experienced a major incident on May 7, 2026 affecting MongoDB Atlas for Government, lasting 6h 57m. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 03:17 PM UTC
Resolved
May 07, 2026, 10:15 PM UTC
Duration
6h 57m
Detected by Pingoru
May 07, 2026, 03:17 PM UTC

Affected components

MongoDB Atlas for Government

Update timeline

  1. identified May 07, 2026, 03:17 PM UTC

    DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.

  2. identified May 07, 2026, 03:20 PM UTC

    DNS changes for AWS clusters are currently degraded. Cluster topology modifications may be delayed or not able to complete successfully. We've identified the issue and are pushing out a patch.

  3. identified May 07, 2026, 04:58 PM UTC

    Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.

  4. investigating May 07, 2026, 05:50 PM UTC

    We are still seeing cases where new cluster update requests are failing to go through due to ACME related DNS issues. We are actively investigating this issue.

  5. monitoring May 07, 2026, 07:47 PM UTC

    We've identified a bad piece of metadata causing DNS issues. We've since patched this metadata and are seeing recovery in ACME updates for cluster topology changes. We will continue to monitor recovery.

  6. monitoring May 07, 2026, 07:47 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved May 07, 2026, 10:15 PM UTC

    DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.