diff --git a/akka-docs-dev/rst/java/http/client-side/host-level.rst b/akka-docs-dev/rst/java/http/client-side/host-level.rst
index d647ed4ab6..51fe6d3e12 100644
--- a/akka-docs-dev/rst/java/http/client-side/host-level.rst
+++ b/akka-docs-dev/rst/java/http/client-side/host-level.rst
@@ -80,6 +80,10 @@ response with its respective request. The way that this is done is by allowing t
 This context object of type ``T`` is completely opaque to Akka HTTP, i.e. you can pick whatever works best for your
 particular application scenario.
 
+.. note::
+  A consequence of using a pool is that long-running requests block a connection while running and may starve other
+  requests. Make sure not to use a connection pool for long-running requests like long-polling GET requests.
+  Use the :ref:`connection-level-api-java` instead.
 
 Connection Allocation Logic
 ---------------------------
diff --git a/akka-docs-dev/rst/java/http/client-side/request-level.rst b/akka-docs-dev/rst/java/http/client-side/request-level.rst
index 3c54a2a0b6..9c00c71d7b 100644
--- a/akka-docs-dev/rst/java/http/client-side/request-level.rst
+++ b/akka-docs-dev/rst/java/http/client-side/request-level.rst
@@ -7,6 +7,10 @@ The request-level API is the most convenient way of using Akka HTTP's client-sid
 :ref:`host-level-api-java` to provide you with a simple and easy-to-use way of retrieving HTTP responses from remote servers.
 Depending on your preference you can pick the flow-based or the future-based variant.
 
+.. note::
+  The request-level API is implemented on top of a connection pool that is shared inside the ActorSystem. A consequence of
+  using a pool is that long-running requests block a connection while running and starve other requests. Make sure not to use
+  the request-level API for long-running requests like long-polling GET requests. Use the :ref:`connection-level-api-java` instead.
 
 Flow-Based Variant
 ------------------
diff --git a/akka-docs-dev/rst/scala/http/client-side/host-level.rst b/akka-docs-dev/rst/scala/http/client-side/host-level.rst
index 242b2ebca9..01675807b9 100644
--- a/akka-docs-dev/rst/scala/http/client-side/host-level.rst
+++ b/akka-docs-dev/rst/scala/http/client-side/host-level.rst
@@ -79,6 +79,10 @@ response with its respective request. The way that this is done is by allowing t
 This context object of type ``T`` is completely opaque to Akka HTTP, i.e. you can pick whatever works best for your
 particular application scenario.
 
+.. note::
+  A consequence of using a pool is that long-running requests block a connection while running and may starve other
+  requests. Make sure not to use a connection pool for long-running requests like long-polling GET requests.
+  Use the :ref:`connection-level-api` instead.
 
 Connection Allocation Logic
 ---------------------------
diff --git a/akka-docs-dev/rst/scala/http/client-side/request-level.rst b/akka-docs-dev/rst/scala/http/client-side/request-level.rst
index 1f4c62ea11..c862b6fc82 100644
--- a/akka-docs-dev/rst/scala/http/client-side/request-level.rst
+++ b/akka-docs-dev/rst/scala/http/client-side/request-level.rst
@@ -7,6 +7,10 @@ The request-level API is the most convenient way of using Akka HTTP's client-sid
 :ref:`host-level-api` to provide you with a simple and easy-to-use way of retrieving HTTP responses from remote servers.
 Depending on your preference you can pick the flow-based or the future-based variant.
 
+.. note::
+  The request-level API is implemented on top of a connection pool that is shared inside the ActorSystem. A consequence of
+  using a pool is that long-running requests block a connection while running and starve other requests. Make sure not to use
+  the request-level API for long-running requests like long-polling GET requests. Use the :ref:`connection-level-api` instead.
 
 Flow-Based Variant
 ------------------