MongoDB incident

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

MongoDB experienced a notice incident on March 30, 2026 affecting MongoDB Cloud, lasting 1h 22m. The incident has been resolved; the full update timeline is below.

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

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.
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.