MongoDB Atlas outage: AWS Cluster DNS Changes Degraded Performance

Affected components

• MongoDB Atlas for Government

1. resolvedMay 7, 2026, 22:15 UTC

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

2. monitoringMay 7, 2026, 19:47 UTC

   We are continuing to monitor for any further issues.

3. monitoringMay 7, 2026, 19:47 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.

4. investigatingMay 7, 2026, 17:50 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. identifiedMay 7, 2026, 16:58 UTC

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

6. identifiedMay 7, 2026, 15:20 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.

7. identifiedMay 7, 2026, 15:17 UTC

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

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.

• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Mailgun: Automatic Sender Security Records Not ProvisioningMinor · May 6, 2026, 15:40 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history