> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nebius.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting public IPv4 ranges

Public [allocations](/vpc/overview#allocation) use public IPv4 addresses from public pools in [Virtual Networks](/vpc/overview#default-virtual-networks-resources). The available public IPv4 range depends on the project [region](/overview/regions). This page explains how to get the public IPv4 [CIDR blocks](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_blocks) that are available for allocations in a project.

## Prerequisites

<Tip>
  You do not need to complete any prerequisites if you use the web console.
</Tip>

If you use the CLI:

1. [Install](/cli/install) and [configure](/cli/configure) the Nebius AI Cloud CLI.
2. Check that your project ID is saved in the Nebius AI Cloud CLI profile configuration:
   ```bash theme={null}
   cat ~/.nebius/config.yaml
   ```

## How to get public IPv4 ranges

<Tabs group="interfaces">
  <Tab title="Web console">
    1. In the [web console](https://console.nebius.com), go to <Icon icon="https://mintlify.s3.us-west-1.amazonaws.com/nebius-ai-cloud/_assets/sidebar/network.svg" /> **Networking** → **Virtual networks**.
    2. If you have access to multiple projects, expand the top-left list of projects and select the required project.
    3. Click **Actions** → **View public CIDR blocks**.

       The **Public CIDR blocks** window shows the public IPv4 CIDR blocks that are available for allocations in the selected project and region.
  </Tab>

  <Tab title="CLI">
    1. [Get the ID](/vpc/networking/resources#how-to-get-a-network-id) of the default network in the required project.

    2. Get the ID of the default network's public pool:

       ```bash theme={null}
       nebius vpc network get --id <network_ID>
       ```

       The pool ID is specified in the `spec.ipv4_public_pools.pools.id` parameter of the output.

       If the default network contains several public pools, a public address can be allocated from any of these pools.

    3. Get the CIDR blocks of the public pool:

       ```bash theme={null}
       nebius vpc pool get --id <pool_ID>
       ```

       The output looks like this:

       ```yaml theme={null}
       metadata:
         id: vpcpool-***
         parent_id: project-***
         name: default-public-pool
         resource_version: "2"
         created_at: "2025-07-21T16:21:38.791627Z"
         updated_at: "2025-07-21T16:46:45.356295Z"
       spec:
         source_pool_id: vpcpool-e00***
         version: IPV4
         visibility: PUBLIC
       status:
         state: READY
         cidrs:
           - 89.169.96.0/22
           - 89.169.102.0/23
           - 89.169.108.0/22
         scope_id: vpcscope-e00***
         assignment:
           networks:
             - vpcnetwork-e00***
       ```

       The output contains the following parameters:

       * `metadata.id`: The ID of the [public pool](/vpc/overview#pool).
       * `metadata.parent_id`: The project ID.
       * `metadata.name`: The name of the public pool.
       * `spec.source_pool_id`: The ID of the source pool for this public pool.
       * `spec.version`: The IP version of the pool.
       * `spec.visibility`: The pool visibility.
       * `status.state`: The current state of the public pool.
       * `status.cidrs`: The public IPv4 CIDR blocks that are available for allocations in the project. These addresses form the public IPv4 range from which Virtual Networks allocates public addresses.
       * `status.scope_id`: The ID of the scope associated with the public pool.
       * `status.assignment.networks`: The IDs of the networks that use this public pool.
  </Tab>
</Tabs>