diff --git a/tidb-cloud/serverless-faqs.md b/tidb-cloud/serverless-faqs.md
index 470a0ad66dc1d..4561e6d2bd33f 100644
--- a/tidb-cloud/serverless-faqs.md
+++ b/tidb-cloud/serverless-faqs.md
@@ -84,6 +84,10 @@ For more information about how to set up TiFlash replicas, see [Create TiFlash r
 
 When you connect via a Public Endpoint, your connection passes through various network providers and intermediate devices. These devices might have their own short idle timeouts, which can interrupt your connection prematurely. For more information, see [Connection limitations](/tidb-cloud/serverless-limitations.md#connection).
 
+### Why did I receive a "Connection limit exceeded" error?
+
+This error occurs when your cluster exceeds its maximum concurrent connection limit. For more information, see [Connection limitations](/tidb-cloud/serverless-limitations.md#connection).
+
 ## Billing and metering FAQs
 
 ### What are Request Units?
diff --git a/tidb-cloud/serverless-limitations.md b/tidb-cloud/serverless-limitations.md
index 81ce6a1b483bf..359502e0ef930 100644
--- a/tidb-cloud/serverless-limitations.md
+++ b/tidb-cloud/serverless-limitations.md
@@ -23,6 +23,7 @@ We are constantly filling in the feature gaps between {{{ .starter }}}/Essential
 - Only [Public Endpoint](/tidb-cloud/connect-via-standard-connection-serverless.md) and [Private Endpoint](/tidb-cloud/set-up-private-endpoint-connections-serverless.md) can be used. You cannot use [VPC Peering](/tidb-cloud/set-up-vpc-peering-connections.md) to connect to {{{ .starter }}} or {{{ .essential }}} clusters.
 - No [Firewall Rules](/tidb-cloud/configure-serverless-firewall-rules-for-public-endpoints.md) support for Private Endpoint.
 - Your database client connections might be terminated unexpectedly if they remain open for more than 30 minutes. This can occur when a TiDB server shuts down, restarts, or undergoes maintenance, potentially causing application disruptions. To avoid this issue, configure a maximum connection lifetime. It is recommended to start with 5 minutes and increase it gradually if it affects tail latency. For more information, see [Recommended settings for connection pools](/develop/dev-guide-connection-parameters.md).
+- For a {{{ .starter }}} cluster, you can have up to 400 concurrent connections. This limit increases to 5,000 if you set a spending limit.
 
 > **Note:**
 >