← Live dashboard

AWS Cluster DNS Changes Degraded Performance

ResolvedmajorOfficial source confirmedSpecific component onlyFirst recorded update May 7, 2026, 03:17 PM · Resolved May 7, 2026, 10:15 PM

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

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with MongoDB Atlas now? Check the current status

Affected services

MongoDB Atlas for Government

Updates (7)

  1. May 7, 2026, 10:15 PM
    AWS Cluster DNS Changes Degraded Performance

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

    MongoDB Atlas ↗
  2. May 7, 2026, 07:47 PM
    AWS Cluster DNS Changes Degraded Performance

    We are continuing to monitor for any further issues.

    MongoDB Atlas ↗
  3. May 7, 2026, 07:47 PM
    AWS Cluster DNS Changes Degraded Performance

    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.

    MongoDB Atlas ↗
  4. May 7, 2026, 05:50 PM
    AWS Cluster DNS Changes Degraded Performance

    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.

    MongoDB Atlas ↗
  5. May 7, 2026, 04:58 PM
    AWS Cluster DNS Changes Degraded Performance

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

    MongoDB Atlas ↗
  6. May 7, 2026, 03:20 PM
    AWS Cluster DNS Changes Degraded Performance

    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.

    MongoDB Atlas ↗
  7. May 7, 2026, 03:17 PM
    AWS Cluster DNS Changes Degraded Performance

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

    MongoDB Atlas ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow MongoDB Atlas's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.