The incident was caused by an overloaded database. The instance was scaled up. It is stable again now. We are investigating heavy queries and will apply improvements.

AWS Middle East (UAE) Region (ME-CENTRAL-1) is still experiencing severe disruptions. We are actively monitoring the situation and following updates from AWS. Please follow the https://health.aws.amazon.com/health/status page for latest updates.

The operational impact affecting ClickPipes in the us-east-1 region has been fully resolved.

All systems are operating normally, including ingestion and operational functionality. We will continue to monitor the platform to ensure ongoing stability.
Thank you for your patience.

All services stuck in waking in all azure regions are started now.

All systems operational. We apologize for the disruption this issue caused. We are committed to the reliability of all ClickHouse Cloud services and appreciate your understanding as we continue to improve our systems and operations. If you have questions or need information on a specific ClickHouse service, please contact support.

Maintenance has completed

Maintenance operation was completed

Maintenance has completed

Maintenance operation is complete

Maintenance has completed

After verifying that all affected ClickPipes have recovered, the incident can be declared as resolved. We will be sharing an RCA in the next few days with the affected customers. We sincerely apologize for the disruption caused.

We have confirmed that all systems are stable and operating normally. The networking configuration has been fully restored across all regions, and we have implemented additional monitoring and safeguards to prevent recurrence.

We will continue to monitor systems closely over the coming days as part of our standard post-incident procedures, and share an RCA as soon as possible.

The issue is fully resolved. The latest data in ControlPlane UI monitoring dashboards was backfilled and should be available.

The issue seems to be related to networking issues on underlying VMs. Team is investigating the root cause to make sure it won't happen again or in other regions.

We have fixed the issue in authentication.

The issue has been resolved, and the Azure germanywestcentral region is fully operational.