MongoDB incident

DNS Resolution failures for public IP addresses within 31.89.0.0/24

Minor Resolved View vendor source →
Started
Feb 13, 2026, 04:11 PM UTC
Resolved
Feb 13, 2026, 05:57 PM UTC
Duration
1h 46m
Detected by Pingoru
Feb 13, 2026, 04:11 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. investigating Feb 13, 2026, 04:11 PM UTC

    We are investigating an issue with DNS resolution for public IP addresses within 31.89.0.0/24. We are engaging with AWS support to remediate the situation.

  2. identified Feb 13, 2026, 04:42 PM UTC

    We have identified the root cause and are working on backfilling those records with AWS support. We have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.

  3. resolved Feb 13, 2026, 05:57 PM UTC

    The DNS records have been backfilled and clusters that had these IP addresses should be recovered.

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