MongoDB incident

Some AWS us-east-1 free tier (M0 instance size) clusters in degraded state

Notice Resolved View vendor source →

MongoDB experienced a notice incident on August 18, 2025 affecting MongoDB Cloud, lasting 16h 57m. The incident has been resolved; the full update timeline is below.

Started
Aug 18, 2025, 07:27 AM UTC
Resolved
Aug 19, 2025, 12:25 AM UTC
Duration
16h 57m
Detected by Pingoru
Aug 18, 2025, 07:27 AM UTC

Affected components

MongoDB Cloud

Update timeline

  1. investigating Aug 18, 2025, 07:27 AM UTC

    We're investigating an issue impacting some AWS us-east-1 free tier (M0 instance size) clusters. These clusters are experiencing connection issues and a failure to upgrade to dedicated instance sizes. This issue impacts <1% of AWS us-east-1 M0 clusters.

  2. identified Aug 18, 2025, 07:53 AM UTC

    We've identified the issue causing some AWS us-east-1 free tier M0 clusters to be in a degraded state. The team is working on a fix.

  3. identified Aug 18, 2025, 12:46 PM UTC

    We continue to work on a fix for impacted M0 clusters.

  4. identified Aug 18, 2025, 07:38 PM UTC

    We continue to work on a fix for the impacted M0 clusters. No additional AWS us-east-1 M0 clusters have been impacted since the original post.

  5. monitoring Aug 18, 2025, 11:31 PM UTC

    Impacted free tier M0 AWS us-east-1 clusters are now healthy. Customers that attempted an upgrade of their M0 cluster to a dedicated instance tier can now retry their request.

  6. resolved Aug 19, 2025, 12:25 AM UTC

    This incident has been resolved.