diff --git a/pages/cockpit/how-to/manage-data-exports.mdx b/pages/cockpit/how-to/manage-data-exports.mdx
index f5aa414031..909b964096 100644
--- a/pages/cockpit/how-to/manage-data-exports.mdx
+++ b/pages/cockpit/how-to/manage-data-exports.mdx
@@ -123,3 +123,21 @@ To check whether a data export generates errors:
 
 You are **responsible for how your exported data is used** and for **any changes in resource volume**. Adding resources naturally increases the number of generated metrics and logs, and the exported volume may fluctuate even without manual action (for example, autoscaling creates additional resources, resulting in more data to export).
 Find out how data exports are billed in the [dedicated documentation page](/cockpit/reference-content/cockpit-pricing/#billing-information-for-cockpit-data-exports).
+
+## How to check the status of your data exports
+
+The console displays status information about each data export to help you assess the health of your exports and whether or not you need to take any action.
+
+1. Click **Cockpit** in the **Monitoring** section of the [console](https://console.scaleway.com/) side menu. The Cockpit overview page displays.
+2. Click the **Data export** tab. The list of your data exports displays.
+3. Hover over the status indicator next to your data export to check status. Here is what each status means:
+
+    - **Creating**: The data export is being created.
+    - **Ready**: The data export is up and running.
+    - **Disabled**: No logs or metrics have been successfully transferred to the destination servers for at least 24 hours. Typical causes of a failed data transfer include an incorrect URL or a destination server error. 
+
+    <Message type="tip">
+        As a temporary workaround, re-enable the data export by editing and saving its configuration.
+    </Message>
+
+    - **Error**: The data export is failing. Common reasons are a server-side outage or an ongoing incident.
\ No newline at end of file