Resolved after 5 days 2 hours, affecting germanywestcentral and eastus2 and 1 more, on May 28, 2026.
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
Update timeline
- investigating May 28, 2026, 06:26 PM 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.
- identified May 29, 2026, 09:12 PM 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.
- resolved Jun 02, 2026, 09:19 PM 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.
Your product runs on more than ClickHouse
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services