diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx
index 353c8ab73e..4e43dc27b3 100644
--- a/pages/serverless-containers/reference-content/containers-limitations.mdx
+++ b/pages/serverless-containers/reference-content/containers-limitations.mdx
@@ -73,6 +73,10 @@ Do not have your containers listen on these ports, as they are used by our servi
 * `PORT`: Value of the port defined in the Container settings, which the container has to listen on. You can use this environment variable inside your Container for easier deployments.
 * `SCW_*`: Reserved for product configuration (for example: token validation)
 
+### Dedicated IP
+
+**Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product.
+
 ## Private Network and Virtual Private Cloud (VPC) compatibility
 
 Refer to the [dedicated FAQ](/faq/serverless-containers/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Containers compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
diff --git a/pages/serverless-functions/reference-content/functions-limitations.mdx b/pages/serverless-functions/reference-content/functions-limitations.mdx
index 9f0bbabd19..3100d66bc0 100644
--- a/pages/serverless-functions/reference-content/functions-limitations.mdx
+++ b/pages/serverless-functions/reference-content/functions-limitations.mdx
@@ -61,6 +61,10 @@ Due to potential abuse (spam), no outbound traffic is allowed through following
 ### Reserved environment variables:
 * `SCW_*`: Reserved for product configuration (for example: token validation).
 
+### Dedicated IP
+
+**Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product.
+
 ## Private Network and Virtual Private Cloud (VPC) compatibility
 
 Refer to the [dedicated FAQ](/faq/serverless-functions/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Functions compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
diff --git a/pages/serverless-jobs/reference-content/jobs-limitations.mdx b/pages/serverless-jobs/reference-content/jobs-limitations.mdx
index 4977cdc43b..06be3a4002 100644
--- a/pages/serverless-jobs/reference-content/jobs-limitations.mdx
+++ b/pages/serverless-jobs/reference-content/jobs-limitations.mdx
@@ -55,6 +55,10 @@ In order to ensure the proper functioning of the product, we restrict the use of
   * **25**: Due to potential abuse (spam), no outbound traffic is allowed through this port, except from Scaleway Transactional Email SMTP servers.
   * **465**: Due to potential abuse (spam), no outbound traffic is allowed through this port, except from Scaleway Transactional Email SMTP servers.
 
+### Dedicated IP
+
+**Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product.
+
 ## Private Network and Virtual Private Cloud (VPC) compatibility
 
 Refer to the [dedicated FAQ](/faq/serverless-jobs/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Jobs compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).