Virtual Networks limits
Find the quotas that networks, subnets, ports, and routers count against, and the fixed limits for names, address blocks, gateways, and static routes.
Virtual Networks has two kinds of limits:
- Quotas cap how many networks, subnets, ports, and routers you can have: the subscription's quota and the project's allocation. You can request an increase.
- Product limits are fixed rules for names, address blocks, and routes. They can't be changed.
Quotas
| Quota | What counts | Adjustable? | Notes |
|---|---|---|---|
| Networks | Each network | Yes | Quota ID q-networks. Checked when you create a network. |
| Subnets | Each subnet | Yes | Quota ID q-subnets. |
| Ports | Each port | Yes | Quota ID q-ports. |
| Routers | Each router | Yes | Quota ID q-routers. |
When you create a network, the platform checks the Networks quota of the subscription first. If the request would exceed it, it's refused, and nothing is created. The message names the quota ID, for example "Request an increase for q-networks to continue."
Floating IPs and security groups have their own quotas. See Floating IPs and Security Groups.
Project allocations
Your subscription's quota is shared between its projects. Each project can use only its allocation, the share of the quota that's assigned to it, and the cloud enforces that allocation for networks, subnets, ports, and routers.
A new project starts with an allocation of up to 5 networks, 10 subnets, 50 ports, and 2 routers, as far as the subscription's limits have room left.
A create that fits the subscription's quota can still fail in a project whose allocation is used up. Free up resources in the project, or raise its allocation.
The quota page counts your networks and routers. It doesn't count subnets and ports, but the cloud enforces those quotas all the same.
To see your quotas and allocations, move allocation between projects, or request an increase, see Quotas.
Product limits
| Resource | Limit | Adjustable? | Notes |
|---|---|---|---|
| Network name | 1–63 characters | No | Lowercase letters, numbers, and hyphens. Unique within the project. |
| Router name | 1–63 characters | No | Lowercase letters, numbers, and hyphens. Unique within the project. |
| Subnet name | 1–255 characters | No | Unique within the network. No leading or trailing spaces, control characters, or characters outside the Basic Multilingual Plane, such as most emoji. |
| Port name | 1–60 characters | No | Lowercase letters, numbers, and hyphens. |
| Tag key of a network | 1–128 characters | No | |
| Tag value of a network | Up to 256 characters | No | |
| Subnet address block | A private IPv4 block inside 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 | No | When you create a subnet in the console or with the REST API. The console doesn't change a subnet's block after creation. |
| Prefix length of the first subnet in the create-network form | Not /31 or /32 | No | Such a block leaves no address for the gateway. |
| Subnet gateway | One IPv4 address, or none | No | Inside the block when you add the subnet. Without your own address, the first usable address of the block. |
| Host route | An IPv4 destination block and an IPv4 next hop | No | |
| Allocation pool range | An IPv4 start and end address inside the block | No | The end can't come before the start. |
| Fixed IP addresses of a port that you create in the console | 1 | No | |
| Attachments of one subnet to one router | 1 | No | |
| External gateways per router | 1 | No | In the console, the platform picks the external network. |
| Static routes per destination on one router | 1 | No | |
| Static route destination | A block that starts at its first address | No | For example, 10.20.0.0/16. |
| Static route next hop | An address that the router reaches through an attached subnet or its external gateway's network | No | For a next hop in one of your subnets, attach that subnet first. |