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 for business
    • 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
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All use cases
    • On-premises without redundancy and one cloud network
    • On-premises without redundancy and multiple cloud networks
    • On-premises with redundancy and one cloud network
    • On-premises with redundancy and multiple cloud networks
    • Two separate route instances without on-premises redundancy
    • Even redistribution of on-premise traffic (Active-Active)
    • Prioritizing on-premise traffic based on direction (Active-Standby)
    • Reserving an on-premise connection via a VPN gateway (PRC)
    • 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-premises
    • Organizing network connectivity between a BareMetal private subnet and a Virtual Private Cloud network
    • Establishing network connectivity between a BareMetal private subnet and on-premise resources
    • Changing a set of VPC IP prefixes in a routing instance
  • Access management
  • Release notes

In this article:

  • Changing VPC IP prefixes in a routing instance
  • Contacting support to change IP prefixes in a private connection
  • Contacting support to add IP prefixes to a private connection
  • Contacting support to delete IP prefixes from a private connection
  • Support team's response to your ticket
  1. Tutorials
  2. Changing a set of VPC IP prefixes in a routing instance

Changing a set of VPC IP prefixes in a routing instance

Written by
Yandex Cloud
Updated at July 3, 2025
  • Changing VPC IP prefixes in a routing instance
    • Contacting support to change IP prefixes in a private connection
    • Contacting support to add IP prefixes to a private connection
    • Contacting support to delete IP prefixes from a private connection
    • Support team's response to your ticket

Changing VPC IP prefixes in a routing instanceChanging VPC IP prefixes in a routing instance

To change IP prefixes in a private connection, do the following:

  1. Delete the existing IP prefixes from the private connection.
  2. 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 connectionContacting support to change IP prefixes in a private connection

Follow this request format:

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 connectionContacting support to add IP prefixes to a private connection

Follow this request format:

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 connectionContacting support to delete IP prefixes from a private connection

Follow this request format:

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 ticketSupport 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 IP connectivity issues, contact support for diagnostics and troubleshooting.

Was the article helpful?

Previous
Establishing network connectivity between a BareMetal private subnet and on-premise resources
Next
Access management
© 2025 Direct Cursus Technology L.L.C.