ClickHouse Outage History

ClickHouse is up right now

There were 12 ClickHouse outages since February 3, 2026 totaling 1356h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.clickhouse.com

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-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-1
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-1
Timeline · 5 updates
  1. investigating Apr 08, 2026, 04:09 PM UTC

    Status: Investigating We spotted an issue where creation of new ClickHouse instances is delayed or stuck. Team is investigating the issue and already applying a temporary remediation. Affected components ap-southeast-1 (Degraded performance) ap-southeast-2 (Degraded performance) us-east-2 (Degraded performance) us-west-2 (Degraded performance) ap-northeast-2 (Degraded performance) il-central-1 (Degraded performance) ap-south-1 (Degraded performance) eu-west-2 (Degraded performance) us-east-1 (Degraded performance) eu-central-1 (Degraded performance) eu-west-1 (Degraded performance) ap-northeast-1 (Degraded performance)

  2. identified Apr 08, 2026, 04:21 PM UTC

    Status: Identified We identified the issue and applying the remediation. The issue was caused by manual operation performed on the AWS Route53 configuration earlier today. It caused increase in the rate of requests to Route53 API, leading to throttling and retries (including provisioning of new ClickHouse instances). Affected components ap-northeast-1 (Degraded performance) us-west-2 (Degraded performance) ap-south-1 (Degraded performance) eu-west-2 (Degraded performance) ap-northeast-2 (Degraded performance) il-central-1 (Degraded performance) us-east-1 (Degraded performance) ap-southeast-1 (Degraded performance) eu-central-1 (Degraded performance) ap-southeast-2 (Degraded performance) eu-west-1 (Degraded performance) us-east-2 (Degraded performance)

  3. monitoring Apr 08, 2026, 04:49 PM UTC

    Status: Monitoring We applied the fix for a subset of regions and see signs of improvements. We are gradually applying the fix to all other regions and monitoring the status. Affected components us-west-2 (Degraded performance) eu-west-2 (Degraded performance) us-east-1 (Degraded performance) ap-southeast-1 (Degraded performance) ap-southeast-2 (Degraded performance) us-east-2 (Degraded performance) ap-northeast-2 (Degraded performance) il-central-1 (Degraded performance) ap-south-1 (Degraded performance) eu-central-1 (Degraded performance) eu-west-1 (Degraded performance) ap-northeast-1 (Degraded performance)

  4. monitoring Apr 08, 2026, 07:20 PM UTC

    Status: Monitoring ClickHouse continues to scale external-dns in each region. The following regions are complete and operating normally: us-east-1, af-south-1, ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1 Additional regions are in progress or will begin shortly, and the ETA to complete the remaining regions is estimated as 3-5 hours: us-east-2, us-west-2, eu-central-1, eu-west-1, eu-west-2, ap-southeast-1, ap-southeast-2, il-central-1 Affected components ap-south-1 (Operational) eu-west-2 (Degraded performance) eu-central-1 (Degraded performance) ap-southeast-2 (Degraded performance) eu-west-1 (Degraded performance) us-east-2 (Degraded performance) ap-northeast-2 (Operational) il-central-1 (Degraded performance) us-east-1 (Operational) ap-southeast-1 (Degraded performance) ap-northeast-1 (Operational) us-west-2 (Degraded performance)

  5. resolved Apr 08, 2026, 10:24 PM UTC

    Status: Resolved This issue is resolved. External-DNS has been scaled for all impacted regions. Affected components us-east-1 (Operational) ap-northeast-2 (Operational) il-central-1 (Operational) eu-west-2 (Operational) ap-southeast-1 (Operational) eu-central-1 (Operational) ap-southeast-2 (Operational) eu-west-1 (Operational) us-east-2 (Operational) ap-northeast-1 (Operational) us-west-2 (Operational) ap-south-1 (Operational)

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-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 February 12, 2026

Partial outage in ClickPipes services (CDC ClickPipes)

Detected by Pingoru
Feb 12, 2026, 06:16 PM UTC
Resolved
Feb 12, 2026, 06:16 PM UTC
Duration
—
Affected: ClickPipes - ap-northeast-2ClickPipes - us-east-2ClickPipes - ap-southeast-2ClickPipes - eu-central-1ClickPipes - us-east-1ClickPipes - ap-south-1
Timeline · 7 updates
  1. investigating Feb 12, 2026, 04:37 PM UTC

    Status: Investigating There is an ongoing incident affecting CDC ClickPipes in us-east-1. The team is investigating. Affected components ClickPipes - us-east-1 (Partial outage)

  2. investigating Feb 12, 2026, 05:02 PM UTC

    Status: Investigating The incident is affecting all regions for CDC ClickPipes only. The team continues to investigate. Affected components ClickPipes - ap-south-1 (Partial outage) ClickPipes - ap-northeast-2 (Partial outage) ClickPipes - eu-central-1 (Partial outage) ClickPipes - us-east-2 (Partial outage) ClickPipes - us-east-1 (Partial outage) ClickPipes - ap-southeast-2 (Partial outage)

  3. identified Feb 12, 2026, 05:18 PM UTC

    Status: Identified We have identified the issue and are working on a fix. Affected components ClickPipes - eu-central-1 (Partial outage) ClickPipes - us-east-2 (Partial outage) ClickPipes - us-east-1 (Partial outage) ClickPipes - ap-southeast-2 (Partial outage) ClickPipes - ap-south-1 (Partial outage) ClickPipes - ap-northeast-2 (Partial outage)

  4. identified Feb 12, 2026, 05:34 PM UTC

    Status: Identified We are rolling out the fix region per region. ap-southeast-2 is now fully operational. Affected components ClickPipes - eu-central-1 (Partial outage) ClickPipes - us-east-2 (Partial outage) ClickPipes - us-east-1 (Partial outage) ClickPipes - ap-southeast-2 (Operational) ClickPipes - ap-south-1 (Partial outage) ClickPipes - ap-northeast-2 (Partial outage)

  5. identified Feb 12, 2026, 05:42 PM UTC

    Status: Identified We have fixed the issue and rolled it out across all regions. In the next few minutes, you should see CDC ClickPipes recover and catch up on the replication backlog. Affected components ClickPipes - ap-southeast-2 (Operational) ClickPipes - ap-south-1 (Operational) ClickPipes - ap-northeast-2 (Operational) ClickPipes - eu-central-1 (Operational) ClickPipes - us-east-2 (Operational) ClickPipes - us-east-1 (Operational)

  6. monitoring Feb 12, 2026, 05:43 PM UTC

    Status: Monitoring We continue monitoring the recovery of ClickPipes across all regions, after rolling out the fix to all affected CDC ClickPipes. Affected components ClickPipes - us-east-1 (Operational) ClickPipes - ap-southeast-2 (Operational) ClickPipes - ap-south-1 (Operational) ClickPipes - ap-northeast-2 (Operational) ClickPipes - eu-central-1 (Operational) ClickPipes - us-east-2 (Operational)

  7. resolved Feb 12, 2026, 06:16 PM UTC

    Status: Resolved After verifying that all affected ClickPipes have recovered, the incident can be declared as resolved. We will be sharing an RCA in the next few days with the affected customers. We sincerely apologize for the disruption caused. Affected components ClickPipes - eu-central-1 (Operational) ClickPipes - us-east-2 (Operational) ClickPipes - us-east-1 (Operational) ClickPipes - ap-southeast-2 (Operational) ClickPipes - ap-south-1 (Operational) ClickPipes - ap-northeast-2 (Operational)

Read the full incident report →

Minor February 3, 2026

Elevated error rate in AWS

Detected by Pingoru
Feb 03, 2026, 10:09 AM UTC
Resolved
Feb 03, 2026, 10:09 AM UTC
Duration
—
Affected: us-east-1eu-west-2ap-southeast-1eu-central-1ClickPipes - us-east-1
Timeline · 11 updates
  1. investigating Jan 31, 2026, 10:03 AM UTC

    Status: Investigating We are investigating a partial outage affecting services in the AWS region us-east-1.

  2. identified Jan 31, 2026, 10:55 AM UTC

    Status: Identified Our engineering team has identified the root cause of the service disruption affecting ClickHouse some instances in US-EAST-1. We are currently deploying a fix across the region. ClickHouse instances should begin resuming normal operations within the next 10-30 minutes. We will continue to monitor closely and provide updates as services are restored. Affected components us-east-1 (Partial outage) ClickPipes - us-east-1 (Partial outage)

  3. resolved Jan 31, 2026, 11:51 AM UTC

    Status: Resolved This issue is now fixed. Affected components us-east-1 (Operational) ClickPipes - us-east-1 (Operational)

  4. investigating Feb 01, 2026, 09:27 AM UTC

    Status: Investigating We are investigating an elevated error rate in AWS us-east-1 and eu-west-2. Affected components us-east-1 (Partial outage)

  5. resolved Feb 01, 2026, 09:45 AM UTC

    Status: Resolved All components are operational after the restart of an internal component (Cilium) in the affected regions. The team is working on an RCA. Affected components us-east-1 (Operational)

  6. investigating Feb 02, 2026, 09:35 AM UTC

    Status: Investigating We are investigating an elevated error rate in AWS eu-central-1 and ap-southeast-1. Affected components ClickPipes - us-east-1 (Operational) eu-central-1 (Partial outage) eu-west-2 (Operational) us-east-1 (Operational) ap-southeast-1 (Partial outage)

  7. monitoring Feb 02, 2026, 10:23 AM UTC

    Status: Monitoring The team mitigated the issue in affected regions and continues to investigate the root cause. Affected components us-east-1 (Operational) ap-southeast-1 (Operational) ClickPipes - us-east-1 (Operational) eu-central-1 (Operational) eu-west-2 (Operational)

  8. monitoring Feb 02, 2026, 06:13 PM UTC

    Status: Monitoring Additional configuration changes have been applied to prevent the recurrence of this issue. The team continues to monitor the systems. Affected components eu-central-1 (Operational) eu-west-2 (Operational) us-east-1 (Operational) ap-southeast-1 (Operational) ClickPipes - us-east-1 (Operational)

  9. monitoring Feb 02, 2026, 10:47 PM UTC

    Status: Monitoring We believe this is related to a known bug in the version of our networking stack currently in use and are mitigating the issue by resetting this layer across all AWS regions. The team continues to monitor all systems closely. Affected components eu-west-2 (Operational) us-east-1 (Operational) ap-southeast-1 (Operational) ClickPipes - us-east-1 (Operational) eu-central-1 (Operational)

  10. monitoring Feb 03, 2026, 03:06 AM UTC

    Status: Monitoring We have completed the reset of the networking stack across all regions and continue to monitor all systems closely. Affected components eu-west-2 (Operational) us-east-1 (Operational) ap-southeast-1 (Operational) ClickPipes - us-east-1 (Operational) eu-central-1 (Operational)

  11. resolved Feb 03, 2026, 10:09 AM UTC

    Status: Resolved We have confirmed that all systems are stable and operating normally. The networking configuration has been fully restored across all regions, and we have implemented additional monitoring and safeguards to prevent recurrence. We will continue to monitor systems closely over the coming days as part of our standard post-incident procedures, and share an RCA as soon as possible. Affected components us-east-1 (Operational) ap-southeast-1 (Operational) ClickPipes - us-east-1 (Operational) eu-central-1 (Operational) eu-west-2 (Operational)

Read the full incident report →

Looking to track ClickHouse downtime and outages?

Pingoru polls ClickHouse's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when ClickHouse reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track ClickHouse alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring ClickHouse for free

5 free monitors · No credit card required