diff --git a/docs/guides/high-availability/multi-cluster/building-blocks.adoc b/docs/guides/high-availability/multi-cluster/building-blocks.adoc
index 0affeea4413..4f91025aaac 100644
--- a/docs/guides/high-availability/multi-cluster/building-blocks.adoc
+++ b/docs/guides/high-availability/multi-cluster/building-blocks.adoc
@@ -19,7 +19,9 @@ include::../partials/blueprint-disclaimer.adoc[]
 
 == Two sites with low-latency connection
 
-Ensures that synchronous replication is available for both the database and the external {jdgserver_name}.
+{project_name} requires a low latency network connection for the synchronous replication of data by the database and the external {jdgserver_name}.
+
+include::../partials/network-latency.adoc[]
 
 *Suggested setup:* Two AWS Availability Zones within the same AWS Region.
 
diff --git a/docs/guides/high-availability/partials/network-latency.adoc b/docs/guides/high-availability/partials/network-latency.adoc
new file mode 100644
index 00000000000..ac0b0d7150a
--- /dev/null
+++ b/docs/guides/high-availability/partials/network-latency.adoc
@@ -0,0 +1,10 @@
+////
+See https://www.cloudping.co/ for an overview of AWS latencies inside of a region, for example, from eu-west-1 to eu-west-1.
+The latency within a region is the latency between AZs.
+////
+
+A P50 round-trip latency of less than 5 ms is suggested and below 10 ms is strongly recommended, together with a reliable network between the zones to avoid unexpected problems with latency, throughput or connectivity.
+
+Network latency and latency spikes amplify in the response time of the service and can lead to queued requests, timeouts, and failed requests.
+Networking problems can cause downtimes until the failure detection isolates problematic nodes.
+
diff --git a/docs/guides/high-availability/single-cluster/building-blocks.adoc b/docs/guides/high-availability/single-cluster/building-blocks.adoc
index 7dc5b9c43c8..3ecc9b22f3f 100644
--- a/docs/guides/high-availability/single-cluster/building-blocks.adoc
+++ b/docs/guides/high-availability/single-cluster/building-blocks.adoc
@@ -22,7 +22,9 @@ include::../partials/blueprint-disclaimer.adoc[]
 [#single-cluster-blocks-low-latency]
 == Multiple availability-zones with low-latency connection
 
-Ensures that synchronous replication is available for both the database and {project_name} clustering.
+{project_name} requires a low latency network connection for the synchronous replication of data by the database and {project_name} clustering.
+
+include::../partials/network-latency.adoc[]
 
 *Suggested setup:* A {kubernetes} cluster consisting of two or more AWS Availability Zones within the same AWS Region.