Major incident

MongoDB Cloud: AWS Cluster DNS Changes Degraded Performance

May 7, 2026, 15:17 UTC
started
22:15 UTC
resolved
6 h 58 min
duration

Affected: MongoDB Atlas for Government

Current status of MongoDB Cloud: Operational — live MongoDB Cloud status

Timeline

  1. May 7, 2026, 15:17 UTC
    identified
    DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.
  2. May 7, 2026, 15:20 UTC
    identified
    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. May 7, 2026, 16:58 UTC
    identified
    Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.
  4. May 7, 2026, 17:50 UTC
    investigating
    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. May 7, 2026, 19:47 UTC
    monitoring
    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. May 7, 2026, 19:47 UTC
    monitoring
    We are continuing to monitor for any further issues.
  7. May 7, 2026, 22:15 UTC
    resolved
    DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.

Updates as published by MongoDB Cloud (original).

Other services with incidents at the same time

More MongoDB Cloud incidents