ClickHouse · Blargian · Dec 2, 2025 · Nov 25, 2025 · Nov 25, 2025 · Nov 25, 2025
@@ -4,7 +4,7 @@ title: 'v24.2 Changelog'
 description: 'Fast release changelog for v24.2'
 keywords: ['changelog']
 sidebar_label: '24.2'
-sidebar_position: 9
+sidebar_position: 10
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v24.5 Changelog for Cloud'
 description: 'Fast release changelog for v24.5'
 keywords: ['changelog', 'cloud']
 sidebar_label: '24.5'
-sidebar_position: 8
+sidebar_position: 9
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v24.6 Changelog for Cloud'
 description: 'Fast release changelog for v24.6'
 keywords: ['changelog', 'cloud']
 sidebar_label: '24.6'
-sidebar_position: 7
+sidebar_position: 8
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v24.8 Changelog for Cloud'
 description: 'Fast release changelog for v24.8'
 keywords: ['changelog', 'cloud']
 sidebar_label: '24.8'
-sidebar_position: 6
+sidebar_position: 7
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v24.10 Changelog for Cloud'
 description: 'Fast release changelog for v24.10'
 keywords: ['changelog', 'cloud']
 sidebar_label: '24.10'
-sidebar_position: 5
+sidebar_position: 6
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v24.12 Changelog for Cloud'
 description: 'Fast release changelog for v24.12'
 keywords: ['changelog', 'cloud']
 sidebar_label: '24.12'
-sidebar_position: 4
+sidebar_position: 5
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v25.4 Changelog for Cloud'
 description: 'Fast release changelog for v25.4'
 keywords: ['changelog', 'cloud']
 sidebar_label: '25.4'
-sidebar_position: 3
+sidebar_position: 4
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v25.6 Changelog for Cloud'
 description: 'Fast release changelog for v25.6'
 keywords: ['changelog', 'cloud']
 sidebar_label: '25.6'
-sidebar_position: 2
+sidebar_position: 3
 doc_type: 'changelog'
 ---
 

@@ -4,7 +4,7 @@ title: 'v25.8 Changelog for Cloud'
 description: 'Fast release changelog for v25.8'
 keywords: ['changelog', 'cloud']
 sidebar_label: '25.8'
-sidebar_position: 1
+sidebar_position: 2
 doc_type: 'changelog'
 ---
 

@@ -0,0 +1,51 @@
+---
+title: 'Release status page'
+sidebar_label: 'Release status'
+keywords: ['aws', 'gcp', 'google cloud', 'azure', 'cloud', 'regions']
+description: 'Page with release status for each release channel'
+slug: /cloud/release-status
+doc_type: 'reference'
+---
+
+import ReleaseSchedule from '@site/src/components/ReleaseSchedule/ReleaseSchedule';
+
+ClickHouse Cloud offers different release channels to cater to different user needs regarding stability, access to new features, and upgrade predictability. Each channel has a distinct upgrade schedule and is meant to address the different usecases - for users that want instant access to new releases and those that want to defer upgrades to ensure they receive the most stable version of the release.
+
+## Release channel details {#release-channel-details}
+
+<details>
+<summary>Learn more about release channels</summary>
+
+| Channel Name | Description | Key Considerations | Tiers Supported |
+| :--- | :--- | :--- | :--- |
+| **Fast (Early Release)** | Recommended for non production environments. This is the first release channel for every database version upgrade | New feature access over stability.<br/>Ability to test releases in non production environments ahead of production upgrade | Basic (default)<br/>Scale, Enterprise tiers |
+| **Regular** | Default release channel for all multi replica services.<br/>Updates on this channel typically happen two weeks post the Fast release channel. | Default/ fleetwide upgrades.<br/>Upgrades on this channel are usually done two weeks post the Fast release channel upgrade | Scale and Enterprise |
+| **Slow (Deferred)** | Recommended for those more risk averse users that want their services to be upgraded towards the end of the release schedule.<br/>Updates on this channel typically happen two weeks post the Regular release channel. | Maximum stability and predictability.<br/>Meant for users that need more testing of new releases on either the Fast/Regular channel | Enterprise |
+
+<br/>
+<br/>
+
+:::note
+All single replica services are automatically enrolled in the Fast release channel.
+:::
+
+</details>
+
+Scheduled upgrades are available for all release channels for services in the Enterprise tier. This feature allows users to configure a time window on a given day of the week for upgrades.
+
+## Release schedule {#release-schedule}
+
+The release dates given below are an estimate and may be subject to change.
+
+<ReleaseSchedule releases={[
+   {
+    changelog_link: 'https://clickhouse.com/docs/changelogs/25.10',
+    version: '25.10',
+    fast_date: '2025-12-09',
+    regular_date: '2026-01-05',
+    slow_date: 'TBD',
+    fast_progress: 'green',
+    regular_progress: 'green',
+    slow_progress: 'green'
+  }
+]} />
@@ -596,7 +596,7 @@ Dictionaries can be used for enriching datasets at query time or insert time. Ea
 - **Insert time** - This is typically appropriate if the enrichment value does not change and exists in an external source which can be used to populate the dictionary. In this case, enriching the row at insert time avoids the query time lookup to the dictionary. This comes at the cost of insert performance as well as an additional storage overhead, as enriched values will be stored as columns.
 - **Query time** - If values in a dictionary change frequently, query time lookups are often more applicable. This avoids needing to update columns (and rewrite data) if mapped values change. This flexibility comes at the expense of a query time lookup cost. This query time cost is typically appreciable if a lookup is required for many rows, e.g. using a dictionary lookup in a filter clause. For result enrichment, i.e. in the `SELECT`, this overhead is typically not appreciable.
 
-We recommend that users familiarize themselves with the basics of dictionaries. Dictionaries provide an in-memory lookup table from which values can be retrieved using dedicated [specialist functions](/sql-reference/functions/ext-dict-functions#dictgetall).
+We recommend that users familiarize themselves with the basics of dictionaries. Dictionaries provide an in-memory lookup table from which values can be retrieved using dedicated [specialist functions](/sql-reference/functions/ext-dict-functions#dictGetAll).
 
 For simple enrichment examples see the guide on Dictionaries [here](/dictionary). Below, we focus on common observability enrichment tasks.
 

@@ -0,0 +1,102 @@
+.tableWrapper {
+  overflow-x: auto;
+  margin-bottom: 1rem;
+}
+
+.table {
+  width: 100%;
+  border-collapse: collapse;
+  font-size: 0.9rem;
+}
+
+.table th,
+.table td {
+  border: 1px solid var(--ifm-table-border-color);
+  padding: 0.75rem;
+  text-align: left;
+}
+
+.table th {
+  background-color: var(--ifm-table-head-background);
+  font-weight: bold;
+}
+
+.statusCell {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+}
+
+.statusIndicator {
+  width: 10px;
+  height: 10px;
+  border-radius: 50%;
+  display: inline-block;
+}
+
+.statusGreen {
+  background-color: #28a745;
+}
+
+.statusOrange {
+  background-color: #fd7e14;
+}
+
+.statusRed {
+  background-color: #dc3545;
+}
+
+.tooltipContainer {
+  position: relative;
+  display: inline-block;
+  cursor: help;
+}
+
+.tooltip {
+  visibility: hidden;
+  width: 200px;
+  background-color: var(--ifm-color-emphasis-900);
+  color: var(--ifm-color-content-inverse);
+  text-align: center;
+  border-radius: 6px;
+  padding: 5px;
+  position: absolute;
+  z-index: 1;
+  bottom: 125%; /* Position above */
+  left: 50%;
+  margin-left: -100px;
+  opacity: 0;
+  transition: opacity 0.3s;
+  font-size: 0.8rem;
+  pointer-events: none;
+}
+
+.tooltip::after {
+  content: "";
+  position: absolute;
+  top: 100%;
+  left: 50%;
+  margin-left: -5px;
+  border-width: 5px;
+  border-style: solid;
+  border-color: var(--ifm-color-emphasis-900) transparent transparent transparent;
+}
+
+.tooltipContainer:hover .tooltip {
+  visibility: visible;
+  opacity: 1;
+}
+
+.infoIcon {
+  display: inline-flex;
+  justify-content: center;
+  align-items: center;
+  width: 16px;
+  height: 16px;
+  border-radius: 50%;
+  background-color: var(--ifm-color-emphasis-300);
+  color: var(--ifm-color-content);
+  font-size: 0.7rem;
+  font-weight: bold;
+  margin-left: 0.5rem;
+}
@@ -0,0 +1,108 @@
+import React from 'react';
+import styles from './ReleaseSchedule.module.css';
+
+type ProgressStatus = 'green' | 'orange' | 'red';
+
+interface ReleaseRow {
+  version: string;
+  changelog_link?: string;
+  fast_date: string;
+  regular_date: string;
+  slow_date: string;
+  fast_delay_note?: string;
+  regular_delay_note?: string;
+  slow_delay_note?: string;
+  fast_progress: ProgressStatus;
+  regular_progress: ProgressStatus;
+  slow_progress: ProgressStatus;
+}
+
+interface ReleaseScheduleProps {
+  releases: ReleaseRow[];
+}
+
+const StatusIndicator = ({ status }: { status: ProgressStatus }) => {
+  const statusClass =
+    status === 'green'
+      ? styles.statusGreen
+      : status === 'orange'
+        ? styles.statusOrange
+        : styles.statusRed;
+  return <span className={`${styles.statusIndicator} ${statusClass}`} />;
+};
+
+const DateCell = ({
+  date,
+  note,
+  status,
+}: {
+  date: string;
+  note?: string;
+  status: ProgressStatus;
+}) => {
+  return (
+    <div className={styles.statusCell}>
+      <StatusIndicator status={status} />
+      <span>{date}</span>
+      {note && (
+        <div className={styles.tooltipContainer}>
+          <span className={styles.infoIcon}>i</span>
+          <span className={styles.tooltip}>{note}</span>
+        </div>
+      )}
+    </div>
+  );
+};
+
+export default function ReleaseSchedule({ releases }: ReleaseScheduleProps) {
+  return (
+    <div className={styles.tableWrapper}>
+      <table className={styles.table}>
+        <thead>
+          <tr>
+            <th>Version</th>
+            <th>Fast Channel (Estimated)</th>
+            <th>Regular Channel (Estimated)</th>
+            <th>Slow Channel (Estimated)</th>
+          </tr>
+        </thead>
+        <tbody>
+          {releases.map((release, index) => (
+            <tr key={index}>
+              <td>
+                {release.changelog_link ? (
+                  <a href={release.changelog_link} target="_blank" rel="noopener noreferrer">
+                    {release.version}
+                  </a>
+                ) : (
+                  release.version
+                )}
+              </td>
+              <td>
+                <DateCell
+                  date={release.fast_date}
+                  note={release.fast_delay_note}
+                  status={release.fast_progress}
+                />
+              </td>
+              <td>
+                <DateCell
+                  date={release.regular_date}
+                  note={release.regular_delay_note}
+                  status={release.regular_progress}
+                />
+              </td>
+              <td>
+                <DateCell
+                  date={release.slow_date}
+                  note={release.slow_delay_note}
+                  status={release.slow_progress}
+                />
+              </td>
+            </tr>
+          ))}
+        </tbody>
+      </table>
+    </div>
+  );
+}