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 Virtual Private Cloud
  • Getting started
    • All guides
      • Creating a static route
      • Creating and setting up a NAT gateway
      • Getting information about a NAT gateway
      • Moving a route table between folders
      • Getting information about a route table
      • Moving a NAT gateway between folders
      • Deleting a route table
      • Deleting a NAT gateway
    • Enabling a software-accelerated network
    • Chart of network connections
    • Viewing operations with resources
  • DDoS Protection
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Disassociating a route table from a subnet
  • Deleting a route table
  1. Step-by-step guides
  2. Static routing
  3. Deleting a route table

Deleting a route table

Written by
Yandex Cloud
Updated at July 14, 2025
  • Disassociating a route table from a subnet
  • Deleting a route table

If you no longer need the route table, you can delete it. Before deleting a table, disassociate it from all subnets it is associated with.

Disassociating a route table from a subnetDisassociating a route table from a subnet

Management console
CLI
Terraform
API
  1. In the management console, go to the folder where you need to disassociate a route table.

  2. In the list of services, select Virtual Private Cloud.

  3. Go to the cloud network the route table belongs to.

    Note

    If you do not know which network the route table belongs to, in the left-hand panel, select Routing tables. This will open a list of route tables. Find the network you need in the Network column next to the route table name. To view the cloud network, click its name.

  4. In the list of subnets, find the subnet associated with the route table.

  5. Disassociate the route table from the subnet using any of these methods:

    • In the row with subnet information, click next to the route table name.
    • In the row with subnet information, click and select Edit. In the window that opens, click in the row with the route table name and save the changes.
    • Open the subnet information and click next to the route table name.
    • Open the subnet information and click Edit in the top-right corner. In the window that opens, click in the row with the route table name and save the changes.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To disassociate a route table from a subnet:

  1. View the description of the CLI command for updating subnet parameters:

    yc vpc subnet update --help
    
  2. Get the name or ID of the subnet the route table is associated with:

    yc vpc subnet list
    

    Result:

    +----------------------+----------------------------+----------------------+----------------------+---------------+-----------------+
    |          ID          |            NAME            |      NETWORK ID      |    ROUTE TABLE ID    |     ZONE      |      RANGE      |
    +----------------------+----------------------------+----------------------+----------------------+---------------+-----------------+
    | e9b4vdgv0v1n******** | default-ru-central1-a      | enptgj64mv2r******** |                      | ru-central1-a | [10.128.0.0/24] |
    | e2lp11c4o77d******** | default-ru-central1-b      | enptgj64mv2r******** | enpcaaqahk3c******** | ru-central1-b | [10.129.0.0/24] |
    +----------------------+----------------------------+----------------------+----------------------+---------------+-----------------+
    
    
  3. Disassociate the route table from the subnet:

    yc vpc subnet update <subnet_name_or_ID> --disassociate-route-table
    

    Use either the --id or --name parameter.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

To disassociate a route table from a subnet in the infrastructure created in Terraform:

  1. Open the Terraform configuration file and find the fragment with the description of the subnet associated with the route table:

    Example of a subnet description in the Terraform configuration
    ...
    resource "yandex_vpc_subnet" "subnet" {
      folder_id      = "<user_folder_ID>"
      name           = "<subnet_name>"
      v4_cidr_blocks = ["10.20.30.0/24"]
      zone           = "<availability_zone>"
      network_id     = "<subnet_ID>"
      route_table_id = "<route_table_ID>"
    }
    ...
    
  2. Delete the route table description string from this fragment:

    route_table_id = "<route_table_ID>"
    
  3. In the command line, go to the directory with the Terraform configuration file.

  4. Check the configuration using this command:

    terraform validate
    

    If the configuration is correct, you will get this message:

    Success! The configuration is valid.
    
  5. Run this command:

    terraform plan
    

    You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will point them out.

  6. Apply the changes:

    terraform apply
    
  7. Type yes and press Enter to confirm changes.

    You can check the updates using the management console or this CLI command:

    yc vpc subnet get <subnet_name_or_ID>
    

    Use either the --id or --name parameter.

To disassociate a route table from a subnet, use the update REST API method for the Subnet resource or the SubnetService/Update gRPC API call, and provide an empty string in the following request parameter:

  • routeTableId: For REST API
  • route_table_id: For gRPC API

Warning

The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

Deleting a route tableDeleting a route table

Warning

Before deleting a table, disassociate it from all subnets it is associated with.

Management console
CLI
Terraform
API

To delete a route table:

  1. In the management console, go to the folder where you need to delete a route table.
  2. In the list of services, select Virtual Private Cloud.
  3. In the left-hand panel, select Routing tables.
  4. Click in the row with the table name and select Delete.
  5. In the window that opens, click Delete.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To delete a route table:

  1. View the description of the CLI command for deleting a route table:

    yc vpc route-table delete --help
    
  2. Get the name or ID of the route table to delete:

    yc vpc route-table list
    

    Result:

    +----------------------+---------+-------------+----------------------+
    |          ID          |  NAME   | DESCRIPTION |      NETWORK-ID      |
    +----------------------+---------+-------------+----------------------+
    | enpd3s8svtkd******** | table-1 |             | enptgj64mv2r******** |
    +----------------------+---------+-------------+----------------------+
    
  3. Delete the route table:

    yc vpc route-table delete <route_table_name_or_ID>
    

    Use either the --id or --name parameter.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

To delete a route table created using Terraform:

  1. Open the Terraform configuration file and delete the route table description fragment.

    Example of a route table description in the Terraform configuration
    ...
    resource "yandex_vpc_route_table" "route_table" {
      folder_id  = "<user_folder_ID>"
      name       = "<route_table_name>"
      network_id = "<network_ID>"
      static_route {
        destination_prefix = "10.2.0.0/16"
        next_hop_address   = "172.16.10.10"
      }
    }
    ...
    
  2. In the command line, navigate to the directory with the Terraform configuration file.

  3. Check the configuration using this command:

    terraform validate
    

    If the configuration is correct, you will get this message:

    Success! The configuration is valid.
    
  4. Run this command:

    terraform plan
    

    You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will point them out.

  5. Apply the changes:

    terraform apply
    
  6. Type yes and press Enter to confirm changes.

    You can check updates in the management console or using this CLI command:

    yc vpc subnet list
    

To delete a route table, use the delete REST API method for the RouteTable resource or the RouteTableService/Delete gRPC API call, and provide the ID of the route table you want to delete in the following request parameter:

  • routeTableID: For REST API
  • route_table_id: For gRPC API

To get the route table ID, use the list REST API method for the RouteTable resource or the RouteTableService/List gRPC API call, and provide the folder ID in the following request parameter:

  • folderID: For REST API
  • folder_id: For gRPC API

Was the article helpful?

Previous
Moving a NAT gateway between folders
Next
Deleting a NAT gateway
© 2025 Direct Cursus Technology L.L.C.