Minor impactResolvedDatabases

MongoDB Atlas incident: DNS Resolution failures for public IP addresses within 31.89.0.0/24

MongoDB Atlas reported this minor-impact incident on its official status page on Feb 13, 2026, 16:11 UTC. It was resolved after 1h 46m.

Right now MongoDB Atlas is operational. Live MongoDB Atlas status →

🔔 Get alerted when MongoDB Atlas has issuesFree · email alerts · no credit card
Feb 13, 2026, 16:11 UTC
started
Feb 13, 2026, 17:57 UTC
resolved
1h 46m
duration
Minor
impact

Affected components

  • MongoDB Cloud
  1. resolvedFeb 13, 2026, 17:57 UTC

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

  2. identifiedFeb 13, 2026, 16:42 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. investigatingFeb 13, 2026, 16:11 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.

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.

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

MongoDB Atlas incident on Feb 13, 2026: DNS Resolution failures for public IP addresses within 31.89.0.0/24 · APIStatus.watch