ClickHouse Cloud · 19 Nov 2026
ClickHouse Cloud Problems – 19 Nov 2026
✓Resolved42 min
ClickHouse Cloud had problems starting at 04:14 UTC. The incident lasted 42 min and is now resolved.
- SeverityProblems
- Started19 Nov 2026, 04:14 UTC
- Ended19 Nov 2026, 04:56 UTC
- Duration42 min
- Detected byOfficial status page
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
- Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
16 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
9 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
11 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
57 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
1 h 25 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
32 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
29 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
31 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
39 min - Problems19 Nov 2026
Lightweight updates can cause undesired effects — We’ve discovered an issue where enabling lightweight updates on an **existing table** via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_bloc…
2 h 20 min