ClickHouse Cloud incident: Slow provisioning and operations in AWS us-east-1 region

1. resolvedJul 6, 2026, 15:03 UTC

   The incident was resolved and we don't see any impact in us-east-1 region anymore. For details, please refer to the AWS Health status page: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

2. identifiedJul 6, 2026, 13:09 UTC

   The issue is caused by AWS outage, please see [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

3. identifiedJul 6, 2026, 12:34 UTC

   We have identified an issue with provisioning of new instances and autoscaling operations in AWS us-east-1 region. Connection latencies for CH servers can be also affected due to slow provisioning of compute nodes. ClickHouse Cloud is working with AWS support team to fix the issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in ClickHouse Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluence: Reliability issues with Jira and ConfluenceCritical · Jul 6, 2026, 09:23 UTC
• Linode: Service Issue - ACLP MetricsMinor · Jun 26, 2026, 17:35 UTC
• LaunchDarkly: Verification emails not being sentMinor · Jul 6, 2026, 14:33 UTC

How often does ClickHouse Cloud have incidents?

ClickHouse Cloud reported 16 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 2h 28m. See ClickHouse Cloud's uptime and incident history