Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All use cases
    • On-prem without redundancy and 1 VPC
    • On-prem without redundancy and multiple VPCs
    • On-prem with redundancy and 1 VPC
    • On-prem with redundancy and multiple VPCs
    • Two separate RIs without on-prem redundancy
    • Even redistribution of on-prem traffic (Active-Active)
    • Prioritizing on-prem traffic based on direction (Active-Standby)
    • On-prem (PRC) connection redundancy via a VPN gateway
    • Prioritizing a static VPC route over routes from PRC
    • Even traffic distribution for route 0.0.0.0/0
    • Prioritizing traffic by direction for route 0.0.0.0/0
    • Connectivity for two cloud networks
    • Connectivity for two cloud networks and on-prem
  • Access management
  • Release notes
  1. Use cases
  2. Connectivity for two cloud networks and on-prem

Establishing network connectivity between two or more cloud networks and on-prem resources (VPC Stitching)

Written by
Yandex Cloud
Updated at July 14, 2025

Warning

This function will only be available if Cloud Interconnect is activated.

Reserved on-prem connection via two private Cloud Interconnect connections to one RI with two or more cloud networks and network connectivity between the cloud networks. This fully-connected topology is called Full Mesh.

The scenario uses the following components:

  • On-Prem client with two local subnets: subnet-c1 and subnet-c2.

  • The On-Prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.

  • Two private connections, prc-m9 and prc-nord, established via two points of presence, M9 and NORD, connect to the Routing Instance in Yandex Cloud.

  • From the Yandex Cloud side, these two virtual networks connect to the Routing Instance:

    • Net-1 comprised of three subnets: subnet-a1, subnet-b1, and subnet-d1.
    • Net-2 comprised of three subnets: subnet-a2, subnet-b2, and subnet-d2.
  • To achieve network connectivity between virtual networks Net-1 and Net-2 for the prc-m9 and prc-nord private connections, you need to configure stitching announcements for the CIDRs of the corresponding subnets in virtual networks Net-1 and Net-2.

Important note

Using the actual subnet prefixes of the virtual networks as stitching announcements is not permitted.

This topology enables network connectivity between:

  • On-Prem subnets and VPC Net-1 subnets.
  • On-Prem subnets and VPC Net-2 subnets.
  • VPC Net-1 and Net-2 subnets.

Note

In case of failure of any of the private connections above, all network traffic will be automatically switched over to the remaining private connection.

Was the article helpful?

Previous
Connectivity for two cloud networks
Next
Organizing network connectivity between a BareMetal private subnet and a Virtual Private Cloud network
© 2025 Direct Cursus Technology L.L.C.