Slow provisioning and operations in AWS us-east-1 region
Jul 6, 12:34 UTCJul 6, 15:03 UTC
Duration
2h 29m
Impact
Minor
Root cause
Not disclosed
ClickHouse, 90 days
15 incidents
Affected
Not listed by the vendor.
Final update
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")
Timeline
- Resolved · Jul 6, 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")
- Identified · Jul 6, 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")
- Identified · Jul 6, 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.
More from ClickHouse
Full historySQL Console database connection outagelasted 50mDegraded support ticket submission and responselasted 2h 48mGoogle Cloud Outagelasted 6h 44mSupport case creation unavailablelasted 31mStreaming ClickPipes degradation in AWS eu-central-1 regionlasted 29mSome ClickPipes CDC pipes paused and can't be resumedlasted 33m