Is ClickHouse down?

Last checked 3m ago
Current status
ClickHouse is up

No incidents right now.

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

Real-time ClickHouse status, recent outages, and incident history: pulled directly from ClickHouse's official status page at status.clickhouse.com every 5 minutes. Pingoru tracks 84 ClickHouse services and has captured 14 incidents in the last 90 days (98.94% uptime). Get email, Slack, Discord, or webhook alerts the moment ClickHouse reports a new incident, free for 3 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 8,000+ providers
ClickHouse uptime 98.94% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 47m
    Started Oct 23, 2026, 04:51 AM UTC · Resolved Oct 23, 2026, 07:39 AM UTC
    SQLConsoleAuthorizationClickHouse Cloud API
    Timeline · 2 updates
    • identified · Oct 23, 2026, 04:51 AM UTC

      Status: Identified "Support Ticket Creation through Cloud Console is degraded, and other Salesforce integrated functions may be impacted due to an outage reported at Salesforce status page: https://status.salesforce.com/products/Salesforce_Services. Creating support tickets through the ClickHouse Cloud Console may intermittently fail or take longer than usual. Responses to existing support tickets may also be delayed. If you have trouble submitting a support request, please email [email protected]: mailto:[email protected] or use the support chat in the Cloud Console. For reference, Salesforce service updates are available on the Salesforce status page: https://status.salesforce.com/products/Salesforce_Services. " Affected components Authorization (Degraded performance) ClickHouse Cloud API (Degraded performance) SQLConsole (Degraded performance)

    • resolved · Oct 23, 2026, 07:39 AM UTC

      Status: Resolved Salesforce team resolved the issue that prevented users from logging in. They identified an issue with a recent release that prevented login sessions from being created. Deployed a fix forward, and access is now restored. Users can log in and open their orgs again. https://status.salesforce.com/incidents/20004512 Affected components Authorization (Operational) ClickHouse Cloud API (Operational) SQLConsole (Operational)

    Latest: Status: Resolved Salesforce team resolved the issue that prevented users from logging in. They identified an issue with a recent release that prevented login sessions from being cr…

  2. Resolved 6h 44m
    Started Oct 20, 2026, 07:39 AM UTC · Resolved Oct 20, 2026, 02:23 PM UTC
    GCP europe-west2
    Timeline · 6 updates
    • identified · Oct 20, 2026, 07:39 AM UTC

      Status: Identified Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google support to restore normal behavior and will provide an update as soon as we have more information.

    • identified · Oct 20, 2026, 09:52 AM UTC

      Status: Identified This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Currently only zone B is impacted. We are migrating workloads away from this zone.

    • identified · Oct 20, 2026, 10:04 AM UTC

      Status: Identified This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Currently only zone B is impacted. Clusters in this region should be operational - accepting reads and writes, but provisioning of new services currently blocked until this zone is operational. Affected components GCP europe-west2 (Degraded performance)

    • identified · Oct 20, 2026, 01:00 PM UTC

      Status: Identified The zone is recovering. Clickpipes is fully restored but we continue to monitor until google reports all issues have been resolved. Affected components GCP europe-west2 (Operational)

    • monitoring · Oct 20, 2026, 01:03 PM UTC

      Status: Monitoring We do not see any current impact on clickpipes or ClickHouse services, with full service restored. Google has not marked the incident as resolved, so we continue to monitor. Affected components GCP europe-west2 (Operational)

    • resolved · Oct 20, 2026, 02:23 PM UTC

      Status: Resolved The issue has been resolved. All services are fully operational. Affected components GCP europe-west2 (Operational)

    Latest: Status: Resolved The issue has been resolved. All services are fully operational. Affected components GCP europe-west2 (Operational)

  3. Resolved 30m
    Started Oct 12, 2026, 01:55 AM UTC · Resolved Oct 12, 2026, 02:26 AM UTC
    Timeline · 2 updates
    • investigating · Oct 12, 2026, 01:55 AM UTC

      Status: Investigating We have identified an issue that prevents customers from creating new support cases and viewing existing cases in the ClickHouse Cloud console. Affected users may see an error when loading the support page or submitting a case. ClickHouse Cloud services, queries, and data are not affected. We are rolling out a fix now and expect it in production within the next 30–60 minutes.

    • resolved · Oct 12, 2026, 02:26 AM UTC

      Status: Resolved The issue preventing customers from creating and viewing support cases in the ClickHouse Cloud console has been resolved. Support case functionality is working normally again. If you couldn’t open a case during the affected window, please submit it again from the console.

    Latest: Status: Resolved The issue preventing customers from creating and viewing support cases in the ClickHouse Cloud console has been resolved. Support case functionality is working nor…

  4. Resolved 29m
    Started Sep 24, 2026, 08:42 AM UTC · Resolved Sep 24, 2026, 09:11 AM UTC
    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)

    Latest: 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-c…

  5. Resolved 33m
    Started Sep 24, 2026, 08:31 AM UTC · Resolved Sep 24, 2026, 09:05 AM 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 · 5 updates
    • investigating · Sep 24, 2026, 08:31 AM UTC

      Status: Investigating We are aware about an issue where CDC ClickPipes were paused and can't be operated via API. ClickHouse team is investigating the issue. The issue affects subset of customers. Affected components AWS eu-central-1 (Degraded performance) GCP europe-west2 (Degraded performance) GCP europe-west3 (Degraded performance) GCP northamerica-northeast1 (Degraded performance) AWS ap-south-1 (Degraded performance) GCP asia-southeast1 (Degraded performance) GCP australia-southeast1 (Degraded performance) AWS ap-southeast-2 (Degraded performance) AWS ca-central-1 (Degraded performance) AWS il-central-1 (Degraded performance) GCP us-west1 (Degraded performance) AWS ap-southeast-5 (Degraded performance) AWS us-west-2 (Degraded performance) AWS eu-west-1 (Degraded performance) AWS eu-north-1 (Degraded performance) AWS eu-west-2 (Degraded performance) AWS mx-central-1 (Degraded performance) GCP europe-west4 (Degraded performance) GCP europe-west6 (Degraded performance) AWS af-south-1 (Degraded performance) AWS ap-east-2 (Degraded performance) AWS us-east-1 (Degraded performance) AWS ap-northeast-2 (Degraded performance) AWS ap-southeast-1 (Degraded performance) AWS sa-east-1 (Degraded performance) AWS ap-northeast-1 (Degraded performance) AWS ap-southeast-3 (Degraded performance) GCP asia-northeast1 (Degraded performance) GCP us-central1 (Degraded performance) AWS us-east-2 (Degraded performance) AWS ap-east-1 (Degraded performance)

    • investigating · Sep 24, 2026, 08:35 AM UTC

      Status: Investigating The issue happened during planned maintenance. ClickHouse team is applying a remediation to resume paused pipes. Affected components GCP australia-southeast1 (Degraded performance) AWS ap-northeast-2 (Degraded performance) AWS eu-west-1 (Degraded performance) GCP asia-southeast1 (Degraded performance) GCP us-west1 (Degraded performance) AWS us-east-1 (Degraded performance) AWS eu-west-2 (Degraded performance) AWS sa-east-1 (Degraded performance) AWS ap-southeast-5 (Degraded performance) AWS af-south-1 (Degraded performance) GCP europe-west6 (Degraded performance) AWS us-east-2 (Degraded performance) AWS us-west-2 (Degraded performance) GCP europe-west4 (Degraded performance) AWS eu-central-1 (Degraded performance) AWS ap-northeast-1 (Degraded performance) AWS ap-southeast-3 (Degraded performance) AWS eu-north-1 (Degraded performance) AWS il-central-1 (Degraded performance) GCP europe-west3 (Degraded performance) AWS ap-southeast-2 (Degraded performance) AWS ap-south-1 (Degraded performance) AWS ap-southeast-1 (Degraded performance) AWS mx-central-1 (Degraded performance) GCP northamerica-northeast1 (Degraded performance) AWS ap-east-2 (Degraded performance) AWS ca-central-1 (Degraded performance) GCP asia-northeast1 (Degraded performance) GCP us-central1 (Degraded performance) AWS ap-east-1 (Degraded performance) GCP europe-west2 (Degraded performance)

    • monitoring · Sep 24, 2026, 08:46 AM UTC

      Status: Monitoring We are seeing signs of improvements in most regions and pipes are resumed. Affected components AWS eu-west-1 (Degraded performance) AWS ap-northeast-1 (Degraded performance) AWS ap-southeast-3 (Degraded performance) AWS eu-west-2 (Degraded performance) GCP australia-southeast1 (Degraded performance) AWS ap-south-1 (Degraded performance) AWS us-west-2 (Degraded performance) GCP asia-southeast1 (Degraded performance) GCP us-west1 (Degraded performance) AWS us-east-1 (Degraded performance) AWS ap-northeast-2 (Degraded performance) AWS af-south-1 (Degraded performance) AWS ap-east-1 (Degraded performance) AWS ca-central-1 (Degraded performance) AWS il-central-1 (Degraded performance) GCP europe-west6 (Degraded performance) AWS sa-east-1 (Degraded performance) GCP us-central1 (Degraded performance) GCP europe-west3 (Degraded performance) AWS eu-central-1 (Degraded performance) AWS ap-southeast-1 (Degraded performance) GCP europe-west4 (Degraded performance) AWS ap-southeast-5 (Degraded performance) AWS ap-east-2 (Degraded performance) AWS us-east-2 (Degraded performance) AWS ap-southeast-2 (Degraded performance) GCP asia-northeast1 (Degraded performance) GCP northamerica-northeast1 (Degraded performance) AWS eu-north-1 (Degraded performance) AWS mx-central-1 (Degraded performance) GCP europe-west2 (Degraded performance)

    • monitoring · Sep 24, 2026, 09:01 AM UTC

      Status: Monitoring All regions recovered except us-east-1 region. It is also progressing and expected to be remediated soon. Affected components AWS us-west-2 (Operational) AWS ap-northeast-2 (Operational) AWS ap-east-1 (Operational) AWS mx-central-1 (Operational) GCP asia-northeast1 (Operational) AWS us-east-1 (Degraded performance) AWS ap-south-1 (Operational) AWS eu-west-1 (Operational) AWS ap-southeast-1 (Operational) AWS il-central-1 (Operational) GCP europe-west6 (Operational) AWS ap-northeast-1 (Operational) AWS ap-southeast-3 (Operational) GCP europe-west2 (Operational) AWS eu-central-1 (Operational) AWS ap-southeast-2 (Operational) AWS ca-central-1 (Operational) AWS ap-southeast-5 (Operational) AWS us-east-2 (Operational) GCP us-central1 (Operational) AWS af-south-1 (Operational) AWS eu-west-2 (Operational) AWS sa-east-1 (Operational) GCP australia-southeast1 (Operational) GCP europe-west3 (Operational) AWS ap-east-2 (Operational) AWS eu-north-1 (Operational) GCP europe-west4 (Operational) GCP asia-southeast1 (Operational) GCP us-west1 (Operational) GCP northamerica-northeast1 (Operational)

    • resolved · Sep 24, 2026, 09:05 AM UTC

      Status: Resolved All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future. Affected components AWS ap-northeast-1 (Operational) AWS il-central-1 (Operational) GCP asia-southeast1 (Operational) GCP us-west1 (Operational) AWS eu-central-1 (Operational) AWS ap-southeast-2 (Operational) GCP europe-west4 (Operational) GCP europe-west3 (Operational) GCP northamerica-northeast1 (Operational) AWS ap-southeast-3 (Operational) GCP asia-northeast1 (Operational) AWS ap-east-2 (Operational) AWS ap-northeast-2 (Operational) AWS af-south-1 (Operational) AWS eu-north-1 (Operational) AWS mx-central-1 (Operational) GCP us-central1 (Operational) GCP europe-west2 (Operational) GCP europe-west6 (Operational) AWS us-east-2 (Operational) AWS ca-central-1 (Operational) AWS us-east-1 (Operational) AWS eu-west-1 (Operational) GCP australia-southeast1 (Operational) AWS ap-southeast-5 (Operational) AWS ap-south-1 (Operational) AWS ap-east-1 (Operational) AWS ap-southeast-1 (Operational) AWS eu-west-2 (Operational) AWS sa-east-1 (Operational) AWS us-west-2 (Operational)

    Latest: Status: Resolved All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future. Affected components AWS …

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

Incident record

Since April 2026 · incident.io · 84 components checked every 5 minutes
64incidents recorded
62last 12 months
14last 90 days
3 daystypical duration, 12 months

The longest incident in the last year, Full outage on AWS me-central-1 region on March 1, 2026, ran for 82 days. 5 maintenance windows announced in the same period.

Most affected components, last 12 months

  • us-east-19
  • us-east-18
  • AWS us-east-17
  • eastus27
  • AWS eu-central-16

Latest incidents

  • Degraded support ticket submission and response October 23, 2026 · 3 hours · degraded service

    Status: Identified "Support Ticket Creation through Cloud Console is degraded, and other Salesforce integrated functions may be impacted due to an outage…

  • Google Cloud Outage October 20, 2026 · 7 hours · degraded service

    Status: Identified Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google…

  • Support case creation unavailable October 12, 2026 · 30 minutes · degraded service

    Status: Investigating We have identified an issue that prevents customers from creating new support cases and viewing existing cases in the ClickHouse Cloud…

Outage history

Past 90 days · 14 incidents View full outage history →