ClickHouse incident
An issue with unidling ClickHouse instances in Azure regions
Resolved after 1 hour 42 minutes, affecting germanywestcentral and eastus2 and 1 more, on February 27, 2026.
Azure eastus2 is fully operational again (all services stuck in waking started).
Affected components
Update timeline
- identified Feb 27, 2026, 08:07 AM UTC
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.
- monitoring Feb 27, 2026, 09:26 AM UTC
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.
- monitoring Feb 27, 2026, 09:27 AM UTC
Azure region westus3 is fully operational again. All services previously stuck in waking up have started.
- monitoring Feb 27, 2026, 09:46 AM UTC
Azure eastus2 is fully operational again (all services stuck in waking started).
- resolved Feb 27, 2026, 09:49 AM UTC
All services stuck in waking in all azure regions are started now.
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