diff --git a/pages/vpc-peering/concepts.mdx b/pages/vpc-peering/concepts.mdx
index de872d427a..7a42c305e9 100644
--- a/pages/vpc-peering/concepts.mdx
+++ b/pages/vpc-peering/concepts.mdx
@@ -51,6 +51,8 @@ Scaleway VPC Peering natively supports transitive peering across up to four chai
 
 To allow transitive peering across chained VPCs, additional [custom routes](#custom-routes) must be created in each VPC of the transitive chain.
 
+Refer to the [dedicated documentation](/vpc-peering/reference-content/understanding-transitive-peering/) for more information on transitive peering.
+
 ## VPC Peering
 
 Scaleway VPC Peering is a networking service that enables two Scaleway VPCs to establish a private peering connection and route traffic between their resources.
diff --git a/pages/vpc-peering/faq.mdx b/pages/vpc-peering/faq.mdx
index 281f00ff7b..1dc7f076b7 100644
--- a/pages/vpc-peering/faq.mdx
+++ b/pages/vpc-peering/faq.mdx
@@ -47,7 +47,9 @@ No. Only VPCs in the same Scaleway region can be peered.
 
 ### Does Scaleway VPC Peering support transitive peering?
 
-Yes, you can chain several VPCs using peering connectors, and benefit from transitivity between up to four VPCs using custom routes. Refer to the [concepts page](/vpc-peering/concepts/#transitive-peering/) for more information.
+Yes, you can chain several VPCs using peering connectors, and benefit from transitivity between up to four VPCs using custom routes.
+
+Refer to the [dedicated documentation](/vpc-peering/reference-content/understanding-transitive-peering/) for more information on transitive peering.
 
 ## Access and security
 
diff --git a/pages/vpc-peering/menu.ts b/pages/vpc-peering/menu.ts
index 9bd9104d10..d2bbd4b5f3 100644
--- a/pages/vpc-peering/menu.ts
+++ b/pages/vpc-peering/menu.ts
@@ -58,6 +58,10 @@ export const vpcPeeringMenu = {
           label: 'Features and limitations',
           slug: 'features-limitations',
         },
+        {
+          label: 'Understanding transitive peering',
+          slug: 'understanding-transitive-peering',
+        },
         {
           label: 'VPC Peering statuses',
           slug: 'statuses',
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-full-transitivity-4.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-full-transitivity-4.webp
new file mode 100644
index 0000000000..3d552eeb03
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-full-transitivity-4.webp differ
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-3.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-3.webp
new file mode 100644
index 0000000000..f9e4c124a5
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-3.webp differ
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-4.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-4.webp
new file mode 100644
index 0000000000..797876dadf
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-no-transitivity-4.webp differ
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-simple-co.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-simple-co.webp
new file mode 100644
index 0000000000..eb92937e3a
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-simple-co.webp differ
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-3.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-3.webp
new file mode 100644
index 0000000000..d7481b4307
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-3.webp differ
diff --git a/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-4.webp b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-4.webp
new file mode 100644
index 0000000000..d56a5f151d
Binary files /dev/null and b/pages/vpc-peering/reference-content/assets/scaleway-vpc-peering-transitivity-4.webp differ
diff --git a/pages/vpc-peering/reference-content/understanding-transitive-peering.mdx b/pages/vpc-peering/reference-content/understanding-transitive-peering.mdx
new file mode 100644
index 0000000000..334e253f98
--- /dev/null
+++ b/pages/vpc-peering/reference-content/understanding-transitive-peering.mdx
@@ -0,0 +1,71 @@
+---
+title: Understanding transitive peering
+description: This page helps users understand how transitivity works when using Scaleway VPC Peering.
+tags: peering transitivity daisy chained hub spoke
+dates:
+  validation: 2026-05-18
+  posted: 2026-05-18
+---
+
+import peeringSimple from './assets/scaleway-vpc-peering-simple-co.webp'
+import peeringNoTransitivity3 from './assets/scaleway-vpc-peering-no-transitivity-3.webp'
+import peeringTransitivity3 from './assets/scaleway-vpc-peering-transitivity-3.webp'
+import peeringNoTransitivity4 from './assets/scaleway-vpc-peering-no-transitivity-4.webp'
+import peeringTransitivity4 from './assets/scaleway-vpc-peering-transitivity-4.webp'
+import peeringFullTransitivity from './assets/scaleway-vpc-peering-full-transitivity-4.webp'
+
+<Message type="note">
+VPC Peering is currently in Public Beta.
+</Message>
+
+## Overview
+
+Scaleway VPC Peering natively supports transitive peering.
+
+Transitive peering (or transitive routing) allows two VPCs that are not directly peered to exchange traffic through a third VPC that is peered with both. Traffic is forwarded through this intermediate network, making the connection transitive.
+
+To enable transitivity, you must [define custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) in each VPC.
+
+For example, if VPC A is peered with both VPC B and VPC C, you can route traffic between VPC B and VPC C through VPC A. To do so, define a custom route in VPC B directing traffic to VPC C via VPC A, and a corresponding route in VPC C directing traffic to VPC B via VPC A.
+
+<Message type="note">
+As routing complexity increases with each additional VPC in the transitivity chain, transitive peering is limited to four chained VPCs.
+</Message>
+
+## Examples
+
+**Simple peering connection**
+
+With two VPCs, there is no routing transitivity: a single VPC Peering connection is enough for VPC A to communicate with VPC B.
+
+<Lightbox image={peeringSimple} alt="A graphic shows how two different VPCs each create a peering connector, which enables them to communicate over a peering connection." />
+
+**Three peered VPCs without transitivity**
+
+With three chained VPCs, if you only add routes related to the next peer, then VPC A and B can communicate, and VPC B and C can communicate, but VPC A and C cannot.
+
+<Lightbox image={peeringNoTransitivity3} alt="A graphic shows how three different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, but not via a common VPC." />
+
+**Three peered VPCs with transitivity**
+
+To enable VPC A and C to communicate with each other, you must add corresponding routes.
+
+<Lightbox image={peeringTransitivity3} alt="A graphic shows how three different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, and via a common VPC by adding corresponding custom routes." />
+
+**Four peered VPCs without transitivity**
+
+With four chained VPCs, if you only add routes related to the next peer, then each VPC is only able to communicate with its immediate neighbors.
+
+<Lightbox image={peeringNoTransitivity4} alt="A graphic shows how four different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, but not via a common VPC." />
+
+**Four peered VPCs with partial transitivity**
+
+To enable VPC A and D to communicate with each other, you must add corresponding routes. This also includes custom routes in VPC B and C, which must have a path to each extremity of the chain.
+
+<Lightbox image={peeringTransitivity4} alt="A graphic shows how four different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, and via a common VPC by adding corresponding custom routes." />
+
+**Four peered VPCs with full transitivity**
+
+To enable full transitivity and allow any two VPCs of the chain to communicate, you must add additional routes to VPCs A and D.
+
+<Lightbox image={peeringFullTransitivity} alt="A graphic shows how four different VPCs each create a peering connector, which enables them to communicate with any other VPC by adding custom routes to each VPC to enable full transitivity." />