ClickHouse incident
We are investigating an issue in Azure eastus2 region, impacting replicas in one specific Availability Zone
ClickHouse experienced a minor incident on August 2, 2026 affecting eastus2, lasting 4h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 02, 2026, 02:44 PM UTC
Status: Investigating We are aware about service degradation in Azure eastus2 region, impacting only one Availability Zone. New service provisioning time might be delayed. Customers may see increased latency. Affected components eastus2 (Degraded performance)
- identified Aug 02, 2026, 03:42 PM UTC
Status: Identified We are applying a change, unblocking the pending replicas. We already see sign of improvements for services that have the change applied. Affected components eastus2 (Degraded performance)
- identified Aug 02, 2026, 04:16 PM UTC
Status: Identified We still see problematic compute nodes provided by CSP, so remediation may take more time. We working closely with Azure support. Affected components eastus2 (Degraded performance)
- investigating Aug 02, 2026, 05:02 PM UTC
Status: Investigating We are still working closely with CSP support to figure out the path forward. The Azure support confirmed there is an issue with some components provided by CSP, investigation ongoing. Affected components eastus2 (Degraded performance)
- monitoring Aug 02, 2026, 07:05 PM UTC
Status: Monitoring The issue seems to be resolved on the Azure side. We are monitoring before we resolve the issue. Affected components eastus2 (Degraded performance)
- resolved Aug 02, 2026, 07:34 PM UTC
Status: Resolved The issue is now resolved. All services are back to normal. Affected components eastus2 (Operational)