fix(vpcrdb): correct routing info

Author: RoRoJ

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx

@@ -19,7 +19,7 @@ This improves performance by reducing the latency between your application and y
 You can create new Database Instances to attach to your Private Network, or attach existing ones.
 
 <Message type="note">
-  Managed Databases for PostgreSQL and MySQL is compatible with the [VPC routing](/vpc/concepts/#routing) feature, which allows you to connect one or more Database Instances in Private Network to resources in other Private Networks of the same VPC. Refer to the [How to manage routing](/vpc/how-to/manage-routing/) documentation page for more information.
+  Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with the [VPC routing](/vpc/concepts/#routing) feature, which allows you to connect one or more Database Instances in a Private Network to resources in other Private Networks of the same VPC. Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. Refer to the [How to manage routing](/vpc/how-to/manage-routing/) documentation page for more information about VPC routing.
 </Message>
 
 <Requirements />

pages/vpc/faq.mdx

@@ -42,6 +42,10 @@ Yes, use the [Network ACL feature](/vpc/reference-content/understanding-nacls/)
 NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console.
 </Message>
 
+### Why can I not route traffic to my Managed Database on another Private Network?
+
+Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. 
+
 ### How are NACLs different from security groups?
 
 [Security groups](/instances/how-to/use-security-groups/) filter **public** traffic on your Instances, whereas NACLs filter traffic to/from Private Networks only.

pages/vpc/how-to/manage-routing.mdx

@@ -193,7 +193,7 @@ Follow the steps below to define a custom route:
 
 8. Enter a **next hop** for the route. The VPC will route traffic for the destination IP to the resource designated as next hop.
     - Select the Private Network which the next hop resource is attached to.
-    - Select a resource type: **Instance**, **Public Gateway** or **Elastic Metal**.
+    - Select a resource type, e.g. **Instance**, **Public Gateway** or **Elastic Metal**.
     - Select the **name** of the specific resource you want to route traffic to. The resource must be attached to a Private Network in this VPC.
 
     <Message type="note">

pages/vpc/reference-content/understanding-routing.mdx

@@ -156,4 +156,5 @@ Alternatively, and aligned with best practice, when the default NACL rule **Deni
 
 ## Limitations
 
+- Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with VPC routing. Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well.
 - VPC routing does not currently support virtual IPs.

pages/vpc/troubleshooting/vpc-limitations.mdx

@@ -22,4 +22,5 @@ This page sets out some current limitations of Scaleway's VPC.
   - Kubernetes Kapsule (only during the process of creating the Kapsule cluster)
   - Serverless Functions and Containers (egress traffic only, with VPC-supporting namespaces)
 - Private Networks are not supported on some legacy Instance offers which have reached EOL, e.g. `VC1`, `START1` and `X64-*GB`. Note that all Instance offers in the [current product catalogue](https://www.scaleway.com/en/pricing/?tags=compute) are supported.
+- Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. 
 

pages/vpc/troubleshooting/vpc-pn-routing-connectivity-issues.mdx

@@ -18,6 +18,10 @@ This is standard behavior:
 - Once you have activated routing on a VPC, you cannot deactivate it
 - You do not have the option to create a new VPC where routing is deactivated
 
+## My Managed Database cannot communicate with other resources in my VPC
+
+Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. 
+
 ## I cannot route between VPCs/Private Networks in different regions, or different Scaleway Projects.
 
 Currently, routing is only supported between Private Networks in a single VPC. We do not support: