MongoDB incident

Elevated errors for cluster creation on AWS

Critical Resolved View vendor source →

MongoDB experienced a critical incident on February 12, 2026 affecting MongoDB Cloud, lasting 59m. The incident has been resolved; the full update timeline is below.

Started
Feb 12, 2026, 10:10 PM UTC
Resolved
Feb 12, 2026, 11:10 PM UTC
Duration
59m
Detected by Pingoru
Feb 12, 2026, 10:10 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. investigating Feb 12, 2026, 10:10 PM UTC

    We are currently investigating elevated errors for customers attempting to create a cluster on AWS

  2. identified Feb 12, 2026, 11:00 PM UTC

    We have identified the root cause and are implementing a fix to remediate the situation

  3. monitoring Feb 12, 2026, 11:08 PM UTC

    We have implemented the fix. Customers will now be able to create new clusters on AWS.

  4. resolved Feb 12, 2026, 11:10 PM UTC

    This incident has been resolved.