- Detected by Pingoru
- Sep 24, 2026, 09:11 AM UTC
- Resolved
- Sep 24, 2026, 09:11 AM UTC
- Duration
- —
Affected: AWS eu-central-1
Timeline · 3 updates
-
investigating Sep 24, 2026, 08:42 AM UTC
Status: Investigating 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 Affected components AWS eu-central-1 (Degraded performance)
-
monitoring Sep 24, 2026, 09:03 AM UTC
Status: Monitoring Remediation was applied and we see signs of improvement Affected components AWS eu-central-1 (Degraded performance)
-
resolved Sep 24, 2026, 09:11 AM UTC
Status: Resolved Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause. Affected components AWS eu-central-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2026, 09:05 AM UTC
- Resolved
- Sep 24, 2026, 09:05 AM UTC
- Duration
- —
Affected: AWS ap-northeast-2AWS eu-west-1AWS us-east-2AWS ap-southeast-2AWS eu-central-1AWS us-east-1AWS ap-south-1AWS us-west-2AWS eu-north-1AWS ca-central-1AWS af-south-1AWS ap-east-1AWS ap-northeast-1AWS ap-southeast-1AWS ap-southeast-3AWS eu-west-2AWS il-central-1AWS mx-central-1AWS sa-east-1GCP asia-northeast1GCP asia-southeast1GCP europe-west2GCP europe-west4GCP us-central1GCP us-west1GCP australia-southeast1GCP europe-west3GCP europe-west6GCP northamerica-northeast1AWS ap-southeast-5AWS ap-east-2
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 03:59 PM UTC
- Resolved
- Sep 23, 2026, 03:59 PM UTC
- Duration
- —
Affected: eastus2
Timeline · 3 updates
-
investigating Sep 23, 2026, 03:28 PM UTC
Status: Investigating 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 Azure support to restore normal behavior. We’ll provide another update within 30 minutes, or sooner if we have more information. Affected components eastus2 (Degraded performance)
-
monitoring Sep 23, 2026, 03:36 PM UTC
Status: Monitoring 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. Affected components eastus2 (Degraded performance)
-
resolved Sep 23, 2026, 03:59 PM UTC
Status: Resolved The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future. Affected components eastus2 (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2026, 06:25 PM UTC
- Resolved
- Sep 22, 2026, 06:25 PM UTC
- Duration
- —
Affected: germanywestcentraleastus2westus3
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2026, 12:43 AM UTC
- Resolved
- Sep 17, 2026, 12:43 AM UTC
- Duration
- —
Affected: AWS us-east-1
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2026, 12:05 AM UTC
- Resolved
- Sep 17, 2026, 12:05 AM UTC
- Duration
- —
Affected: ClickHouse Cloud API
Timeline · 4 updates
-
investigating Sep 16, 2026, 10:16 AM UTC
Status: Investigating 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 update as soon as more information becomes available. Thank you for your patience. Affected components ClickHouse Cloud API (Degraded performance)
-
identified Sep 16, 2026, 02:24 PM UTC
Status: Identified We have confirmed that the impact to our Support tab is related to this Salesforce incident "Salesforce incident": https://status.salesforce.com/incidents/20004433. Salesforce is rolling out a fix, and we are seeing strong signs of recovery. We have observed no further errors for nearly an hour and will continue monitoring the situation closely. We will provide another update when the incident is resolved or if any new information becomes available. Affected components ClickHouse Cloud API (Degraded performance)
-
monitoring Sep 16, 2026, 04:15 PM UTC
Status: Monitoring 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. Affected components ClickHouse Cloud API (Degraded performance)
-
resolved Sep 17, 2026, 12:05 AM UTC
Status: Resolved Salesforce has confirmed the incident is resolved on their end. Affected components ClickHouse Cloud API (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 12:35 AM UTC
- Resolved
- Sep 15, 2026, 12:35 AM UTC
- Duration
- —
Affected: us-east-1
Timeline · 4 updates
-
investigating Sep 14, 2026, 08:36 PM UTC
Status: Investigating 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. Affected components us-east-1 (Degraded performance)
-
identified Sep 14, 2026, 09:28 PM UTC
Status: Identified ClickHouse has identified the cause and proceeding with remedying impacted services. Affected components us-east-1 (Degraded performance)
-
monitoring Sep 14, 2026, 10:41 PM UTC
Status: Monitoring Impacted services have been updated and are now fully operational. ClickHouse is monitoring. Affected components us-east-1 (Operational)
-
resolved Sep 15, 2026, 12:35 AM UTC
Status: Resolved 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: https://console.clickhouse.cloud/support Affected components us-east-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 04:30 PM UTC
- Resolved
- Sep 01, 2026, 04:30 PM UTC
- Duration
- —
Affected: us-central1
Timeline · 3 updates
-
investigating Sep 01, 2026, 04:11 PM UTC
Status: Investigating Due to networking issues in GCP us-central1 zone b (see https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev), 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. Existing ClickHouse Services are not affected and are operating normally. Affected components us-central1 (Degraded performance)
-
investigating Sep 01, 2026, 04:19 PM UTC
Status: Investigating 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. Affected components us-central1 (Operational)
-
resolved Sep 01, 2026, 04:30 PM UTC
Status: Resolved All systems operational. GCP incident has no impact on ClickHouse Cloud. Affected components us-central1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 23, 2026, 10:47 AM UTC
- Resolved
- Aug 23, 2026, 10:47 AM UTC
- Duration
- —
Affected: europe-west4
Timeline · 2 updates
-
investigating Aug 23, 2026, 10:14 AM UTC
Status: Investigating It may take longer time to provision a new service. Affected components europe-west4 (Degraded performance)
-
resolved Aug 23, 2026, 10:47 AM UTC
Status: Resolved Issue was resolved. Services are provisioning successfully. Affected components europe-west4 (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 05:17 PM UTC
- Resolved
- Aug 17, 2026, 05:17 PM UTC
- Duration
- —
Affected: AWS ap-northeast-2AWS eu-west-1AWS us-east-2AWS ap-southeast-2AWS eu-central-1AWS us-east-1AWS ap-south-1AWS us-west-2AWS eu-north-1AWS ca-central-1AWS af-south-1AWS ap-east-1AWS ap-northeast-1AWS ap-southeast-1AWS ap-southeast-3AWS eu-west-2AWS il-central-1AWS mx-central-1AWS sa-east-1GCP asia-northeast1GCP asia-southeast1GCP europe-west2GCP europe-west4GCP us-central1GCP us-west1GCP australia-southeast1GCP europe-west3GCP europe-west6GCP northamerica-northeast1AWS ap-southeast-5AWS ap-east-2
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 07:47 PM UTC
- Resolved
- Aug 14, 2026, 07:47 PM UTC
- Duration
- —
Timeline · 2 updates
-
monitoring Aug 14, 2026, 07:25 PM UTC
Status: Monitoring 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.
-
resolved Aug 14, 2026, 07:47 PM UTC
Status: Resolved This issue has been resolved. Connectivity has returned to normal.
Read the full incident report →
- Detected by Pingoru
- Aug 02, 2026, 07:34 PM UTC
- Resolved
- Aug 02, 2026, 07:34 PM UTC
- Duration
- —
Affected: eastus2
Timeline · 6 updates
-
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)
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 09:28 PM UTC
- Resolved
- Jul 24, 2026, 09:28 PM UTC
- Duration
- —
Affected: ap-southeast-1eu-west-1
Timeline · 5 updates
-
investigating Jul 24, 2026, 01:07 PM UTC
Status: Investigating 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 being applied Affected components eu-west-1 (Degraded performance)
-
resolved Jul 24, 2026, 04:33 PM UTC
Status: Resolved Issue is now resolved. Currently backfilling metrics for dashboards. Affected components eu-west-1 (Operational)
-
investigating Jul 24, 2026, 05:13 PM UTC
Status: Investigating We are investigating an issue impacting customer services in ap-southeast-1. Some services may experience degraded availability. Affected components ap-southeast-1 (Partial outage) eu-west-1 (Operational)
-
monitoring Jul 24, 2026, 08:55 PM UTC
Status: Monitoring The issue with monitoring and billing in ap-southeast-1 is resolved. We are now backfilling the missing data. Affected components ap-southeast-1 (Degraded performance) eu-west-1 (Operational)
-
resolved Jul 24, 2026, 09:28 PM UTC
Status: Resolved Backfill of data for ap-southeast-1 is complete. Affected components ap-southeast-1 (Operational) eu-west-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 02:36 PM UTC
- Resolved
- Jul 22, 2026, 02:36 PM UTC
- Duration
- —
Affected: AWS ap-northeast-2AWS eu-west-1AWS us-east-2AWS ap-southeast-2AWS eu-central-1AWS ca-central-1AWS il-central-1
Timeline · 5 updates
-
investigating Jul 22, 2026, 11:53 AM UTC
Status: Investigating 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. Affected components AWS eu-central-1 (Partial outage)
-
identified Jul 22, 2026, 12:36 PM UTC
Status: Identified Services in eu-central-1 have recovered. We're in the process of manually recovering ~20 services in other regions. Affected components AWS us-east-2 (Partial outage) AWS ap-southeast-2 (Partial outage) AWS ap-northeast-2 (Partial outage) AWS eu-west-1 (Partial outage) AWS ca-central-1 (Partial outage) AWS il-central-1 (Partial outage) AWS eu-central-1 (Operational)
-
identified Jul 22, 2026, 01:05 PM UTC
Status: Identified Most services have fully recovered. Continuing to roll out the fix to remaining 4 services (all in eu-central-1, us-east-2). Affected components AWS us-east-2 (Partial outage) AWS ap-southeast-2 (Operational) AWS ap-northeast-2 (Operational) AWS eu-west-1 (Operational) AWS ca-central-1 (Operational) AWS il-central-1 (Operational) AWS eu-central-1 (Partial outage)
-
monitoring Jul 22, 2026, 01:39 PM UTC
Status: Monitoring 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. Affected components AWS il-central-1 (Operational) AWS eu-central-1 (Operational) AWS us-east-2 (Operational) AWS ap-southeast-2 (Operational) AWS ap-northeast-2 (Operational) AWS eu-west-1 (Operational) AWS ca-central-1 (Operational)
-
resolved Jul 22, 2026, 02:36 PM UTC
Status: Resolved 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. Affected components AWS eu-central-1 (Operational) AWS us-east-2 (Operational) AWS ap-southeast-2 (Operational) AWS ap-northeast-2 (Operational) AWS eu-west-1 (Operational) AWS ca-central-1 (Operational) AWS il-central-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 01:59 AM UTC
- Resolved
- Jul 16, 2026, 01:59 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating Jul 15, 2026, 11:33 PM UTC
Status: Investigating We are seeing degraded performance in AWS eu-central-1 starting around 4 pm PT. https://health.aws.amazon.com/health/status
-
resolved Jul 16, 2026, 01:59 AM UTC
Status: Resolved AWS has mitigated the disruption affecting the eu-central-1 availability zone. We will continue monitoring to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 07:36 PM UTC
- Resolved
- Jul 08, 2026, 07:36 PM UTC
- Duration
- —
Affected: SQLConsoleAuthorizationClickHouse Cloud API
Timeline · 2 updates
-
investigating Jul 08, 2026, 07:30 PM UTC
Status: Investigating The backend services are not impacted but the cloud console UI is down. Affected components Authorization (Full outage) ClickHouse Cloud API (Full outage) SQLConsole (Full outage)
-
resolved Jul 08, 2026, 07:36 PM UTC
Status: Resolved The Cloud Console is back up. Affected components SQLConsole (Operational) Authorization (Operational) ClickHouse Cloud API (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 03:03 PM UTC
- Resolved
- Jul 06, 2026, 03:03 PM UTC
- Duration
- —
Affected: us-east-1us-east-1
Timeline · 3 updates
-
identified Jul 06, 2026, 12:34 PM UTC
Status: Identified 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 issue. Affected components us-east-1 (Degraded performance)
-
identified Jul 06, 2026, 01:09 PM UTC
Status: Identified The issue is caused by AWS outage, please see https://health.aws.amazon.com/health/status Affected components us-east-1 (Degraded performance)
-
resolved Jul 06, 2026, 03:03 PM UTC
Status: Resolved 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 Affected components us-east-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 12:24 PM UTC
- Resolved
- Jul 01, 2026, 12:24 PM UTC
- Duration
- —
Timeline · 3 updates
-
investigating Jul 01, 2026, 12:04 PM UTC
Status: Investigating ClickHouse Cloud team is investigating an issue with creating new ClickPipes in GCP. Provisioning of new pipes might be delayed or stuck.
-
identified Jul 01, 2026, 12:17 PM UTC
Status: Identified We identified the cause of the issue and the team have applied a fix
-
resolved Jul 01, 2026, 12:24 PM UTC
Status: Resolved The fix was applied and we see the issue is not reproducing anymore.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 09:03 PM UTC
- Resolved
- Jun 05, 2026, 09:03 PM UTC
- Duration
- —
Affected: asia-southeast1ap-south-1us-east-1ap-southeast-2eu-west-2us-central1europe-west4asia-northeast1germanywestcentraleastus2westus3AWS ap-northeast-2AWS eu-west-1AWS us-east-2SQLConsoleAuthorizationus-east1ap-southeast-1ClickHouse Cloud APIap-northeast-2il-central-1us-east-2us-west-2eu-central-1AWS ap-southeast-2AWS eu-central-1AWS us-east-1eu-west-1AWS ap-south-1AWS us-west-2ap-northeast-1ap-northeast-2ap-south-1ap-southeast-1ap-southeast-2eu-central-1eu-west-1eu-west-2us-east-1us-east-2us-west-2ClickHouse Agents
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:19 PM UTC
- Resolved
- Jun 02, 2026, 09:19 PM UTC
- Duration
- —
Affected: germanywestcentraleastus2westus3
Timeline · 3 updates
-
investigating May 28, 2026, 06:26 PM UTC
Status: Investigating 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. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Degraded performance)
-
identified May 29, 2026, 09:12 PM UTC
Status: Identified 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. Affected components westus3 (Degraded performance) eastus2 (Degraded performance) germanywestcentral (Degraded performance)
-
resolved Jun 02, 2026, 09:19 PM UTC
Status: Resolved 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 shortly. We are working with Microsoft Azure to fully resolve the underlying issue. Affected components eastus2 (Operational) germanywestcentral (Operational) westus3 (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 04:53 PM UTC
- Resolved
- Jun 01, 2026, 04:53 PM UTC
- Duration
- —
Affected: eu-west-1eu-west-1
Timeline · 5 updates
-
investigating Jun 01, 2026, 11:45 AM UTC
Status: Investigating Connectivity to services is affected. Affected components eu-west-1 (Degraded performance)
-
investigating Jun 01, 2026, 11:59 AM UTC
Status: Investigating Impact is on eu-west-1 region. Incident name had a typo in the beginning. Affected components eu-west-1 (Degraded performance)
-
identified Jun 01, 2026, 12:42 PM UTC
Status: Identified The root cause of issue is identified Affected components eu-west-1 (Degraded performance)
-
monitoring Jun 01, 2026, 01:53 PM UTC
Status: Monitoring The root cause was identified and issue was fixed. Connectivity issues should not happen again. Affected components eu-west-1 (Degraded performance)
-
resolved Jun 01, 2026, 04:53 PM UTC
Status: Resolved Issue is resolved. Affected components eu-west-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 07:11 PM UTC
- Resolved
- May 27, 2026, 07:11 PM UTC
- Duration
- —
Affected: ClickHouse Agents
Timeline · 3 updates
-
investigating May 27, 2026, 05:48 PM UTC
Status: Investigating Issues logging into ClickHouse Agents reported Affected components ClickHouse Agents (Degraded performance)
-
monitoring May 27, 2026, 06:03 PM UTC
Status: Monitoring Mitigation rolled out, monitoring. Affected components ClickHouse Agents (Operational)
-
resolved May 27, 2026, 07:11 PM UTC
Status: Resolved 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. Affected components ClickHouse Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 04:50 PM UTC
- Resolved
- May 22, 2026, 04:50 PM UTC
- Duration
- —
Affected: us-east-1us-east-1
Timeline · 2 updates
-
identified May 22, 2026, 04:11 PM UTC
Status: Identified 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. Affected components us-east-1 (Degraded performance)
-
resolved May 22, 2026, 04:50 PM UTC
Status: Resolved 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 you have questions or need information on a specific ClickHouse service, please contact support "contact support": https://clickhouse.cloud/support. Affected components us-east-1 (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 09:06 AM UTC
- Resolved
- May 22, 2026, 09:06 AM UTC
- Duration
- —
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 06:32 PM UTC
- Resolved
- May 20, 2026, 06:32 PM UTC
- Duration
- —
Affected: us-east1
Timeline · 2 updates
-
investigating May 18, 2026, 12:31 PM UTC
Status: Investigating We are currently experiencing capacity constraints in the affected GCP region. As a result, users may encounter issues when creating new clusters or operating existing clusters in this region. Our team is actively working on mitigation to restore normal capacity and minimize customer impact. We will continue to provide updates as more information becomes available. Affected components us-east1 (Degraded performance)
-
resolved May 20, 2026, 06:32 PM UTC
Status: Resolved No more capacity issues observed for us-east1 region. Provisioning and scaling should work as usual. Affected components us-east1 (Operational)
Read the full incident report →