New service provisioning may fail in Azure
May 28, 18:26 UTCJun 2, 21:19 UTC
Duration
5d 2h
Impact
Minor
Root cause
Not disclosed
ClickHouse, 90 days
18 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Jun 2, 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.
- Identified · May 29, 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.
- Investigating · May 28, 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.
More from ClickHouse
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2408:42 UTC | Streaming ClickPipes degradation in AWS eu-central-1 region | minor | 29m |
| Sep 2408:31 UTC | Some ClickPipes CDC pipes paused and can't be resumed | minor | 33m |
| Sep 2315:28 UTC | We are investigating an issue affecting Azure eastus2 region | minor | 30m |
| Sep 2213:19 UTC | We are investigating an issue with CH servers in Azure germanywestcentral region | minor | 5h 6m |
| Sep 1610:16 UTC | Intermittent Issues with the Support tab | minor | 13h 50m |
| Sep 1518:57 UTC | ClickPipes failing on Kinesis in AWS us-east-1 | critical | 29h 46m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.