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 for business
    • 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
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All use cases
    • On-premises without redundancy and one cloud network
    • On-premises without redundancy and multiple cloud networks
    • On-premises with redundancy and one cloud network
    • On-premises with redundancy and multiple cloud networks
    • Two separate route instances without on-premises redundancy
    • Even redistribution of on-premise traffic (Active-Active)
    • Prioritizing on-premise traffic based on direction (Active-Standby)
    • Reserving an on-premise connection via a VPN gateway (PRC)
    • 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-premises
  • Access management
  • Release notes
  1. Use cases
  2. Connectivity for two cloud networks

Establishing network connectivity between two or more cloud networks (VPC Stitching)

Written by
Yandex Cloud
Updated at November 10, 2025

Warning

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

The network topology is presented on the diagram in the following configuration:

  • From the Yandex Cloud side, the Routing Instance is connected to by virtual network Net-1 comprised of six subnets: subnet-a1, subnet-a2, subnet-b1, subnet-b2, subnet-d1, and subnet-d2. The information about the subnets' IP prefixes is added to RI.

  • From the Yandex Cloud side, the Routing Instance is connected to by virtual network Net-2 comprised of six subnets: subnet-a3, subnet-a4, subnet-b3, subnet-b4, subnet-d3, and subnet-d4. The information about the subnets' IP prefixes is added to RI.

  • For network connectivity between virtual networks Net-1 and Net-2, a special private vpc-stitching connection is created in the Routing Instance. This private connection terminates on Yandex Cloud network equipment.

  • To achieve network connectivity between virtual networks Net-1 and Net-2 for the vpc-stitching private connection, you need to configure stitching announcements for the CIDRs of the corresponding subnets in virtual networks Net-1 and Net-2.

Important note

Virtual network subnets' own prefixes cannot be used as stitching announcements.

Was the article helpful?

Previous
Prioritizing traffic by direction for route 0.0.0.0/0
Next
Connectivity for two cloud networks and on-premises
© 2025 Direct Cursus Technology L.L.C.