Is ClickHouse Cloud Down?

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:<region>:<account-id>:stream/<stream-name>/consumer/<consumer-name>`) rather than the stream resource (for example, `arn:aws:kinesis:<region>:<account-id>:stream/<stream-name>`). 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. --- [2026-09-15T22:45:45Z] (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. --- [2026-09-15T20:06:07Z] (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. --- [2026-09-15T19:10:26Z] (investigating) Currently investigating failures on AWS us-east-1 for customers using ClickPipes on Kinesis in this region.

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> --- [2026-09-14T22:41:00Z] (monitoring) Impacted services have been updated and are now fully operational. ClickHouse is monitoring. --- [2026-09-14T21:28:27Z] (identified) ClickHouse has identified the cause and proceeding with remedying impacted services. --- [2026-09-14T20:36:13Z] (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.

All systems operational. GCP incident has no impact on ClickHouse Cloud. --- [2026-09-01T16:19:54Z] (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. --- [2026-09-01T16:12:48Z] (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.