Static CIDRs are a Starter+ feature. On the Free plan the Static CIDRs sidebar item is hidden — upgrade to declare on-prem ranges.
Add a single static CIDR
- In the left sidebar, click Static CIDRs.
- Click Add static CIDR (top right).
- In the dialog, fill in:
- CIDR (required) — e.g.
192.168.50.0/24. - Kind — leave on On-prem. (A "Future reservation" option appears on Pro+ — that one is managed differently; see Future reservations.)
- Label (required) — e.g.
DC London. - Owner note (optional) — ticket #, owning team, etc.
- Expires at (optional).
- CIDR (required) — e.g.
- Click Add.
On success you'll see one of two banners: "Linked to pool …" (green) if the range falls inside a pool, or "Added as orphan" (blue) if no pool currently contains it. An orphan isn't an error — it auto-links the moment you create a containing pool.
Bulk import from CSV
Declaring a whole datacenter at once? Use bulk import.
- On the Static CIDRs page, click Bulk import.
- (Optional) click Download CSV template. The accepted columns are:
cidr,label,description
10.50.0.0/16,DC London,primary datacenter
192.168.10.0/24,Branch HQ,- Drop in your
.csvand click Continue to preview. VNet IQ validates every row server-side (a dry run — nothing is saved yet) and shows which rows are valid and which pool they'd link to. - Click Import N rows, then Done.
Up to 1,000 rows / 1 MiB per upload. If any row fails validation, the whole batch
is rejected and nothing is saved — fix the flagged rows and re-upload. Only cidr,
label, and description are recognised; any other column (e.g. kind)
is ignored with a warning.
The rules static CIDRs enforce
- Valid CIDR notation, e.g.
10.0.0.0/24. - No exact duplicate of an existing static of the same kind.
- No overlap with another on-prem static range.
- A static may sit inside a future reservation — it's treated as an exclusion zone, not a conflict.
How it shows up
Each static CIDR links to the deepest pool whose range contains it (or stays org-level as an orphan). Once declared, any overlap between a static range and a cloud network appears on the Conflicts page as "Network → On-prem" — which is exactly the cross-environment overlap that's easy to miss until routing breaks.