ClickHouse incident

New service provisioning may fail in Azure

Minor Resolved View vendor source →

ClickHouse experienced a minor incident on June 2, 2026 affecting germanywestcentral and eastus2 and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 02, 2026, 09:19 PM UTC
Resolved
Jun 02, 2026, 09:19 PM UTC
Duration
—
Detected by Pingoru
Jun 02, 2026, 09:19 PM UTC

Affected components

germanywestcentraleastus2westus3

Update timeline

  1. investigating May 28, 2026, 06:26 PM UTC

    Status: Investigating Due to extremely slow response time for some API calls to Azure infrastructure, new service provisioning may timeout before Cloud Control Plane or OpenAPI request gets response. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Degraded performance)

  2. identified May 29, 2026, 09:12 PM UTC

    Status: Identified Azure confirmed the issue is related to an ongoing backend DNS zone migration. The issue is transient but we are working with Azure team to find a resolution to this issue. Affected components westus3 (Degraded performance) eastus2 (Degraded performance) germanywestcentral (Degraded performance)

  3. resolved Jun 02, 2026, 09:19 PM UTC

    Status: Resolved Service provisioning is working, but some users may intermittently see an error message stating: “This service name is already in use.” This error is transient. If you encounter it, please refresh the page -your service should still be provisioning and will become visible shortly. We are working with Microsoft Azure to fully resolve the underlying issue. Affected components eastus2 (Operational) germanywestcentral (Operational) westus3 (Operational)