Nebius AI Cloud’s capacity advisor provides insights into GPU capacity availability for launching virtual machines (VMs) with specific hardware presets. It helps you understand where you can launch VMs based on your quotas and the current physical capacity in Nebius AI Cloud regions.
Scope
The capacity advisor provides data for the following virtual machines with GPUs:
Data about computing resource availability of standalone applications and VMs without GPUs isn’t provided.
Data provided by the capacity advisor is accurate as of a specific timestamp included in the data and doesn’t guarantee availability of GPU resources at creation time.
Prerequisites
Nebius AI Cloud provider for Terraform doesn’t support the capacity advisor.
How to get data from the capacity advisor
In the sidebar, go to
Capacity dashboard under Manage.For each VM platform, preset, region, InfiniBand™ fabric and VM type (regular, preemptible or with reservations), the capacity advisor shows:
-
How many VMs you can launch, based on your quotas and the current physical capacity (for regular and preemptible VMs) or on your active capacity reservations (for VMs with reservations).
-
How likely you are to be able to launch the displayed number of regular or preemptible VMs.
For example, if your quota for a certain kind of VMs is 10 VMs, you have a high chance of launching them all when the overall capacity is in the hundreds, but a low chance when the capacity is less than 10 VMs.
As reservations guarantee you a certain number of GPUs that aren’t subject to quotas, the chance of launch isn’t displayed for VMs with reservations.
-
Get the tenant ID.
To get the tenant ID, go to the web console and expand the top-left list of tenants. Next to the tenant’s name, click
→ Copy tenant ID.
-
Run
nebius capacity resource-advice list to get the capacity advisor data:
nebius capacity resource-advice list --parent-id <tenant_ID>
In the output, each list item contains data for a single combination of VM platform, preset, region, InfiniBand fabric and VM type:items:
- spec:
region: eu-north1
fabric: fabric-2
compute_instance:
platform: gpu-h100-sxm
preset:
name: 1gpu-16vcpu-200gb
resources:
vcpu_count: 16
memory_gibibytes: 200
gpu_count: 1
gpu_memory_gigabytes: 80
status:
reserved:
availability_level: AVAILABILITY_LEVEL_LIMIT_REACHED
data_state: DATA_STATE_FRESH
effective_at: "2026-03-27T11:25:55.695087Z"
on_demand:
available: 24
limit: 32
availability_level: AVAILABILITY_LEVEL_HIGH
data_state: DATA_STATE_FRESH
effective_at: "2026-03-27T11:08:07.360Z"
preemptible:
available: 22
limit: 128
availability_level: AVAILABILITY_LEVEL_MEDIUM
data_state: DATA_STATE_FRESH
effective_at: "2026-03-27T11:08:07.360Z"
...
In the .items[*].status fields, on_demand, preemptible and reserved contain data about regular VMs, preemptible VMs and VMs with reservations, respectively. Each of these fields contains the following data:
-
available: Maximum number of VMs that you can launch, based on your quotas and the current physical capacity.
-
limit: Your current quota.
-
availability_level: Level of resource availability. Possible values:
AVAILABILITY_LEVEL_LOW: Low chance of launch — Available capacity is significantly lower than your quota. Creating resources might not be possible.
AVAILABILITY_LEVEL_MEDIUM: Medium chance of launch — available capacity is lower than your quota. Creating resources is possible, but may fail.
AVAILABILITY_LEVEL_HIGH: High chance of launch — available capacity is enough to fully satisfy your quota.
AVAILABILITY_LEVEL_LIMIT_REACHED: Launch impossible — No available capacity.
-
data_state: State of the data. Possible values:
DATA_STATE_FRESH: Data is up to date (fetched recently).
DATA_STATE_STALE: Data is stale (fetched a long time ago).
DATA_STATE_UNKNOWN: Capacity advisor failed to fetch data.
-
effective_at: Timestamp of the last update.