[Yandex Cloud documentation](../../index.md) > [Yandex Cloud Router](../index.md) > [Step-by-step guides](index.md) > Managing networks and IP prefixes in a routing instance

# Managing networks and IP prefixes in a routing instance

## Updating networks and IP prefixes in a routing instance {#update-networks}

You can use the `yc cloudrouter routing-instance update-networks` Yandex Cloud CLI [command](../cli-ref/routing-instance/update-networks.md) to simultaneously manage multiple [announced IP prefixes](../concepts/announces.md) of Yandex Virtual Private Cloud cloud [networks](../../vpc/concepts/network.md#network) added to a [routing instance](../concepts/routing-instance.md), as well as add new networks to a routing instance and delete the existing ones. 

{% note info %}

To manage networks and IP prefixes in a routing instance, you need the `cloud-router.editor` [role](../security/index.md#cloudrouter-editor).

{% endnote %}

### Adding a cloud network to a routing instance {#add-network}

{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  1. View the description of the command for managing networks and IP prefixes in a routing instance:
     
     ```bash
     yc cloudrouter routing-instance update-networks --help
     ```
  1. View the list of all routing instances in the folder:
     
     ```bash
     yc cloudrouter routing-instance list \
       --folder-id <folder_ID>
     ```
     
     Where `--folder-id` is the [ID of the folder](../../resource-manager/operations/folder/get-id.md) containing the routing instance.
     
     Result:
     
     ```text
     +----------------------+------+----------+--------------------------------+
     |          ID          | NAME |  STATUS  |     PRIVATE CONNECTION ID      |
     +----------------------+------+----------+--------------------------------+
     | c3lgk007olse******** | ri1  | UPDATING | cf3or586ln29********,          |
     |                      |      |          | cf3uj9uph7b6********           |
     +----------------------+------+----------+--------------------------------+
     ```
  1. Get information about a routing instance by specifying its ID:
     
     ```bash
     yc cloudrouter routing-instance get c3lgk007olse******** \
       --folder-id <folder_ID>
     ```
     
     Result:
     
     
     ```text
     id: c3lgk007olse********
     name: ri1
     description: Routing instance 1
     folder_id: b1gt6g8ht345********
     region_id: ru-central1
     vpc_info:
       - vpc_network_id: enpcfncr6uld********
         az_infos:
           - manual_info:
               az_id: ru-central1-d
               prefixes:
                 - 192.168.7.0/24
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.2.0/24
           - manual_info:
               az_id: ru-central1-b
               prefixes:
                 - 192.168.15.0/24
       - vpc_network_id: enpt8ok6snlp********
         az_infos:
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.45.0/24
                 - 192.168.46.0/24
     cic_private_connection_info:
       - cic_private_connection_id: cf3or586ln29********
       - cic_private_connection_id: cf3uj9uph7b6********
     status: UPDATING
     created_at: "2025-12-23T07:30:19Z"
     ```
  1. Add a new network with an announced IP prefix to the routing instance by specifying this network's [ID](../../vpc/operations/network-get-info.md) under `id` in the `--add-vpc-net` parameter:

      ```bash
      yc cloudrouter routing-instance update-networks \
        --folder-id <folder_ID> \
        --id c3lgk007olse******** \
        --add-vpc-net id=enpvt41bh5gk********,zone=ru-central1-a,ipv4-prefixes=192.168.100.0/24,192.168.101.0/24 \
        --async
      ```

      Result:

      ```text
      id: foku4jbrp07i********
      description: routing instance update prefix mask
      created_at: "2025-12-23T08:35:04.852963002Z"
      created_by: ajeol2afu1js********
      modified_at: "2025-12-23T08:35:04.852963002Z"
      metadata:
        '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
        routing_instance_id: c3lgk007olse********
      ```

      Where:
      
      * `id`: ID of the operation performed with a routing instance.
      * `description`: Description of the operation in progress.
      * `created_by`: ID of the subject running the operation.
      * `async`: Running the operation in asynchronous mode. We recommend using this mode for all operations that modify your resources.

  1. Wait for the operation to [complete](../../cli/cli-ref/operation/cli-ref/get.md) and make sure the routing instance configuration has been updated:

      ```bash
      yc cloudrouter routing-instance get c3lgk007olse******** \
        --folder-id <folder_ID>
      ```

      Result:

      
      ```text
      id: c3lgk007olse********
      name: ri1
      description: Routing instance 1
      folder_id: b1gt6g8ht345********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: enpcfncr6uldme5e5929
          az_infos:
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 192.168.7.0/24
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.2.0/24
            - manual_info:
                az_id: ru-central1-b
                prefixes:
                  - 192.168.15.0/24
        - vpc_network_id: enpt8ok6snlp********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.45.0/24
                  - 192.168.46.0/24
        - vpc_network_id: enpvt41bh5gk********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.100.0/24
                  - 192.168.101.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3or586ln29********
        - cic_private_connection_id: cf3uj9uph7b6********
      status: ACTIVE
      created_at: "2025-12-23T08:35:07Z"
      ```


      * `id`: Routing instance ID.
      * `name`: Routing instance name.
      * `description`: Routing instance description.
      * `folder_id`: ID of the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) the routing instance was created in.
      * `region_id`: Region of the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) the routing instance was created in.
      * `vpc_info`: List of IP prefixes by [availability zone](../../overview/concepts/geo-scope.md). Prefixes are shown separately for each availability zone.
      * `cic_private_connection_info`: List of private connections connected to the routing instance.
      * `status`: Resource state. The target state is `ACTIVE`. When being updated, it may be in the `UPDATING` state.
      * `created_at`: Date and time of resource creation.

{% endlist %}

### Deleting an existing cloud network from a routing instance {#remove-network}

{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  1. View the description of the command for managing networks and IP prefixes in a routing instance:
     
     ```bash
     yc cloudrouter routing-instance update-networks --help
     ```
  1. View the list of all routing instances in the folder:
     
     ```bash
     yc cloudrouter routing-instance list \
       --folder-id <folder_ID>
     ```
     
     Where `--folder-id` is the [ID of the folder](../../resource-manager/operations/folder/get-id.md) containing the routing instance.
     
     Result:
     
     ```text
     +----------------------+------+----------+--------------------------------+
     |          ID          | NAME |  STATUS  |     PRIVATE CONNECTION ID      |
     +----------------------+------+----------+--------------------------------+
     | c3lgk007olse******** | ri1  | UPDATING | cf3or586ln29********,          |
     |                      |      |          | cf3uj9uph7b6********           |
     +----------------------+------+----------+--------------------------------+
     ```
  1. Get information about a routing instance by specifying its ID:
     
     ```bash
     yc cloudrouter routing-instance get c3lgk007olse******** \
       --folder-id <folder_ID>
     ```
     
     Result:
     
     
     ```text
     id: c3lgk007olse********
     name: ri1
     description: Routing instance 1
     folder_id: b1gt6g8ht345********
     region_id: ru-central1
     vpc_info:
       - vpc_network_id: enpcfncr6uld********
         az_infos:
           - manual_info:
               az_id: ru-central1-d
               prefixes:
                 - 192.168.7.0/24
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.2.0/24
           - manual_info:
               az_id: ru-central1-b
               prefixes:
                 - 192.168.15.0/24
       - vpc_network_id: enpt8ok6snlp********
         az_infos:
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.45.0/24
                 - 192.168.46.0/24
     cic_private_connection_info:
       - cic_private_connection_id: cf3or586ln29********
       - cic_private_connection_id: cf3uj9uph7b6********
     status: UPDATING
     created_at: "2025-12-23T07:30:19Z"
     ```
  1. Delete an existing network from the routing instance:

      ```bash
      yc cloudrouter routing-instance update-networks \
        --folder-id <folder_ID> \
        --id c3lgk007olse******** \
        --delete-vpc-net-id id=enpt8ok6snlp******** \
        --async
      ```

      Result:

      ```text
      id: fokg66rcqie1********
      description: routing instance update prefix mask
      created_at: "2025-12-23T08:53:09.626102995Z"
      created_by: ajeol2afu1js********
      modified_at: "2025-12-23T08:53:09.626102995Z"
      metadata:
        '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
        routing_instance_id: c3lgk007olse********
      ```

      Where:
      
      * `id`: ID of the operation performed with a routing instance.
      * `description`: Description of the operation in progress.
      * `created_by`: ID of the subject running the operation.
      * `async`: Running the operation in asynchronous mode. We recommend using this mode for all operations that modify your resources.

  1. Wait for the operation to [complete](../../cli/cli-ref/operation/cli-ref/get.md) and make sure the routing instance configuration has been updated:

      ```bash
      yc cloudrouter routing-instance get c3lgk007olse******** \
        --folder-id <folder_ID>
      ```

      Result:

      
      ```text
      id: c3lgk007olse********
      name: ri1
      description: Routing instance 1
      folder_id: b1gt6g8ht345********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: enpcfncr6uldme5e5929
          az_infos:
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 192.168.7.0/24
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.2.0/24
            - manual_info:
                az_id: ru-central1-b
                prefixes:
                  - 192.168.15.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3or586ln29********
        - cic_private_connection_id: cf3uj9uph7b6********
      status: ACTIVE
      created_at: "2025-12-23T08:35:07Z"
      ```


      * `id`: Routing instance ID.
      * `name`: Routing instance name.
      * `description`: Routing instance description.
      * `folder_id`: ID of the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) the routing instance was created in.
      * `region_id`: Region of the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) the routing instance was created in.
      * `vpc_info`: List of IP prefixes by [availability zone](../../overview/concepts/geo-scope.md). Prefixes are shown separately for each availability zone.
      * `cic_private_connection_info`: List of private connections connected to the routing instance.
      * `status`: Resource state. The target state is `ACTIVE`. When being updated, it may be in the `UPDATING` state.
      * `created_at`: Date and time of resource creation.

{% endlist %}

### Updating IP prefixes of existing cloud networks in a routing instance {#update-prefixes}

{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  1. View the description of the command for managing networks and IP prefixes in a routing instance:
     
     ```bash
     yc cloudrouter routing-instance update-networks --help
     ```
  1. View the list of all routing instances in the folder:
     
     ```bash
     yc cloudrouter routing-instance list \
       --folder-id <folder_ID>
     ```
     
     Where `--folder-id` is the [ID of the folder](../../resource-manager/operations/folder/get-id.md) containing the routing instance.
     
     Result:
     
     ```text
     +----------------------+------+----------+--------------------------------+
     |          ID          | NAME |  STATUS  |     PRIVATE CONNECTION ID      |
     +----------------------+------+----------+--------------------------------+
     | c3lgk007olse******** | ri1  | UPDATING | cf3or586ln29********,          |
     |                      |      |          | cf3uj9uph7b6********           |
     +----------------------+------+----------+--------------------------------+
     ```
  1. Get information about a routing instance by specifying its ID:
     
     ```bash
     yc cloudrouter routing-instance get c3lgk007olse******** \
       --folder-id <folder_ID>
     ```
     
     Result:
     
     
     ```text
     id: c3lgk007olse********
     name: ri1
     description: Routing instance 1
     folder_id: b1gt6g8ht345********
     region_id: ru-central1
     vpc_info:
       - vpc_network_id: enpcfncr6uld********
         az_infos:
           - manual_info:
               az_id: ru-central1-d
               prefixes:
                 - 192.168.7.0/24
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.2.0/24
           - manual_info:
               az_id: ru-central1-b
               prefixes:
                 - 192.168.15.0/24
       - vpc_network_id: enpt8ok6snlp********
         az_infos:
           - manual_info:
               az_id: ru-central1-a
               prefixes:
                 - 192.168.45.0/24
                 - 192.168.46.0/24
     cic_private_connection_info:
       - cic_private_connection_id: cf3or586ln29********
       - cic_private_connection_id: cf3uj9uph7b6********
     status: UPDATING
     created_at: "2025-12-23T07:30:19Z"
     ```
  1. Update the announced IP prefixes in the routing instance:

      
      ```bash
      yc cloudrouter routing-instance update-networks \
        --folder-id <folder_ID> \
        --id c3lgk007olse******** \
        --update-vpc-net id=enpcfncr6uld********,zone=ru-central1-a,ipv4-prefixes=192.168.2.0/28 \
        --update-vpc-net id=enpcfncr6uld********,zone=ru-central1-b,ipv4-prefixes=192.168.15.0/24 \
        --update-vpc-net id=enpcfncr6uld********,zone=ru-central1-d,ipv4-prefixes=192.168.7.0/24 \
        --update-vpc-net id=enpt8ok6snlp********,zone=ru-central1-d,ipv4-prefixes=192.168.47.0/28 \
        --async
      ```


      Result:

      ```text
      id: fokr80vgdskp********
      description: routing instance update prefix mask
      created_at: "2025-12-23T09:56:40.259684884Z"
      created_by: ajeol2afu1js********
      modified_at: "2025-12-23T09:56:40.259684884Z"
      metadata:
        '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
        routing_instance_id: c3lgk007olse********
      ```

      Where:
      
      * `id`: ID of the operation performed with a routing instance.
      * `description`: Description of the operation in progress.
      * `created_by`: ID of the subject running the operation.
      * `async`: Running the operation in asynchronous mode. We recommend using this mode for all operations that modify your resources.

  1. Wait for the operation to [complete](../../cli/cli-ref/operation/cli-ref/get.md) and make sure the routing instance configuration has been updated:

      ```bash
      yc cloudrouter routing-instance get c3lgk007olse******** \
        --folder-id <folder_ID>
      ```

      Result:

      
      ```text
      id: c3lgk007olse********
      name: ri1
      description: Routing instance 1
      folder_id: b1gt6g8ht345********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: enpcfncr6uld********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.2.0/28
            - manual_info:
                az_id: ru-central1-b
                prefixes:
                  - 192.168.15.0/24
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 192.168.7.0/24
        - vpc_network_id: enpt8ok6snlp********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 192.168.47.0/28
      cic_private_connection_info:
        - cic_private_connection_id: cf3or586ln29********
        - cic_private_connection_id: cf3uj9uph7b6********
      status: ACTIVE
      created_at: "2025-12-23T10:46:55Z"
      ```


      * `id`: Routing instance ID.
      * `name`: Routing instance name.
      * `description`: Routing instance description.
      * `folder_id`: ID of the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) the routing instance was created in.
      * `region_id`: Region of the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) the routing instance was created in.
      * `vpc_info`: List of IP prefixes by [availability zone](../../overview/concepts/geo-scope.md). Prefixes are shown separately for each availability zone.
      * `cic_private_connection_info`: List of private connections connected to the routing instance.
      * `status`: Resource state. The target state is `ACTIVE`. When being updated, it may be in the `UPDATING` state.
      * `created_at`: Date and time of resource creation.

{% endlist %}

## Adding IP prefixes to a routing instance {#upsert-prefixes}

You can use the `yc cloudrouter routing-instance upsert-prefixes` Yandex Cloud CLI [command](../cli-ref/routing-instance/upsert-prefixes.md) to [announce new IP prefixes](../concepts/announces.md) in a routing instance.

{% note tip %}

If you need to add new IP prefixes to a routing instance while also deleting all or some of its existing prefixes, [use](#update-networks) the `yc cloudrouter routing-instance update-networks` command.

{% endnote %}

{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  1. See the description of the CLI command for updating a list of IP prefixes in a [routing instance](../concepts/routing-instance.md):

      ```bash
      yc cloudrouter routing-instance upsert-prefixes --help
      ```

  1. View the routing instance configuration and the list of IP prefixes:

      ```bash
      yc cloudrouter routing-instance get c3l871dpin4f******** \
        --folder-id <folder_ID>
      ```

      Where `--folder-id` is the [ID of the folder](../../resource-manager/operations/folder/get-id.md) containing the routing instance.

      Result:

      ```text
      id: c3l871dpin4f********
      name: ri1
      description: Routing instance 1
      folder_id: b1gqfjiz2wda********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: c64ckjtr7b3l********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 10.128.0.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3td2nufvr5********
      status: ACTIVE
      created_at: "2025-03-19T13:35:56Z"
      ```
  1. Add more prefixes to the routing instance IP prefix list:

      {% note info %}
      
      To manage networks and IP prefixes in a routing instance, you need the `cloud-router.editor` [role](../security/index.md#cloudrouter-editor).
      
      {% endnote %}

      
      ```bash
      yc cloudrouter routing-instance upsert-prefixes c3l871dpin4f******** \
        --folder-id <folder_ID> \
        --vpc-net id=c64ckjtr7b3l********,zone=ru-central1-b,ipv4-prefixes=10.129.0.0/24 \
        --vpc-net id=c64ckjtr7b3l********,zone=ru-central1-d,ipv4-prefixes=172.16.1.0/24 \
        --async
      ```


      Result:

      ```text
      id: al457njn6pj1********
      description: routing instance upsert prefixes
      created_at: "2025-03-24T15:24:15.817401507Z"
      created_by: bfbudv7dfn22********
      modified_at: "2025-03-24T15:24:15.817401507Z"
      metadata:
        '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
        routing_instance_id: c3l871dpin4f********
      ```

      Where:
      
      * `id`: ID of the operation performed with a routing instance.
      * `description`: Description of the operation in progress.
      * `created_by`: ID of the subject running the operation.
      * `async`: Running the operation in asynchronous mode. We recommend using this mode for all operations that modify your resources.

  1. Wait for the operation to [complete](../../cli/cli-ref/operation/cli-ref/get.md) and make sure the routing instance configuration has been updated:

      ```bash
      yc cloudrouter routing-instance get c3l871dpin4f******** \
        --folder-id <folder_ID>
      ```

      Result:

      
      ```
      id: c3l871dpin4f********
      name: ri1
      description: Routing instance 1
      folder_id: b1gqfjiz2wda********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: c64ckjtr7b3l********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 10.128.0.0/24
            - manual_info:
                az_id: ru-central1-b
                prefixes:
                  - 10.129.0.0/24
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 172.16.1.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3td2nufvr5********
      status: ACTIVE
      created_at: "2025-03-19T13:35:56Z"
      ```


      Where:

      * `id`: Routing instance ID.
      * `name`: Routing instance name.
      * `description`: Routing instance description.
      * `folder_id`: ID of the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) the routing instance was created in.
      * `region_id`: Region of the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) the routing instance was created in.
      * `vpc_info`: List of IP prefixes by [availability zone](../../overview/concepts/geo-scope.md). Prefixes are shown separately for each availability zone.
      * `cic_private_connection_info`: List of private connections connected to the routing instance.
      * `status`: Resource state. The target state is `ACTIVE`. When being updated, it may be in the `UPDATING` state.
      * `created_at`: Date and time of resource creation.

{% endlist %}

## Deleting IP prefixes from a routing instance {#remove-prefixes}

You can use the `yc cloudrouter routing-instance remove-prefixes` Yandex Cloud CLI [command](../cli-ref/routing-instance/remove-prefixes.md) to delete [announced IP prefixes](../concepts/announces.md) from a routing instance.

{% note tip %}

If you need to delete existing IP prefixes from a routing instance while also adding new prefixes to it, [use](#update-networks) the `yc cloudrouter routing-instance update-networks` command.

{% endnote %}

{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  1. See the description of the CLI command for deleting IP prefixes from a [routing instance](../concepts/routing-instance.md):

      ```bash
      yc cloudrouter routing-instance remove-prefixes --help
      ```

  1. View the routing instance configuration and the list of IP prefixes:

      ```bash
      yc cloudrouter routing-instance get c3l871dpin4f******** \
        --folder-id <folder_ID>
      ```

      Where `--folder-id` is the [ID of the folder](../../resource-manager/operations/folder/get-id.md) containing the routing instance.

      Result:

      
      ```text
      id: c3l871dpin4f********
      name: ri1
      description: Routing instance 1
      folder_id: b1gqfjiz2wda********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: c64ckjtr7b3l********
          az_infos:
            - manual_info:
                az_id: ru-central1-a
                prefixes:
                  - 10.128.0.0/24
            - manual_info:
                az_id: ru-central1-b
                prefixes:
                  - 10.129.0.0/24
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 172.16.1.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3td2nufvr5********
      status: ACTIVE
      created_at: "2025-03-19T13:35:56Z"
      ```


  1. Delete IP prefixes from the routing instance:

      {% note info %}
      
      To manage networks and IP prefixes in a routing instance, you need the `cloud-router.editor` [role](../security/index.md#cloudrouter-editor).
      
      {% endnote %}

      
      ```bash
      yc cloudrouter routing-instance remove-prefixes c3l871dpin4f******** \
        --folder-id <folder_ID> \
        --vpc-net id=c64ckjtr7b3l********,zone=ru-central1-b,ipv4-prefixes=10.128.0.0/24 \
        --vpc-net id=c64ckjtr7b3l********,zone=ru-central1-d,ipv4-prefixes=10.129.0.0/24 \
        --async
      ```


      Result:

      ```text
      id: al457njn6pj1********
      description: routing instance remove prefixes
      created_at: "2025-03-24T15:24:15.817401507Z"
      created_by: bfbudv7dfn22********
      modified_at: "2025-03-24T15:24:15.817401507Z"
      metadata:
        '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
        routing_instance_id: c3l871dpin4f********
      ```

      Where:
      
      * `id`: ID of the operation performed with a routing instance.
      * `description`: Description of the operation in progress.
      * `created_by`: ID of the subject running the operation.
      * `async`: Running the operation in asynchronous mode. We recommend using this mode for all operations that modify your resources.

  1. Wait for the operation to [complete](../../cli/cli-ref/operation/cli-ref/get.md) and make sure the routing instance configuration has been updated:

      ```bash
      yc cloudrouter routing-instance get c3l871dpin4f******** \
        --folder-id <folder_ID>
      ```

      Result:

      
      ```text
      id: c3l871dpin4f********
      name: ri1
      description: Routing instance 1
      folder_id: b1gqfjiz2wda********
      region_id: ru-central1
      vpc_info:
        - vpc_network_id: c64ckjtr7b3l********
          az_infos:
            - manual_info:
                az_id: ru-central1-d
                prefixes:
                  - 172.16.1.0/24
      cic_private_connection_info:
        - cic_private_connection_id: cf3td2nufvr5********
      status: ACTIVE
      created_at: "2025-03-19T13:35:56Z"
      ```


      Where:

      * `id`: Routing instance ID.
      * `name`: Routing instance name.
      * `description`: Routing instance description.
      * `folder_id`: ID of the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) the routing instance was created in.
      * `region_id`: Region of the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) the routing instance was created in.
      * `vpc_info`: List of IP prefixes by [availability zone](../../overview/concepts/geo-scope.md). Prefixes are shown separately for each availability zone.
      * `cic_private_connection_info`: List of private connections connected to the routing instance.
      * `status`: Resource state. The target state is `ACTIVE`. When being updated, it may be in the `UPDATING` state.
      * `created_at`: Date and time of resource creation.

{% endlist %}