← Back to MongoDB Atlas History
major✓ Resolved
AWS Cluster DNS Changes Degraded Performance
Status
resolved
Duration
7h 3m
Updates
6
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedThu, May 7, 2026, 10:20 PM
This incident has been resolved.
monitoringThu, May 7, 2026, 07:47 PM
We are continuing to monitor for any further issues.
monitoringThu, May 7, 2026, 07:47 PM
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.
investigatingThu, May 7, 2026, 05:50 PM
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.
identifiedThu, May 7, 2026, 04:58 PM
Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.
identifiedThu, May 7, 2026, 03:20 PM
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.
identifiedThu, May 7, 2026, 03:17 PM
DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.
📊 TECHNICAL DETAILS
Internal ID
800109a3-ba63-4fc8-94f2-c4af80dcb581
External ID
1t1nk96wgyx3
🕐 Started
Thu, May 7, 2026, 03:17 PM
🔄 Last Updated
Thu, May 7, 2026, 10:20 PM
✓ Resolved
Thu, May 7, 2026, 10:20 PM
MAJOR
Impact Level
7h 3m
Total Duration
6
Status Updates
Affected Components
MongoDB Atlas for Government
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed