Kurrent Cloud incident

Azure Provisioning Errors

Minor Resolved View vendor source →

Kurrent Cloud experienced a minor incident on January 24, 2026 affecting Provisioning Azure, lasting 173d 23h. The incident has been resolved; the full update timeline is below.

Started
Jan 24, 2026, 05:18 PM UTC
Resolved
Jul 17, 2026, 05:17 PM UTC
Duration
173d 23h
Detected by Pingoru
Jan 24, 2026, 05:18 PM UTC

Affected components

Provisioning Azure

Update timeline

  1. monitoring Jan 24, 2026, 05:18 PM UTC

    Customers may experience provisioning errors when creating clusters in some Azure regions due to limited Azure compute capacity. Affected regions include, but are not limited to, East US, East US 2, and West US. Azure has not provided an ETA for resolution. Workaround: Attempt provisioning in an alternate Azure region. If a public access cluster is an option, consider deploying to a nearby AWS or GCP region.

  2. monitoring Mar 03, 2026, 03:53 PM UTC

    We have implemented changes to the provisioning system that are improving successful cluster creation. We have additional measures that we are working on and hope to have deployed within the next couple of weeks.

  3. monitoring Jul 17, 2026, 05:17 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 17, 2026, 05:17 PM UTC

    This incident has been resolved.