Lightweight updates can cause undesired effects
ClickHouse Cloud reports that lightweight updates on an existing table can cause incorrect results when setting enableblocknumbercolumn = 1. ClickHouse Cloud is investigating. The provider gives this workaround: create a new table and set enableblockoffsetcolumn = 1 on the table before you insert data.
State
Investigating
Started
Ongoing for
22 min
Worst impact
Degraded
Timeline
1 updateInvestigating
22 min 100%
Updates
Times in UTCAs posted by ClickHouse Cloud
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_block_offset_column = 1` on the table first before inserting any data into it.
ClickHouse Cloud in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
16
Median duration
50 min
This incident
56% shorter than the median
Other ClickHouse Cloud incidents
All incidentsClickHouse Cloud·Provisioning may be degraded
ClickHouse Cloud provisioning was slow in many regions. ClickHouse Cloud reports that the issue is resolved. It lasted 48 minutes, from 12:14 to 13:02 UTC.
ClickHouse Cloud·Provisioning and scaling operations may take longer in AWS ap-northeast-1 Tokyo
ClickHouse Cloud provisioning and scaling operations took longer than usual in AWS ap-northeast-1 (Tokyo). The incident is resolved and lasted about 7 hours and 38 minutes.
ClickHouse Cloud·SQL Console database connection outage
ClickHouse Cloud reported a SQL Console database connection outage. The outage affected Dashboards, Query endpoints, Saved queries, and UDFs. ClickHouse Cloud resolved the incident after 50 minutes.
ClickHouse Cloud·Degraded support ticket submission and response
``` Salesforce team resolved the issue that prevented users from logging in. They identified an issue with a recent release that prevented login sessions from being created. Deployed a fix forward, and access is now restored. Users can log in and open their orgs again. https://status.salesforce.com/incidents/20004512 ```
ClickHouse Cloud·Google Cloud Outage
The issue has been resolved. All services are fully operational.
Follow ClickHouse Cloud
Your coding agent knows when ClickHouse Cloud is down, and tells you when a failure is theirs, not yours. You can also get ClickHouse Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "clickhouse" and tell me if ClickHouse Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=clickhouse/feed subscribe https://outages.live/feed.xml?providers=clickhouseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane