[Yandex Cloud documentation](../../index.md) > [Yandex Cloud Router](../index.md) > [Use cases](index.md) > On-premises without redundancy and multiple cloud networks

# On-prem without redundancy and multiple VPCs

Non-reserved on-prem connection via a single Cloud Interconnect [private connection](../../vpc/concepts/network.md) to a single `RI` with two or more [cloud networks](../../interconnect/concepts/priv-con.md) without network connectivity between them.

![ri-topology-2](../../_assets/cloud-router/ri-topology-2.svg)

The network topology is presented on the diagram in the following configuration:

* `On-Prem` client with two local subnets: `subnet-c1` and `subnet-c2`.
* The on-prem network hardware is connected to the Yandex Cloud network hardware using [Cloud Interconnect](../../interconnect/concepts/index.md).
* The `prc-m9` [private connection](../../interconnect/concepts/priv-con.md) via the `M9` [point of presence](../../interconnect/concepts/pops.md) connects to `RI` in Yandex Cloud.
* Two virtual networks connect to `RI` on the Yandex Cloud side:
  * `Net-1` comprised of three subnets: `subnet-a1`, `subnet-b1`, and `subnet-d1`.
  * `Net-2` comprised of three subnets: `subnet-a2`, `subnet-b2`, and `subnet-d2`.

This topology enables network connectivity between:

* `On-Prem` subnets and `Net-1` VPC subnets `subnet-a1`, `subnet-b1`, and `subnet-d1`.
* `On-Prem` subnets and `Net-2` VPC subnets `subnet-a2`, `subnet-b2`, and `subnet-d2`.

This topology enables network connectivity between `Net-1` and `Net-2` virtual networks subnets.