An issue with unidling ClickHouse instances in Azure regions

Update timeline

1. identified Feb 27, 2026, 08:07 AM UTC

   Status: Identified We have spotted an issue where idled ClickHouse instances in Azure regions can't be woken up. Team is already working on a fix. We expect the fix to be rolled out soon. Affected components westus3 (Degraded performance) eastus2 (Degraded performance) germanywestcentral (Degraded performance)

2. monitoring Feb 27, 2026, 09:26 AM UTC

   Status: Monitoring A fix is deployed. Services waking up now (from idle or starting from stopped) will start as normal. Services that are currently stuck in waking will come up soon. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Degraded performance)

3. monitoring Feb 27, 2026, 09:27 AM UTC

   Status: Monitoring Azure region westus3 is fully operational again. All services previously stuck in waking up have started. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Operational)

4. monitoring Feb 27, 2026, 09:46 AM UTC

   Status: Monitoring Azure eastus2 is fully operational again (all services stuck in waking started). Affected components westus3 (Operational) eastus2 (Operational) germanywestcentral (Degraded performance)

5. resolved Feb 27, 2026, 09:49 AM UTC

   Status: Resolved All services stuck in waking in all azure regions are started now. Affected components eastus2 (Operational) germanywestcentral (Operational) westus3 (Operational)