What is ClickHouse's uptime?

Over the last 90 days, ClickHouse reported 99.26% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.clickhouse.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see ClickHouse's uptime history rolling forward in real time.

Has ClickHouse had outages in 2026?

Yes — ClickHouse has had 12 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last ClickHouse outage?

The most recent ClickHouse incident was "Distributed Cache performance degradation in AWS us-east-1", which started on September 15, 2026 and was resolved on September 15, 2026. Pingoru captured this directly from https://status.clickhouse.com. See the full incident card above for affected components and the update timeline.

How often does ClickHouse have outages?

Based on the last 90 days, ClickHouse averages 4.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is ClickHouse's status page?

ClickHouse's official status page is https://status.clickhouse.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is ClickHouse down right now?

ClickHouse is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment ClickHouse reports a change. Current status is based on 84 tracked services.

How does Pingoru know if ClickHouse is down?

We read https://status.clickhouse.com directly, using ClickHouse's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when ClickHouse has an outage?

Create a free Pingoru account and add ClickHouse as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

ClickHouse's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real ClickHouse incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real ClickHouse issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official ClickHouse status?

We use ClickHouse's own status page at https://status.clickhouse.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Partial Outage" mean?

ClickHouse has a partial outage — one or more components are down, but the rest of the service is operational.

Is ClickHouse down?

Last checked 1m ago

Current status

ClickHouse is having a partial outage

2 active incidents: Intermittent Issues with the Support tab, ClickPipes failing on Kinesis in AWS us-east-1

Get alerts when ClickHouse breaks → View ClickHouse outage history →

Free · no credit card

Official status page: https://status.clickhouse.com · Polled every 5 minutes · 84 components tracked

ClickHouse is reporting a partial outage right now (last checked 1m ago). Some components are affected; others remain operational.

Real-time ClickHouse status, recent outages, and incident history — pulled directly from ClickHouse's official status page at https://status.clickhouse.com every 5 minutes. Pingoru tracks 84 ClickHouse services and has captured 14 incidents in the last 90 days (99.26% uptime). Get email, Slack, Discord, or webhook alerts the moment ClickHouse reports a new incident — free for 5 monitors, no credit card.

Users who monitor ClickHouse also follow these Database services:

SolarWinds Observability

Neo4j Aura

Upstash

Pinecone

PlanetScale View all 6,000+ providers

ClickHouse uptime 99.26% uptime · past 90 days

Mon Wed Fri

JunJulAugSep

Less More

Active incidents 2

Intermittent Issues with the Support tab

Ongoing ● 34m

Started Sep 16, 2026, 10:16 AM UTC

ClickHouse Cloud API
Timeline · 1 update
- 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)
Latest: 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.…
ClickPipes failing on Kinesis in AWS us-east-1

Ongoing ● 7h 32m

Started Sep 16, 2026, 03:17 AM UTC

AWS us-east-1
Timeline · 4 updates
- investigating · Sep 15, 2026, 06:57 PM UTC
  
  Status: Investigating Currently investigating failures on AWS us-east-1 for customers using ClickPipes on Kinesis in this region. Affected components AWS us-east-1 (Full outage)
- identified · Sep 15, 2026, 08:03 PM UTC
  
  Status: Identified 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 the kinesis:RegisterStreamConsumer action like so: { "Effect": "Allow", "Action": [ "kinesis:RegisterStreamConsumer" ], "Resource": [ "arn:aws:kinesis:{REGION}:{ACCOUNT_ID}:stream/{STREAM_NAME}/*" ] } Once this is applied, you must restart your ClickPipe for the changes to take affect. Affected components AWS us-east-1 (Full outage)
- identified · Sep 15, 2026, 10:45 PM UTC
  
  Status: Identified 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 meantime, if your ClickPipe is still affected, please update your IAM policy as instructed in the previous status update. Affected components AWS us-east-1 (Full outage)
- identified · Sep 16, 2026, 03:17 AM UTC
  
  Status: Identified 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 recent change that introduced a defect in how RegisterStreamConsumer requests are authorized, causing each request to be evaluated against the specific consumer resource (for example, arn:aws:kinesis:::stream//consumer/) rather than the stream resource (for example, arn:aws:kinesis:::stream/). As a result, IAM policies that granted kinesis:RegisterStreamConsumer only at the stream level, which previously succeeded and aligns with our published documentation, no longer matched the request and returned AccessDeniedException. AWS has begun rolling back this change in the affected Region, and expect calls that were previously permitted at the stream level to succeed again once the rollback completes on September 16, 2026, by 6:00 PM PDT. As a workaround, please update your IAM policy as instructed in the previous status update. Affected components AWS us-east-1 (Full outage)
Latest: Status: Identified AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStr…

Recent outages & incidents

Past 90 days

Distributed Cache performance degradation in AWS us-east-1

Resolved —

Started Sep 15, 2026, 12:35 AM UTC · Resolved Sep 15, 2026, 12:35 AM UTC

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)
Latest: 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 Distribute…
Service degradation in GCP us-central-1

Resolved —

Started Sep 01, 2026, 04:30 PM UTC · Resolved Sep 01, 2026, 04:30 PM UTC

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)
Latest: Status: Resolved All systems operational. GCP incident has no impact on ClickHouse Cloud. Affected components us-central1 (Operational)
Slow provisioning times of services in GCP europe-west4 region

Resolved —

Started Aug 23, 2026, 10:47 AM UTC · Resolved Aug 23, 2026, 10:47 AM UTC

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)
Latest: Status: Resolved Issue was resolved. Services are provisioning successfully. Affected components europe-west4 (Operational)
Provisioning of new CDC pipes for Postgres might be delayed or failing

Resolved —

Started Aug 17, 2026, 05:17 PM UTC · Resolved Aug 17, 2026, 05:17 PM UTC

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-1
Timeline · 3 updates
- identified · Aug 17, 2026, 03:23 PM UTC
  
  Status: Identified We identified an issue where new CDC ClickPipes can't be provisioned due to dependency on GitHub availability (https://www.githubstatus.com/incidents/zkxwbgr0cnmx). Team is monitoring the issue and tries to find a possible workaround. Affected components AWS eu-central-1 (Degraded performance) AWS ca-central-1 (Degraded performance) AWS il-central-1 (Degraded performance) GCP asia-northeast1 (Degraded performance) AWS ap-southeast-2 (Degraded performance) AWS us-west-2 (Degraded performance) AWS ap-northeast-1 (Degraded performance) AWS eu-north-1 (Degraded performance) AWS us-east-1 (Degraded performance) AWS ap-south-1 (Degraded performance) GCP us-west1 (Degraded performance) AWS ap-southeast-3 (Degraded performance) AWS us-east-2 (Degraded performance) AWS ap-east-1 (Degraded performance) GCP northamerica-northeast1 (Degraded performance) AWS ap-east-2 (Degraded performance) AWS eu-west-1 (Degraded performance) AWS mx-central-1 (Degraded performance) GCP us-central1 (Degraded performance) AWS ap-southeast-1 (Degraded performance) AWS ap-southeast-5 (Degraded performance) GCP europe-west4 (Degraded performance) GCP australia-southeast1 (Degraded performance) GCP europe-west3 (Degraded performance) GCP europe-west6 (Degraded performance) GCP europe-west2 (Degraded performance) AWS ap-northeast-2 (Degraded performance) AWS af-south-1 (Degraded performance) AWS eu-west-2 (Degraded performance) AWS sa-east-1 (Degraded performance) GCP asia-southeast1 (Degraded performance)
- monitoring · Aug 17, 2026, 04:35 PM UTC
  
  Status: Monitoring 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. Affected components GCP asia-southeast1 (Degraded performance) GCP asia-northeast1 (Degraded performance) GCP europe-west3 (Degraded performance) GCP europe-west6 (Degraded performance) AWS ap-northeast-2 (Degraded performance) AWS ap-northeast-1 (Degraded performance) GCP australia-southeast1 (Degraded performance) AWS us-east-1 (Degraded performance) AWS us-west-2 (Degraded performance) AWS eu-west-1 (Degraded performance) AWS eu-north-1 (Degraded performance) AWS ap-south-1 (Degraded performance) AWS ap-southeast-1 (Degraded performance) GCP us-west1 (Degraded performance) AWS ap-east-2 (Degraded performance) AWS eu-central-1 (Degraded performance) AWS us-east-2 (Degraded performance) AWS ap-southeast-3 (Degraded performance) AWS ca-central-1 (Degraded performance) AWS eu-west-2 (Degraded performance) GCP europe-west4 (Degraded performance) GCP northamerica-northeast1 (Degraded performance) AWS ap-southeast-2 (Degraded performance) AWS il-central-1 (Degraded performance) AWS mx-central-1 (Degraded performance) AWS ap-east-1 (Degraded performance) GCP us-central1 (Degraded performance) GCP europe-west2 (Degraded performance) AWS ap-southeast-5 (Degraded performance) AWS af-south-1 (Degraded performance) AWS sa-east-1 (Degraded performance)
- resolved · Aug 17, 2026, 05:17 PM UTC
  
  Status: Resolved This issue has been resolved. New CDC pipes for Postgres are provisioning normally. Affected components GCP asia-northeast1 (Operational) AWS il-central-1 (Operational) AWS eu-west-1 (Operational) AWS af-south-1 (Operational) AWS ap-east-1 (Operational) GCP europe-west2 (Operational) AWS eu-central-1 (Operational) AWS us-east-1 (Operational) AWS ap-south-1 (Operational) AWS sa-east-1 (Operational) GCP northamerica-northeast1 (Operational) AWS ap-east-2 (Operational) AWS us-west-2 (Operational) AWS ca-central-1 (Operational) GCP asia-southeast1 (Operational) GCP us-west1 (Operational) GCP australia-southeast1 (Operational) AWS ap-southeast-5 (Operational) AWS eu-west-2 (Operational) GCP us-central1 (Operational) AWS us-east-2 (Operational) AWS ap-southeast-2 (Operational) AWS ap-southeast-3 (Operational) GCP europe-west6 (Operational) GCP europe-west3 (Operational) AWS ap-southeast-1 (Operational) AWS ap-northeast-2 (Operational) AWS ap-northeast-1 (Operational) AWS eu-north-1 (Operational) AWS mx-central-1 (Operational) GCP europe-west4 (Operational)
Latest: Status: Resolved This issue has been resolved. New CDC pipes for Postgres are provisioning normally. Affected components GCP asia-northeast1 (Operational) AWS il-central-1 (Operati…
Network connectivity issue in AWS us-east-1

Resolved —

Started Aug 14, 2026, 07:47 PM UTC · Resolved Aug 14, 2026, 07:47 PM UTC
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.
Latest: Status: Resolved This issue has been resolved. Connectivity has returned to normal.

See the full ClickHouse outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse ClickHouse outage history →

Or sign up free to get alerts when ClickHouse breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →

Intermittent Issues with the Support tab Ongoing

Started Sep 16, 2026, 10:16 AM UTC · ● 34m
ClickPipes failing on Kinesis in AWS us-east-1 Ongoing

Started Sep 16, 2026, 03:17 AM UTC · ● 7h 32m
Distributed Cache performance degradation in AWS us-east-1 Resolved

Started Sep 15, 2026, 12:35 AM UTC · Resolved Sep 15, 2026, 12:35 AM UTC · —
Service degradation in GCP us-central-1 Resolved

Started Sep 01, 2026, 04:30 PM UTC · Resolved Sep 01, 2026, 04:30 PM UTC · —
Slow provisioning times of services in GCP europe-west4 region Resolved

Started Aug 23, 2026, 10:47 AM UTC · Resolved Aug 23, 2026, 10:47 AM UTC · —
Provisioning of new CDC pipes for Postgres might be delayed or failing Resolved

Started Aug 17, 2026, 05:17 PM UTC · Resolved Aug 17, 2026, 05:17 PM UTC · —
Network connectivity issue in AWS us-east-1 Resolved

Started Aug 14, 2026, 07:47 PM UTC · Resolved Aug 14, 2026, 07:47 PM UTC · —
We are investigating an issue in Azure eastus2 region, impacting replicas in one specific Availability Zone Resolved

Started Aug 02, 2026, 07:34 PM UTC · Resolved Aug 02, 2026, 07:34 PM UTC · —