Capacity Constrained Azure regions eastus, eastus2, germanywestcentral and more

This incident has been resolved.

We have deployed the mitigation for M30+ instance sizes, however M10 and M20 may still experience capacity constraints. We recommend customers upgrade to M30+ if they are continuing to experience issues.

We've implemented a code mitigation and are testing the change before deploying to production

We've seen capacity improve in germanywestcentral and have applied mitigations for eastus2. We're still actively working on the a fleet-wide mitigation and expect to deploy today

We are still implementing an overall fleet-wide mitigation. In the meantime, we are working with our support team to apply case-by-case mitigations to unblock customers. These interim solutions may restore service but are not permanent fixes and may have some operational constraints.

The next update will happen at 12pm UTC

We've engaged with the Azure support team to assist with the capacity constrained regions.

We are experiencing elevated capacity errors on Azure regions eastus, eastus2, germanywestcentral, westus2 and more. Azure cluster instance tier modifications and cluster creation may experiencing delays due to this issue. We are working on a mitigation to help alleviate the situation