MongoDB Atlas Status · History · Incident #2135

RESOLVED

AWS Cluster DNS Changes Degraded Performance

Major · Started May 7, 2026 · 3:17 PM

Duration

6h 57m
Severity

Major
Detection lead

—
User reports

—

Summary

AWS Cluster DNS Changes Degraded Performance

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

Started

May 7, 2026 · 3:17 PM
Resolved

May 7, 2026 · 10:15 PM
Duration

6h 57m
Severity

Major

Event timeline

How this incident unfolded

◆

Identified
May 7 · 3:17 PM MongoDB Atlas

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

Identified
May 7 · 3:20 PM MongoDB Atlas

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.
◆

Identified
May 7 · 4:58 PM MongoDB Atlas

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

Investigating
May 7 · 5:50 PM MongoDB Atlas

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.
◉

Monitoring
May 7 · 7:47 PM MongoDB Atlas

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.
◉

Monitoring
May 7 · 7:47 PM MongoDB Atlas

We are continuing to monitor for any further issues.
✓

Resolved
May 7 · 10:15 PM MongoDB Atlas

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

Pattern

Other recent incidents

Browse full incident history →

Get alerted before the next MongoDB Atlas outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free