Changing a set of VPC IP prefixes in a routing instance
Written by
Updated at June 10, 2025
Changing VPC IP prefixes in a routing instance
To change IP prefixes in a private connection, do the following:
- Delete the existing IP prefixes from the private connection.
- Add new IP prefixes to the private connection.
To change your private connection IP prefixes, create a new support ticket.
Contacting support to change IP prefixes in a private connection
Follow this request format:
Subject: [CIC] Changing IP prefixes in a private connection.
Request text:
Please change IP prefixes in the private connection
prc_id: cf3qdug4fsf737******
1. Delete the following IP prefixes from the specified networks (vpc_net_id):
vpc_net_id: enpdffqsg8r221******
ru-central1-a: 10.60.192.0/21
ru-central1-b: 10.60.200.0/21, 10.60.220.0/24
ru-central1-d: 10.60.208.0/20
2. Add the following IP prefixes to the specified networks (vpc_net_id):
vpc_net_id: enpdffqsg8r221******
ru-central1-a: 10.60.1.0/24
ru-central1-b: 10.60.4.0/24, 10.60.8.0/24
ru-central1-d: 10.60.10.0/20
vpc_net_id: enpdhpdcp2u748******
ru-central1-a: 10.45.11.0/21, 10.45.100.0/24
ru-central1-b: 10.45.21.0/21
ru-central1-d: 10.45.31.0/20
Where:
vpc_net_id: Yandex Virtual Private Cloud virtual network ID. For each such virtual network, you need to specify IPv4 subnet prefixes grouped by Yandex Cloud availability zones.
Contacting support to add IP prefixes to a private connection
Follow this request format:
Subject: [CIC] Adding IP prefixes to a private connection.
Request text:
Please add IP prefixes to the private connection
prc_id: cf3qdug4fsf737******
Add the following IP prefixes to the specified networks (vpc_net_id):
vpc_net_id: enpdffqsg8r221******
ru-central1-a: 10.60.1.0/24
ru-central1-b: 10.60.4.0/24, 10.60.8.0/24
ru-central1-d: 10.60.10.0/20
vpc_net_id: enpdhpdcp2u748******
ru-central1-a: 10.45.11.0/21, 10.45.100.0/24
ru-central1-b: 10.45.21.0/21
ru-central1-d: 10.45.31.0/20
Where:
vpc_net_id: Yandex Virtual Private Cloud virtual network ID. For each such virtual network, you need to specify IPv4 subnet prefixes grouped by Yandex Cloud availability zones.
Contacting support to delete IP prefixes from a private connection
Follow this request format:
Subject: [CIC] Deleting IP prefixes from a private connection.
Request text:
Please delete IP prefixes from the private connection
prc_id: cf3qdug4fsf737******
1. Delete the following IP prefixes from the specified networks (vpc_net_id):
vpc_net_id: enpdffqsg8r221******
ru-central1-a: 10.60.192.0/21
ru-central1-b: 10.60.200.0/21, 10.60.220.0/24
ru-central1-d: 10.60.208.0/20
vpc_net_id: enpdffqsg8r221******
ru-central1-a: 10.60.1.0/24
ru-central1-b: 10.60.4.0/24, 10.60.8.0/24
ru-central1-d: 10.60.10.0/20
Where:
vpc_net_id: Yandex Virtual Private Cloud virtual network ID. For each such virtual network, you need to specify IPv4 subnet prefixes grouped by Yandex Cloud availability zones.
Support team's response to your ticket
Here is an example of the support response to a request for changing private connection IP prefixes (for reference only):
Requested changes to the private connection IP prefixes have been accepted.
prc_id: cf3qdug4fsf737******
Note
Changing IP prefixes may take up to two business days. You will be notified once the process is completed.
If there are any connectivity issues, contact support for diagnostics and troubleshooting.