Is ClickHouse down?

Last checked 8m ago
Current status
ClickHouse is up

No incidents right now.

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

ClickHouse is operational right now. Last checked 8m ago; the most recent incident resolved 13d ago.

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 11 incidents in the last 90 days (99.31% 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: Snowflake Supabase Stitch Data Iron.io Aiven SolarWinds Observability Neo4j Aura Upstash Pinecone PlanetScale View all 6,000+ providers
ClickHouse uptime 99.31% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  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)

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

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

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

  5. Resolved
    Started Aug 02, 2026, 07:34 PM UTC · Resolved Aug 02, 2026, 07:34 PM UTC
    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)

    Latest: Status: Resolved The issue is now resolved. All services are back to normal. Affected components eastus2 (Operational)

See the full ClickHouse outage history

6 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 · 11 incidents View full outage history →