ClickHouse Outage History

ClickHouse is up right now

ClickHouse had 35 outages in the last 2 years totaling 17h 56m of downtime — averaging 1.4 incidents per month.

There were 35 ClickHouse outages since September 17, 2025 totaling 17h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.clickhouse.com

Minor June 5, 2026

Prometheus metrics endpoint missing per-server metri

Detected by Pingoru
Jun 05, 2026, 09:03 PM UTC
Resolved
Jun 05, 2026, 09:03 PM UTC
Duration
—
Affected: asia-southeast1us-central1europe-west4asia-northeast1germanywestcentraleastus2westus3ClickPipes - ap-northeast-2ClickPipes - eu-west-1ClickPipes - us-east-2SQLConsoleAuthorizationus-east1ClickHouse Cloud APIil-central-1ClickPipes - ap-southeast-2ClickPipes - eu-central-1ClickPipes - us-east-1ClickPipes - ap-south-1ClickPipes - 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 →

Minor June 2, 2026

New service provisioning may fail in Azure

Detected by Pingoru
Jun 02, 2026, 09:19 PM UTC
Resolved
Jun 02, 2026, 09:19 PM UTC
Duration
—
Affected: germanywestcentraleastus2westus3
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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 →

Minor June 1, 2026

Connectivity issues in AWS eu-west-1 region

Detected by Pingoru
Jun 01, 2026, 04:53 PM UTC
Resolved
Jun 01, 2026, 04:53 PM UTC
Duration
—
Affected: eu-west-1
Timeline · 5 updates
  1. investigating Jun 01, 2026, 11:45 AM UTC

    Status: Investigating Connectivity to services is affected. Affected components eu-west-1 (Degraded performance)

  2. 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)

  3. identified Jun 01, 2026, 12:42 PM UTC

    Status: Identified The root cause of issue is identified Affected components eu-west-1 (Degraded performance)

  4. 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)

  5. resolved Jun 01, 2026, 04:53 PM UTC

    Status: Resolved Issue is resolved. Affected components eu-west-1 (Operational)

Read the full incident report →

Minor May 27, 2026

ClickHouse Agents Login Issues

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
  1. investigating May 27, 2026, 05:48 PM UTC

    Status: Investigating Issues logging into ClickHouse Agents reported Affected components ClickHouse Agents (Degraded performance)

  2. monitoring May 27, 2026, 06:03 PM UTC

    Status: Monitoring Mitigation rolled out, monitoring. Affected components ClickHouse Agents (Operational)

  3. 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 →

Minor May 22, 2026

Capacity issues in AWS us-east-1 region affecting provisioning times

Detected by Pingoru
May 22, 2026, 04:50 PM UTC
Resolved
May 22, 2026, 04:50 PM UTC
Duration
—
Affected: us-east-1
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor May 20, 2026

GCP us-east1 capacity constraints impacting cluster operations

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
  1. 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)

  2. 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 →

Minor May 9, 2026

Increased Error Rate and Latency on AWS Region (US-EAST-1)

Detected by Pingoru
May 09, 2026, 09:48 AM UTC
Resolved
May 09, 2026, 09:48 AM UTC
Duration
—
Affected: us-east-1us-east-1
Timeline · 2 updates
  1. investigating May 08, 2026, 02:46 AM UTC

    Status: Investigating AWS Region (US-EAST-1) is experiencing disruptions. We are actively monitoring the situation and following updates from AWS. Please follow the https://health.aws.amazon.com/health/status page for latest updates. Affected components us-east-1 (Partial outage)

  2. resolved May 09, 2026, 09:48 AM UTC

    Status: Resolved AWS has mitigated the disruption affecting the US-EAST-1 availability zone. We will continue monitoring to ensure stability. Affected components us-east-1 (Operational)

Read the full incident report →

Minor May 5, 2026

Azure new services impacted

Detected by Pingoru
May 05, 2026, 03:14 PM UTC
Resolved
May 05, 2026, 03:14 PM UTC
Duration
—
Affected: westus3
Timeline · 2 updates
  1. investigating May 05, 2026, 01:03 PM UTC

    Status: Investigating We are currently experiencing issues provisioning new services in Azure. Existing services are not impacted. Affected components westus3 (Degraded performance)

  2. resolved May 05, 2026, 03:14 PM UTC

    Status: Resolved We have resolved the issue and are no longer seeing impact to services Affected components westus3 (Operational)

Read the full incident report →

Minor April 30, 2026

Degraded connectivity affecting us-east-2

Detected by Pingoru
Apr 30, 2026, 02:12 AM UTC
Resolved
Apr 30, 2026, 02:12 AM UTC
Duration
—
Affected: us-east-2us-east-2
Timeline · 6 updates
  1. investigating Apr 28, 2026, 06:44 PM UTC

    Status: Investigating We are currently investigating connection issues affecting some customers, resulting in connection timeouts when connecting to ClickHouse. The issue has been isolated to infrastructure in the us-east-2 region. We have received multiple high-severity reports and are treating this with priority. Our engineering team is actively working to mitigate the issue and restore normal connectivity. We will provide further updates as more information becomes available. Affected components us-east-2 (Degraded performance)

  2. monitoring Apr 28, 2026, 07:18 PM UTC

    Status: Monitoring The connection issues affecting some customers in the us-east-2 region have been mitigated, and services are currently operating normally. We are continuing to monitor the situation closely to ensure stability and prevent recurrence. We will provide further updates if there are any changes. Affected components us-east-2 (Operational)

  3. resolved Apr 28, 2026, 07:41 PM UTC

    Status: Resolved The connection issues affecting some customers in the us-east-2 region have been resolved, and services are operating normally. Affected components us-east-2 (Operational)

  4. investigating Apr 28, 2026, 08:34 PM UTC

    Status: Investigating We are seeing a recurrence of the connection issues affecting some customers in the us-east-2 region, resulting in connection timeouts. Our team is actively investigating and working to mitigate the issue as a priority. We will provide further updates as more information becomes available. Affected components us-east-2 (Degraded performance)

  5. monitoring Apr 28, 2026, 10:32 PM UTC

    Status: Monitoring A subset of services in us-east-2 experienced intermittent connection timeouts earlier today caused by exhaustion of network resources on one of our regional load balancers. We have applied mitigations to restore connectivity and the service is currently operating normally. We are continuing to work with on rolling out additional capacity and safeguards to prevent recurrence. Customers who continue to see connection issues should reach out to support. Affected components us-east-2 (Degraded performance)

  6. resolved Apr 30, 2026, 02:12 AM UTC

    Status: Resolved We have resolved the incident. Affected components us-east-2 (Operational)

Read the full incident report →

Minor April 20, 2026

Capacity constraints for new workloads on GCP us-east1

Detected by Pingoru
Apr 20, 2026, 10:18 PM UTC
Resolved
Apr 20, 2026, 10:18 PM UTC
Duration
—
Affected: us-east1
Timeline · 3 updates
  1. identified Apr 19, 2026, 01:39 PM UTC

    Status: Identified We are experiencing capacity constraints for new workloads on GCP us-east1. Currently running and created instances are not affected. Affected components us-east1 (Degraded performance)

  2. identified Apr 19, 2026, 02:29 PM UTC

    Status: Identified Capacity constraints of GCP us-east1 region do not allow to allocate more instances in the region. We are working with a cloud provider to resolve capacity issues. Running services are working without issues, but new instance creation is disabled. Affected components us-east1 (Degraded performance)

  3. resolved Apr 20, 2026, 10:18 PM UTC

    Status: Resolved Incident has been resolved Affected components us-east1 (Operational)

Read the full incident report →

Minor April 18, 2026

Degraded provisioning times and slower scaling opreations in GCP us-central1 region

Detected by Pingoru
Apr 18, 2026, 11:13 AM UTC
Resolved
Apr 18, 2026, 11:13 AM UTC
Duration
—
Affected: us-central1
Timeline · 3 updates
  1. identified Apr 17, 2026, 03:12 PM UTC

    Status: Identified New instances have increased provisioning times due to IP addresses pool exhaustion. Remediation is being applied. Affected components us-central1 (Degraded performance)

  2. monitoring Apr 17, 2026, 04:27 PM UTC

    Status: Monitoring Issue is mitigated. Services provisioning and scaling is working as expected. Affected components us-central1 (Degraded performance)

  3. resolved Apr 18, 2026, 11:13 AM UTC

    Status: Resolved We can confirm the issue is fully resolved. The ClickHouse team is taking additional measures to prevent similar failure modes in future. Affected components us-central1 (Operational)

Read the full incident report →

Minor April 16, 2026

Unable to edit service scaling settings and delete services

Detected by Pingoru
Apr 16, 2026, 11:55 PM UTC
Resolved
Apr 16, 2026, 11:55 PM UTC
Duration
—
Affected: asia-southeast1ap-south-1us-east-1ap-southeast-2ap-northeast-1eu-west-2us-central1europe-west4asia-northeast1germanywestcentraleastus2westus3us-east1ap-southeast-1ap-northeast-2il-central-1us-east-2us-west-2eu-central-1eu-west-1ap-northeast-1ap-northeast-2ap-south-1ap-southeast-1ap-southeast-2eu-central-1eu-west-1eu-west-2us-east-1us-east-2us-west-2
Timeline · 3 updates
  1. identified Apr 16, 2026, 10:11 PM UTC

    Status: Identified Impacting services on ClickHouse Cloud across multiple regions. Affected components asia-southeast1 (Degraded performance) ap-south-1 (Degraded performance) us-east-1 (Degraded performance) ap-southeast-1 (Degraded performance) eu-central-1 (Degraded performance) europe-west4 (Degraded performance) us-east-2 (Degraded performance) ap-northeast-1 (Degraded performance) eu-west-2 (Degraded performance) ap-southeast-2 (Degraded performance) westus3 (Degraded performance) us-west-2 (Degraded performance) us-central1 (Degraded performance) ap-northeast-2 (Degraded performance) asia-northeast1 (Degraded performance) us-east1 (Degraded performance) eu-west-1 (Degraded performance) il-central-1 (Degraded performance) eastus2 (Degraded performance) germanywestcentral (Degraded performance)

  2. monitoring Apr 16, 2026, 11:55 PM UTC

    Status: Monitoring Fix is rolled out on all regions Affected components eu-west-2 (Degraded performance) us-east-1 (Degraded performance) europe-west4 (Operational) westus3 (Operational) us-east-2 (Degraded performance) ap-northeast-1 (Degraded performance) asia-southeast1 (Operational) eu-west-1 (Degraded performance) asia-northeast1 (Operational) il-central-1 (Degraded performance) eu-central-1 (Degraded performance) us-central1 (Operational) ap-northeast-2 (Degraded performance) eastus2 (Operational) us-east1 (Operational) ap-southeast-1 (Degraded performance) germanywestcentral (Operational) ap-southeast-2 (Degraded performance) us-west-2 (Degraded performance) ap-south-1 (Degraded performance)

  3. resolved Apr 16, 2026, 11:55 PM UTC

    Status: Resolved Fix has been applied on all regions. Affected components il-central-1 (Operational) ap-southeast-1 (Operational) eu-central-1 (Operational) ap-southeast-2 (Operational) europe-west4 (Operational) eastus2 (Operational) ap-south-1 (Operational) us-east1 (Operational) germanywestcentral (Operational) eu-west-1 (Operational) asia-northeast1 (Operational) westus3 (Operational) us-east-2 (Operational) ap-northeast-1 (Operational) us-west-2 (Operational) asia-southeast1 (Operational) eu-west-2 (Operational) us-east-1 (Operational) us-central1 (Operational) ap-northeast-2 (Operational)

Read the full incident report →

Minor April 8, 2026

Creation of new instances in AWS is delayed or stuck

Detected by Pingoru
Apr 08, 2026, 10:24 PM UTC
Resolved
Apr 08, 2026, 10:24 PM UTC
Duration
—
Affected: ap-south-1us-east-1ap-southeast-2ap-northeast-1eu-west-2ap-southeast-1ap-northeast-2il-central-1us-east-2us-west-2eu-central-1eu-west-1ap-northeast-1ap-northeast-2ap-south-1ap-southeast-1ap-southeast-2eu-central-1eu-west-1eu-west-2us-east-1us-east-2us-west-2
Timeline · 5 updates

Read the full incident report →

Minor March 16, 2026

ClickStack UI is not loading

Detected by Pingoru
Mar 16, 2026, 12:59 PM UTC
Resolved
Mar 16, 2026, 12:59 PM UTC
Duration
—
Affected: SQLConsole
Timeline · 2 updates
  1. investigating Mar 16, 2026, 11:28 AM UTC

    Status: Investigating The ClickStack UI (https://hyperdx.clickhouse.cloud/) is currently not loading. We are investigating. Affected components SQLConsole (Degraded performance)

  2. resolved Mar 16, 2026, 12:59 PM UTC

    Status: Resolved The incident was caused by an overloaded database. The instance was scaled up. It is stable again now. We are investigating heavy queries and will apply improvements. Affected components SQLConsole (Operational)

Read the full incident report →

Minor March 3, 2026

Resolved – Operational Impact in ClickPipes

Detected by Pingoru
Mar 03, 2026, 11:00 AM UTC
Resolved
Mar 03, 2026, 11:00 AM UTC
Duration
—
Affected: ClickPipes - us-east-2ClickPipes - us-east-1
Timeline · 4 updates
  1. investigating Mar 03, 2026, 08:39 AM UTC

    Status: Investigating We are currently experiencing degraded operational performance in ClickPlane. Data ingestion is functioning as expected, however some operational features may experience increased latency or intermittent behavior. Our team is actively investigating the issue and working on mitigation. We will provide further updates as soon as more information becomes available. Affected components ClickPipes - us-east-2 (Degraded performance) ClickPipes - us-east-1 (Degraded performance)

  2. identified Mar 03, 2026, 10:04 AM UTC

    Status: Identified We have mitigated the impact affecting ClickPlane in the us-east-1 region. Operational performance in this region has stabilized, and ingestion continues to function normally. We are continuing to monitor the system closely to ensure stability and working to fix the problem on us-east-2 Affected components ClickPipes - us-east-2 (Degraded performance) ClickPipes - us-east-1 (Operational)

  3. identified Mar 03, 2026, 10:20 AM UTC

    Status: Identified We have mitigated the operational impact affecting ClickPipes in the us-east-1 region. Operational performance in this region has stabilized, and ingestion continues to function normally. We are continuing to monitor the system closely to ensure stability. Further updates will be provided if necessary. Affected components ClickPipes - us-east-2 (Degraded performance) ClickPipes - us-east-1 (Operational)

  4. resolved Mar 03, 2026, 11:00 AM UTC

    Status: Resolved The operational impact affecting ClickPipes in the us-east-1 region has been fully resolved. All systems are operating normally, including ingestion and operational functionality. We will continue to monitor the platform to ensure ongoing stability. Thank you for your patience. Affected components ClickPipes - us-east-1 (Operational) ClickPipes - us-east-2 (Operational)

Read the full incident report →

Minor February 27, 2026

An issue with unidling ClickHouse instances in Azure regions

Detected by Pingoru
Feb 27, 2026, 09:49 AM UTC
Resolved
Feb 27, 2026, 09:49 AM UTC
Duration
—
Affected: germanywestcentraleastus2westus3
Timeline · 5 updates
  1. identified Feb 27, 2026, 08:07 AM UTC

    Status: Identified We have spotted an issue where idled ClickHouse instances in Azure regions can't be woken up. Team is already working on a fix. We expect the fix to be rolled out soon. Affected components westus3 (Degraded performance) eastus2 (Degraded performance) germanywestcentral (Degraded performance)

  2. monitoring Feb 27, 2026, 09:26 AM UTC

    Status: Monitoring A fix is deployed. Services waking up now (from idle or starting from stopped) will start as normal. Services that are currently stuck in waking will come up soon. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Degraded performance)

  3. monitoring Feb 27, 2026, 09:27 AM UTC

    Status: Monitoring Azure region westus3 is fully operational again. All services previously stuck in waking up have started. Affected components eastus2 (Degraded performance) germanywestcentral (Degraded performance) westus3 (Operational)

  4. monitoring Feb 27, 2026, 09:46 AM UTC

    Status: Monitoring Azure eastus2 is fully operational again (all services stuck in waking started). Affected components westus3 (Operational) eastus2 (Operational) germanywestcentral (Degraded performance)

  5. resolved Feb 27, 2026, 09:49 AM UTC

    Status: Resolved All services stuck in waking in all azure regions are started now. Affected components eastus2 (Operational) germanywestcentral (Operational) westus3 (Operational)

Read the full incident report →

Minor February 21, 2026

Newly created instances in AWS us-east-1 are stuck provisioning or have wrong configuration

Detected by Pingoru
Feb 21, 2026, 02:26 PM UTC
Resolved
Feb 21, 2026, 02:26 PM UTC
Duration
—
Affected: us-east-1us-east-1
Timeline · 5 updates
  1. investigating Feb 21, 2026, 11:50 AM UTC

    Status: Investigating We are investigating the issue where instances created in AWS us-east-1 have wrong configuration, causing provisioning to stuck or to have wrong number of replicas. This affects only a small number of instances created in last ~25 hours Affected components us-east-1 (Degraded performance)

  2. identified Feb 21, 2026, 12:01 PM UTC

    Status: Identified We have identified the possible cause of the issue and applying remediation for stuck/misconfigured instances. We do not recommend creating new instances in us-east-1 until the incident is resolved. Affected components us-east-1 (Degraded performance)

  3. identified Feb 21, 2026, 12:29 PM UTC

    Status: Identified We have fixed the root cause of the issue. Newly created instances have correct configuration now and are expected to provision successfully. Instances that currently are stuck or have wrong configuration are being corrected by the ClickHouse team. We are closely monitoring creation of new instances and remediation for existing stuck instances. Affected components us-east-1 (Degraded performance)

  4. monitoring Feb 21, 2026, 02:17 PM UTC

    Status: Monitoring Configuration for all affected instances was corrected. We are monitoring the health status of these instances. Affected components us-east-1 (Operational)

  5. resolved Feb 21, 2026, 02:26 PM UTC

    Status: Resolved All systems operational. 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 →

Minor January 30, 2026

AWS ap-south-1 degraded operations

Detected by Pingoru
Jan 30, 2026, 01:27 PM UTC
Resolved
Jan 30, 2026, 01:27 PM UTC
Duration
—
Affected: ap-south-1
Timeline · 5 updates
  1. investigating Jan 30, 2026, 11:55 AM UTC

    Status: Investigating We are investigating issue in AWS ap-south-1 region where: - Admin operations on instances might be delayed or not progressing - Billing metrics not updated - Some dashboards in Control Plane UI not loading or loading slowly Affected components ap-south-1 (Partial outage)

  2. identified Jan 30, 2026, 12:08 PM UTC

    Status: Identified The team has identified the issue and working on the fix. ClickHouse instances are expected to be reachable and working (except autoscaling functionality). Affected components ap-south-1 (Degraded performance)

  3. monitoring Jan 30, 2026, 12:56 PM UTC

    Status: Monitoring We are seeing signs of recovery, and closely monitoring. Affected components ap-south-1 (Degraded performance)

  4. monitoring Jan 30, 2026, 01:16 PM UTC

    Status: Monitoring User dashboards and autoscaling operations should be recovering now. Old data is already available, last hours are being backfilled. Affected components ap-south-1 (Degraded performance)

  5. resolved Jan 30, 2026, 01:27 PM UTC

    Status: Resolved The issue is fully resolved. The latest data in ControlPlane UI monitoring dashboards was backfilled and should be available. The issue seems to be related to networking issues on underlying VMs. Team is investigating the root cause to make sure it won't happen again or in other regions. Affected components ap-south-1 (Operational)

Read the full incident report →