Skip to main content
Vendor reliability

Vendor record

ClickHouse Cloud

Vendor reports Operational

Checked

Front door check counts and ClickHouse Cloud’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented ClickHouse Cloud endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.clickhouse.cloud
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every ClickHouse Cloud product, region or your app worked.

How we count front door checks

ClickHouse Cloud says

Incident posts from ClickHouse Cloud’s status page, with its titles, impact levels and times. They say what ClickHouse Cloud chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

11

incidents ClickHouse Cloud posted, last 90 days

Median recorded duration: 1h 53m. From 10 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Support case creation unavailable

    Not specified

    First seen by CheckUpstream

    Closed in our record

  • Streaming ClickPipes degradation in AWS eu-central-1 region

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(29m)

    ClickHouse Cloud’s post

  • Some ClickPipes CDC pipes paused and can't be resumed

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(33m)

    ClickHouse Cloud’s post

  • We are investigating an issue affecting Azure eastus2 region

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(30m)

    ClickHouse Cloud’s post

  • We are investigating an issue with CH servers in Azure germanywestcentral region

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(5h 6m)

    ClickHouse Cloud’s post
6 older records

  • Intermittent Issues with the Support tab

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(13h 49m)

    ClickHouse Cloud’s post

  • ClickPipes failing on Kinesis in AWS us-east-1

    Critical

    Started, per ClickHouse Cloud

    Closed in our record(1d 5h)

    ClickHouse Cloud’s post

  • Distributed Cache performance degradation in AWS us-east-1

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(3h 59m)

    ClickHouse Cloud’s post

  • Service degradation in GCP us-central-1

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(19m)

    ClickHouse Cloud’s post

  • Provisioning of new CDC pipes for Postgres might be delayed or failing

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(1h 53m)

    ClickHouse Cloud’s post

  • We are investigating an issue in Azure eastus2 region, impacting replicas in one specific Availability Zone

    Minor

    Started, per ClickHouse Cloud

    Closed in our record(4h 49m)

    ClickHouse Cloud’s post

Your code, your dependencies

See which of your code paths call ClickHouse Cloud

Connect GitHub or GitLab to find where your public or private repository uses ClickHouse Cloud. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add ClickHouse Cloud status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · ClickHouse CloudStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/clickhouse-cloud?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="ClickHouse Cloud status badge"></iframe>

Frequently Asked Questions

Is ClickHouse Cloud currently down?

ClickHouse Cloud's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did ClickHouse Cloud last have an outage?

The most recent closed incident record began 4 days ago and spans 30 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for ClickHouse Cloud?

No. CheckUpstream checks ClickHouse Cloud’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor ClickHouse Cloud in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track ClickHouse Cloud?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors