OneView experienced a minor incident on October 19, 2026 affecting europe-west4 and europe-west4 and 1 more component, lasting 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Oct 19, 2026, 12:11 PM UTC
Status: Monitoring We've identified a slowdown on Clickhouse Cloud europe-west4 Cluster, we're monitoring the situation with Clickhouse team. Affected components OneView Dashboard (Partial outage) europe-west4 (Full outage) europe-west4 (Partial outage)
- monitoring Oct 19, 2026, 12:26 PM UTC
Status: Monitoring Clickhouse is restoring service. OneView API is back online. Affected components OneView Dashboard (Operational) europe-west4 (Full outage) europe-west4 (Operational)
- resolved Oct 19, 2026, 12:28 PM UTC
Status: Resolved We identified the cause of the issue to live on Clickhouse Cloud. Its actually a combination of several factors. • In summary: • System logs tables cleanup is a single transaction with a lot of operation in it. • While this transaction is running, other writes to the logs on this given replica are locked, and sometimes it might take time. • Because of the lock, Idle controller was not able to get the service usage stats and considered this "no activity" as the idle trigger. • The existing pod was not terminated immediately due to ongoing background activity (there is an up to 1h grace period to let the replica complete ongoing tasks before pod termination), and this caused delays in launching the new pod when the service was un-idled a few mins later. • Clickhouse team has a confirmed fix for this in the newer version and their engineering team is working on the back-port. As soon as the back-port is ready, our cluster will be upgraded to the version with the fix. Affected components europe-west4 (Operational) OneView Dashboard (Operational) europe-west4 (Operational)