MongoDB incident

AWS Cluster DNS Changes Degraded Performance

MongoDB is currently experiencing a major incident affecting MongoDB Atlas for Government, which began 3h ago. The vendor's full update timeline is below.

Started
May 07, 2026, 03:17 PM UTC
Resolved
Ongoing
Duration
● 2h 48m
Detected by Pingoru
May 07, 2026, 03:17 PM UTC

Affected components

MongoDB Atlas for Government

Update timeline

  1. identified May 07, 2026, 03:17 PM UTC

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

  2. identified May 07, 2026, 03:20 PM 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.

  3. identified May 07, 2026, 04:58 PM UTC

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

  4. investigating May 07, 2026, 05:50 PM 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.

Looking to track MongoDB downtime and outages?

Pingoru polls MongoDB's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when MongoDB reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track MongoDB alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring MongoDB for free

5 free monitors · No credit card required