MongoDB incident

Delays in cluster creation and adding new cluster nodes in Azure East US 2 region

Resolved after 1 hour 22 minutes, affecting MongoDB Cloud, on March 30, 2026.

resolved Mar 30, 2026, 11:10 PM UTC

We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.

Started
Mar 30, 2026, 09:47 PM UTC
Resolved
Mar 30, 2026, 11:10 PM UTC
Duration
1h 22m
Detected by Pingoru
Mar 30, 2026, 09:47 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. identified Mar 30, 2026, 09:47 PM UTC

    Identified: Some clusters in the Azure East US 2 region will see delays provisioning new clusters or adding additional nodes to their existing clusters due to Azure capacity constraints. What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region. User action: As a workaround, users can provision clusters in other Azure regions.

  2. resolved Mar 30, 2026, 11:10 PM UTC

    We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.

Your product runs on more than MongoDB

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →