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

1. resolvedAug 2, 2026, 19:34 UTC

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

2. monitoringAug 2, 2026, 19:05 UTC

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

3. investigatingAug 2, 2026, 17:02 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.

4. identifiedAug 2, 2026, 16:16 UTC

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

5. identifiedAug 2, 2026, 15:42 UTC

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

6. investigatingAug 2, 2026, 14:44 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in ClickHouse Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Plaid: Service Disruption Impacting Bank of America connectionsMajor · Aug 2, 2026, 14:51 UTC
• Supabase: Management API Performance DegradationMinor · Jul 31, 2026, 18:36 UTC

How often does ClickHouse Cloud have incidents?

ClickHouse Cloud reported 16 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 2h 28m. See ClickHouse Cloud's uptime and incident history