Minor impactResolvedDatabases

ClickHouse Cloud incident: New service provisioning may fail in Azure

ClickHouse Cloud reported this minor-impact incident on its official status page on May 28, 2026, 18:26 UTC. It was resolved after 5d 2h.

Right now ClickHouse Cloud is operational. Live ClickHouse Cloud status →

🔔 Get alerted when ClickHouse Cloud has issuesFree · email alerts · no credit card
May 28, 2026, 18:26 UTC
started
Jun 2, 2026, 21:19 UTC
resolved
5d 2h
duration
Minor
impact
  1. resolvedJun 2, 2026, 21:19 UTC

    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.

  2. identifiedMay 29, 2026, 21:12 UTC

    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.

  3. investigatingMay 28, 2026, 18:26 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in ClickHouse Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does ClickHouse Cloud have incidents?

ClickHouse Cloud reported 16 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 2h 28m. See ClickHouse Cloud's uptime and incident history

ClickHouse Cloud incident on May 28, 2026: New service provisioning may fail in Azure · APIStatus.watch