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
    • 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
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All guides
    • Getting information about a routing instance
    • Getting a list of operations in a routing instance
    • Create a routing instance
    • Editing routing instance parameters
    • Updating the list of IP prefixes in a routing instance
    • Deleting IP prefixes from a routing instance
    • Adding a private connection to a routing instance
    • Deleting a private connection from a routing instance
    • Deleting a routing instance
    • Cloud Interconnect tutorials
    • 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. Step-by-step guides
  2. Getting information about a routing instance

Getting information about a routing instance

Written by
Yandex Cloud
Updated at June 10, 2025

Note

You need the cloud-router.viewer role for this operation.

CLI
  1. See the description of the CLI command to get routing instance information:

    yc cloudrouter routing-instance get --help
    
  2. Get a list of Routing Instance objects (RIs) for the specified folder:

    yc cloudrouter routing-instance list --folder-id b1gqf2hjizv2jw****** 
    

    Result:

    +----------------------+--------------------+--------+-----------------------+
    |          ID          |        NAME        | STATUS | PRIVATE CONNECTION ID |
    +----------------------+--------------------+--------+-----------------------+
    | cf3jqdc4gjpxig****** | routing-instance   | ACTIVE | euuiog88zphgsq******, |
    |                      |                    |        | euucr7p47329kq******  |
    +----------------------+--------------------+--------+-----------------------+
    
  3. Get information about the RI by specifying its ID you obtained in the previous step:

    # yc cloudrouter routing-instance get <RI_ID>
    yc cloudrouter routing-instance get cf3jqdc4gjpxig******
    

    Result:

    id: cf3jqdc4gjpxig******
    name: routing-instance
    description: '-'
    folder_id: b1gqf2hjizv2jw******
    region_id: ru-central1
    vpc_info:
      - vpc_network_id: enp0qpdijf4h2p******
        az_infos:
          - manual_info:
              az_id: ru-central1-a
              prefixes:
                - 10.128.11.0/24
                - 10.128.12.0/24
                - 10.128.13.0/24
          - manual_info:
              az_id: ru-central1-b
              prefixes:
                - 10.129.21.0/24
                - 10.129.22.0/24
                - 10.129.23.0/24
          - manual_info:
              az_id: ru-central1-d
              prefixes:
                - 10.130.31.0/24
                - 10.130.32.0/24
                - 10.130.33.0/24
      - vpc_network_id: enp3vifnkc6l4******
        az_infos:
          - manual_info:
              az_id: ru-central1-a
              prefixes:
                - 172.16.1.0/24
                - 172.16.2.0/24
                - 172.16.3.0/24
          - manual_info:
              az_id: ru-central1-b
              prefixes:
                - 172.16.11.0/24
                - 172.16.12.0/24
                - 172.16.13.0/24
          - manual_info:
              az_id: ru-central1-d
              prefixes:
                - 172.16.21.0/24
                - 172.16.22.0/24
                - 172.16.23.0/24
    cic_private_connection_info:
      - cic_private_connection_id: euuiog88zphgsq******
      - cic_private_connection_id: euucr7p47329kq******
    status: ACTIVE
    

    Where:

    • id: Routing instance ID.
    • name: RI name.
    • description: RI description.
    • folder_id: ID of the cloud folder the RI was created in.
    • region_id: ID of the region the RI was created in.
    • vpc_info: Information about virtual networks and their IP prefixes with the prefixes grouped by availability zone. A routing instance may have one or more connected virtual networks.
    • cic_private_connection_info: Information about private connections to this RI.
    • status: RI state. It may take the following values:
      • ACTIVE: RI is active.
      • CREATING: RI is being created.
      • UPDATING: RI is being updated.
      • DELETING: RI is being deleted.

Was the article helpful?

Previous
All guides
Next
Getting a list of operations in a routing instance
© 2025 Direct Cursus Technology L.L.C.