From e48a101a42063b4b161ee31d2939e901558d16bf Mon Sep 17 00:00:00 2001
From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com>
Date: Wed, 15 Oct 2025 10:52:26 +0200
Subject: [PATCH] fix(rdb): remove vpc routing info

---
 .../how-to/connect-database-instance.mdx                      | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
index c7311aefe0..2bb34fdd63 100644
--- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
+++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
@@ -51,10 +51,6 @@ 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 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>
-
 ### How to attach a Database Instance to a Private Network
 
 <Message type="note">