ClickHouse incident

We are investigating an issue in Azure eastus2 region, impacting replicas in one specific Availability Zone

Resolved after 4 hours 49 minutes, affecting eastus2, on August 2, 2026.

monitoring Aug 02, 2026, 07:05 PM UTC

The issue seems to be resolved on the Azure side. We are monitoring before we resolve the issue.

Started
Aug 02, 2026, 02:44 PM UTC
Resolved
Aug 02, 2026, 07:34 PM UTC
Duration
4h 49m
Detected by Pingoru
Aug 02, 2026, 02:44 PM UTC

Affected components

eastus2

Update timeline

  1. investigating Aug 02, 2026, 02:44 PM UTC

    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.

  2. identified Aug 02, 2026, 03:42 PM UTC

    We are applying a change, unblocking the pending replicas. We already see sign of improvements for services that have the change applied.

  3. identified Aug 02, 2026, 04:16 PM UTC

    We still see problematic compute nodes provided by CSP, so remediation may take more time. We working closely with Azure support.

  4. investigating Aug 02, 2026, 05:02 PM UTC

    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.

  5. monitoring Aug 02, 2026, 07:05 PM UTC

    The issue seems to be resolved on the Azure side. We are monitoring before we resolve the issue.

  6. resolved Aug 02, 2026, 07:34 PM UTC

    The issue is now resolved. All services are back to normal.

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.

Add your stack →