Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • 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
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
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
    • VPC Stithcing. Connectivity for two cloud networks
    • VPC Stitching. Connectivity for two cloud networks and on-prem
  • Access management
  • Release notes
  1. Use cases
  2. Even redistribution of on-prem traffic (Active-Active)

Even redistribution of on-prem traffic (Active-Active)

Written by
Yandex Cloud
Updated at June 10, 2025

The example below shows load balancing using two private connections set up through two points of presence.

Customer edge routers announce the 10.0.0.0/8 prefix from the customer infrastructure over BGP through two points of presence towards Yandex Cloud. Yandex Cloud will then use ECMP load balancing to distribute traffic between those points of presence.

Note that this balancing mode can create traffic asymmetry. For example, a request originating from the customer infrastructure to cloud resources could arrive through the M9 point of presence, while the response will be sent through NORD.

While Yandex Cloud hardware allows and correctly handles traffic asymmetry, specific types of equipment within the customer infrastructure, such as firewalls, may experience issues with asymmetric traffic patterns.

To allow asymmetric traffic from Yandex Cloud, disable RPF on the network elements handling traffic in the customer infrastructure. This will enable you to use all active Cloud Interconnect links with a redundant connectivity through two or more points of presence.

Was the article helpful?

Previous
Two separate RIs without on-prem redundancy
Next
Prioritizing on-prem traffic based on direction (Active-Standby)
Yandex project
© 2025 Yandex.Cloud LLC