ClickHouse Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. identified 2026-10-20 07:39 UTC

   Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google support to restore normal behavior and will provide an update as soon as we have more information.

2. identified 2026-10-20 09:52 UTC

   This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj...

3. identified 2026-10-20 10:04 UTC

   This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj...

4. identified 2026-10-20 13:00 UTC

   The zone is recovering. Clickpipes is fully restored but we continue to monitor until google reports all issues have been resolved.

5. monitoring 2026-10-20 13:03 UTC

   We do not see any current impact on clickpipes or ClickHouse services, with full service restored. Google has not marked the incident as resolved, so we continue to monitor.

6. resolved 2026-10-20 14:23 UTC

   The issue has been resolved. All services are fully operational.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 01:55 UTC

   We have identified an issue that prevents customers from creating new support cases and viewing existing cases in the ClickHouse Cloud console. Affected users may see an error when loading the support page or submitting a case. ClickHouse Cloud services, queries, and data are...

2. resolved 2026-10-12 02:26 UTC

   The issue preventing customers from creating and viewing support cases in the ClickHouse Cloud console has been resolved. Support case functionality is working normally again. If you couldn’t open a case during the affected window, please submit it again from the console.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-24 08:42 UTC

   We detected an issue with network configuration in eu-central-1 region which causes failures for streaming Clickpipes in this region. Team is working on remediation

2. monitoring 2026-09-24 09:03 UTC

   Remediation was applied and we see signs of improvement

3. resolved 2026-09-24 09:11 UTC

   Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-24 08:31 UTC

   We are aware about an issue where CDC ClickPipes were paused and can't be operated via API. ClickHouse team is investigating the issue. The issue affects subset of customers.

2. investigating 2026-09-24 08:35 UTC

   The issue happened during planned maintenance. ClickHouse team is applying a remediation to resume paused pipes.

3. monitoring 2026-09-24 08:46 UTC

   We are seeing signs of improvements in most regions and pipes are resumed.

4. monitoring 2026-09-24 09:01 UTC

   All regions recovered except us-east-1 region. It is also progressing and expected to be remediated soon.

5. resolved 2026-09-24 09:05 UTC

   All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-23 15:28 UTC

   **Investigating delays to provisioning and autoscaling** We are investigating an issue affecting our Kubernetes infrastructure in Azure eastus2 region. Some customers may experience delays with provisioning and autoscaling of ClickHouse clusters. We are working closely with...

2. monitoring 2026-09-23 15:36 UTC

   We have identified the cause of the disruption and already applying the remediation. We will monitor for recovery and send update as soon as it is fully recovered.

3. resolved 2026-09-23 15:59 UTC

   The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-22 13:19 UTC

   We detected an issue with CHC clusters in some Azure regions. ClickHouse cloud team is investigating. Some operations might be degraded.

2. investigating 2026-09-22 13:21 UTC

   Only germanywestcentral Azure region is affected.

3. investigating 2026-09-22 13:31 UTC

   Only one Availability zone is affected in germanywestcentral Azure region. The problem affects internal component (ClickHouse Keepers). Some ClickHouse Services in this region may see increased latency on inserts or DDL queries.

4. investigating 2026-09-22 13:49 UTC

   The problem is caused by Azure outage in the germanywestcentral region. ClickHouse Cloud team is working with Azure support. Impact: • New ClickHouse services can't be provisioned (appear as stuck in UI). • Some services may experience higher latency due to reduced capacity.

5. identified 2026-09-22 14:57 UTC

   The Azure team is working on resolution of the issue. The ClickHouse Cloud team will relay any updates related to ClickHouse clusters operation. An excerpt from Azure incident status: > As per our investigation, we believe this stemmed from multiple underlying storage systems...

6. monitoring 2026-09-22 15:26 UTC

   The issue is still present on Azure infrastructure side and ClickHouse Cloud team is actively monitoring for any impact for existing ClickHouse Clusters. Correction on earlier impact description: Provisioning of new instances is expected to work. Operations like autoscaling of...

7. monitoring 2026-09-22 17:02 UTC

   Azure support shared they are working on fixing the underlying issue, we started seeing some recovery but the incident is not completely resolved yet. We are working with Azure to get this fixed as soon as possible.

8. resolved 2026-09-22 18:25 UTC

   The underlying AZ has recovered and we are fully back online. Since ClickHouse cloud architecture uses 3 AZs we were operational during this outage but there might have been some degradations. Azure support shared the details of the issue as following- Between 12:04 UTC and...

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-16 10:16 UTC

   We are investigating an issue with Salesforce that is affecting our Support tab. Some users may experience errors when accessing or managing support requests. Retrying the action usually resolves the issue. Our team is working to restore normal service, and we will provide an...

2. identified 2026-09-16 14:24 UTC

   We have confirmed that the impact to our Support tab is related to this [Salesforce incident](https://status.salesforce.com/incidents/20004433 "Salesforce incident"). Salesforce is rolling out a fix, and we are seeing strong signs of recovery. We have observed no further errors...

3. monitoring 2026-09-16 16:15 UTC

   We are currently in monitoring phase. No errors have been observed in 2 hours and are awaiting confirmation from Salesforce before fully resolving the incident.

4. resolved 2026-09-17 00:05 UTC

   Salesforce has confirmed the incident is resolved on their end.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-15 18:57 UTC

   Currently investigating failures on AWS us-east-1 for customers using ClickPipes on Kinesis in this region.

2. identified 2026-09-15 20:03 UTC

   The issue has been identified as a change on AWS related to Kinesis IAM permissions and appears to be currently isolated to us-east-1. While we work with AWS to mitigate this issue, we recommend to update your IAM policy to include a trailing wildcard (`/*`) to the resource for...

3. identified 2026-09-15 22:45 UTC

   AWS has confirmed the issue on their end and are in the process of rolling back the change. The ETA for this rollback in us-east-1 is by end of day tomorrow. Signs of gradual recovery are expected in us-east-1 as the rollback progresses across AZs during this time. In the...

4. identified 2026-09-16 03:17 UTC

   AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a...

5. identified 2026-09-16 15:21 UTC

   AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a...

6. resolved 2026-09-17 00:43 UTC

   This incident has been resolved. AWS has confirmed that the Enhanced Fanhout (EFO) Kinesis pipes in us-east-1 region are fully operational. Please contact ClickHouse Support if you experience any further issues:

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-14 20:36 UTC

   ClickHouse is investigating degraded Distributed Cache performance affecting multiple ClickHouse Cloud customers. Distributed Cache is a feature currently in Private Preview. We will provide further updates as they become available.

2. identified 2026-09-14 21:28 UTC

   ClickHouse has identified the cause and proceeding with remedying impacted services.

3. monitoring 2026-09-14 22:41 UTC

   Impacted services have been updated and are now fully operational. ClickHouse is monitoring.

4. resolved 2026-09-15 00:35 UTC

   This incident has been resolved. Distributed Cache performance in the region is back to normal. Please contact ClickHouse Support if any services in the Distributed Cache Private Preview are experiencing any remaining issues:

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 16:11 UTC

   Due to networking issues in GCP us-central1 zone b (see ), ClickHouse Cloud services can be degraded as well. Symptoms can be temporarily unavailable metrics and monitoring dashboards. Creation of new services and ClickPipes pipelines can be temporarily unavailable as well....

2. investigating 2026-09-01 16:19 UTC

   After careful investigation we could not determine any impact of the [GCP service degradation](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev) (in zone b) on ClickHouse Cloud functionality.

3. resolved 2026-09-01 16:30 UTC

   All systems operational. GCP incident has no impact on ClickHouse Cloud.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-23 10:14 UTC

   It may take longer time to provision a new service.

2. resolved 2026-08-23 10:47 UTC

   Issue was resolved. Services are provisioning successfully.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. identified 2026-08-17 15:23 UTC

   We identified an issue where new CDC ClickPipes can't be provisioned due to dependency on GitHub availability ([https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx")). Team...

2. monitoring 2026-08-17 16:35 UTC

   We are seeing signs of recovery. The team is closely monitoring and will report any updates. In case if any pipe gets stuck provisioning, our team can assist with manual operation to make it happen.

3. resolved 2026-08-17 17:17 UTC

   This issue has been resolved. New CDC pipes for Postgres are provisioning normally.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-08-14 19:25 UTC

   We noticed a network issue between 18:10–18:37 UTC affecting a small subset of services on AWS in the us-east-1 region. During that period, you may have experienced connection timeouts to your services. The issue has been resolved, and our team continues to monitor the situation.

2. resolved 2026-08-14 19:47 UTC

   This issue has been resolved. Connectivity has returned to normal.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-02 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.

2. identified 2026-08-02 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.

3. identified 2026-08-02 16:16 UTC

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

4. investigating 2026-08-02 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.

5. monitoring 2026-08-02 19:05 UTC

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

6. resolved 2026-08-02 19:34 UTC

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

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 13:07 UTC

   Monitoring and billing is degraded in eu-west-1. Specifically: Monitoring dashboards will not contain the latest data Metric-based notification will not be sent Missing metrics in prometheus endpoints Billing metering is not currently updating Autoscaling recommendations are not...

2. resolved 2026-07-24 16:33 UTC

   Issue is now resolved. Currently backfilling metrics for dashboards.

3. investigating 2026-07-24 17:13 UTC

   We are investigating an issue impacting customer services in ap-southeast-1. Some services may experience degraded availability.

4. monitoring 2026-07-24 20:55 UTC

   The issue with monitoring and billing in ap-southeast-1 is resolved. We are now backfilling the missing data.

5. resolved 2026-07-24 21:28 UTC

   Backfill of data for ap-southeast-1 is complete.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 11:53 UTC

   As part of our weekly upgrade process, CDC ClickPipes in `eu-central-1` became stuck in maintenance state. The team is working on a mitigation.

2. identified 2026-07-22 12:36 UTC

   Services in `eu-central-1` have recovered. We're in the process of manually recovering ~20 services in other regions.

3. identified 2026-07-22 13:05 UTC

   Most services have fully recovered. Continuing to roll out the fix to remaining 4 services (all in `eu-central-1`, `us-east-2`).

4. monitoring 2026-07-22 13:39 UTC

   All services have recovered; we will continue monitoring the affected nodes and consolidating our findings. Please reach out to our support team to request access to the RCA, when available.

5. resolved 2026-07-22 14:36 UTC

   The CDC ClickPipes upgrade rollout remains on hold while we confirm we can safely proceed without triggering the underlying pod networking failure mode that triggered the incident.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-15 23:33 UTC

   We are seeing degraded performance in AWS eu-central-1 starting around 4 pm PT.

2. resolved 2026-07-16 01:59 UTC

   AWS has mitigated the disruption affecting the eu-central-1 availability zone. We will continue monitoring to ensure stability.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 19:30 UTC

   The backend services are not impacted but the cloud console UI is down.

2. resolved 2026-07-08 19:36 UTC

   The Cloud Console is back up.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-07-06 12:34 UTC

   We have identified an issue with provisioning of new instances and autoscaling operations in AWS us-east-1 region. Connection latencies for CH servers can be also affected due to slow provisioning of compute nodes. ClickHouse Cloud is working with AWS support team to fix the...

2. identified 2026-07-06 13:09 UTC

   The issue is caused by AWS outage, please see [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

3. resolved 2026-07-06 15:03 UTC

   The incident was resolved and we don't see any impact in us-east-1 region anymore. For details, please refer to the AWS Health status page: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-01 12:04 UTC

   ClickHouse Cloud team is investigating an issue with creating new ClickPipes in GCP. Provisioning of new pipes might be delayed or stuck.

2. identified 2026-07-01 12:17 UTC

   We identified the cause of the issue and the team have applied a fix

3. resolved 2026-07-01 12:24 UTC

   The fix was applied and we see the issue is not reproducing anymore.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-03 14:48 UTC

   The customer-facing Prometheus metrics endpoint missing all per-server metrics and is only returning Cloud-infra metrics

2. resolved 2026-06-05 21:02 UTC

   -

3. resolved 2026-06-05 21:03 UTC

   The customer-facing Prometheus metrics endpoint missing all per-server metrics and is only returning Cloud-infra metrics

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-01 11:45 UTC

   Connectivity to services is affected.

2. investigating 2026-06-01 11:59 UTC

   Impact is on eu-west-1 region. Incident name had a typo in the beginning.

3. identified 2026-06-01 12:42 UTC

   The root cause of issue is identified

4. monitoring 2026-06-01 13:53 UTC

   The root cause was identified and issue was fixed. Connectivity issues should not happen again.

5. resolved 2026-06-01 16:53 UTC

   Issue is resolved.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-28 18:26 UTC

   Due to extremely slow response time for some API calls to Azure infrastructure, new service provisioning may timeout before Cloud Control Plane or OpenAPI request gets response.

2. identified 2026-05-29 21:12 UTC

   Azure confirmed the issue is related to an ongoing backend DNS zone migration. The issue is transient but we are working with Azure team to find a resolution to this issue.

3. resolved 2026-06-02 21:19 UTC

   Service provisioning is working, but some users may intermittently see an error message stating: _“This service name is already in use.”_ This error is transient. If you encounter it, please refresh the page -your service should still be provisioning and will become visible...

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-27 17:48 UTC

   Issues logging into ClickHouse Agents reported

2. monitoring 2026-05-27 18:03 UTC

   Mitigation rolled out, monitoring.

3. resolved 2026-05-27 19:11 UTC

   Some users may have been unable to log in to ClickHouse Agents due to an overly broad login rate limit. A configuration change was rolled out, access has been confirmed restored, and no customer data or ClickHouse services were impacted.

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-22 16:11 UTC

   We've noticed some instances are stuck in provisioning state due to capacity issues in AWS us-east-1 region. ClickHouse Cloud team is working on possible remediations, but we advise do not create new instances in this region until capacity problem is addressed on AWS side.

2. resolved 2026-05-22 16:50 UTC

   Affected instances have been corrected in the AWS us-east-1 region. We apologize for the disruption this issue caused. We are committed to the reliability of all ClickHouse Cloud services and appreciate your understanding as we continue to improve our systems and operations. If...

Excerpts are shortened. Read the full incident on ClickHouse Cloud's status page.