diff --git a/pages/clustering/high-availability.mdx b/pages/clustering/high-availability.mdx
index 7cfb9da23..fa0d39f1f 100644
--- a/pages/clustering/high-availability.mdx
+++ b/pages/clustering/high-availability.mdx
@@ -295,7 +295,6 @@ e.g during a maintenance work on the instance where the current main is deployed
 </Callout>
 
 
-
 ### Unregister instance
 
 There are various reasons which could lead to the decision that an instance needs to be removed from the cluster. The hardware can be broken,
@@ -366,6 +365,16 @@ This query will return the information about:
 
 If the query `ADD COORDINATOR` wasn't run for the current instance, the value of the bolt server will be "".
 
+### Show replication lag
+
+The user can find the current replication lag on each instance by running `SHOW REPLICATION LAG` on the cluster's leader. The replication lag is expressed with
+the number of committed transactions. Such an info is made durable through snapshots and WALs so restarts won't cause the information loss. The information
+about the replication lag can be useful when manually performing a failover to check whether there is a risk of a data loss.
+
+```plaintext
+SHOW REPLICATION LAG;
+```
+
 
 ## Setting config for highly-available cluster