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. Even traffic distribution for route 0.0.0.0/0

Even traffic distribution for route 0.0.0.0/0

Written by
Yandex Cloud
Updated at June 10, 2025

In some cases, e.g., to connect cloud resources to the internet via the customer infrastructure, you need to set up 0.0.0.0/0 route announcement over BGP towards Yandex Cloud.

The flowchart above shows how the traffic from cloud subnets connected to Cloud Interconnect is unconditionally routed to customer edge routers via both points of presence.

Security groups cannot be assigned to resources outside Yandex Cloud; therefore, the correct way to filter traffic is to use IPv4 prefixes rather than links to other security groups.

In this case, the customer can configure traffic filtering rules on customer edge routers before sending it to the internet through their own NAT gateway without using the Yandex Cloud infrastructure.

Was the article helpful?

Previous
Prioritizing a static VPC route over routes from PRC
Next
Prioritizing traffic by direction for route 0.0.0.0/0
© 2025 Direct Cursus Technology L.L.C.