---
title: "VPCs"
description: "What a TIR VPC is, what it gives you, its statuses and limits, and which resources can use it."
content_type: "concept"
product: "tir-vpc"
platform: "TIR"
url: "/tir/tir-vpc/concepts/vpcs/"
---

# VPCs

A VPC is a private network inside a TIR project. You choose its IPv4 address range, and the resources you place on it
reach each other over private addresses instead of over the public internet. Use a VPC when your resources need to talk
to each other privately.

## What you get

- You choose the private address range of the VPC.
- Resources on the same VPC reach each other directly over private addresses, with no public IP needed.
- Each VPC is a separate network, and its traffic stays apart from every other VPC, even one that uses the
  same range.
- A VPC is ready to use as soon as its status reads **Active**, and you can put machines on it straight
  away, with no routing, gateway, or address assignment to set up.

## Projects and regions

A VPC belongs to one project in one region, and the machines on it come from that same project and region.
The **VPC** page shows the VPCs of the project and region you have selected.

## Statuses

| Status       | What it means                                                                                |
| ------------ | -------------------------------------------------------------------------------------------- |
| **Creating** | TIR is setting up the VPC. You can use it once it turns **Active**, which happens by itself. |
| **Active**   | The VPC is ready.                                                                            |
| **Failed**   | Setting up the VPC failed, and it cannot be used. Delete it and try again.                   |

## How many you can have

An account can have five VPCs in each region, counted across all its projects. Support can raise the limit.
An address range is /16 at the largest and /28 at the smallest.

## What can use a VPC

Virtual machines on a CPU plan in Delhi and Chennai can use a VPC. You choose it under **VPC** in **Network & Security** when
you create the machine, or use **Attach VPC** on the machine afterward. A machine holds one VPC at a time, and attaching
or detaching restarts it. The VPC must be **Active**, in the machine's own region, and have enough free IPs for the
machines you launch. Instances and inference services get a private address another way: a reserved IP of **Type**
Private from a VPC in your E2E MyAccount project, described in [Reserved IPs](/tir/tir-reserved-ip/concepts/reserved-ips/).

Every project also has a default VPC that TIR manages for it. It stays off the list, and you cannot rename or delete
it. The name `default` is reserved, so give your own VPC a different name.

## Billing

A VPC is free. Network resources are billed separately from the compute charge of the resources that use them. For the rates of other resources, see [E2E's pricing page](https://www.e2enetworks.com/pricing).

## What you can do

[Create a VPC](/tir/tir-vpc/how-to/create-a-vpc/), [rename it](/tir/tir-vpc/how-to/rename-a-vpc/), or
[delete it](/tir/tir-vpc/how-to/delete-a-vpc/). To choose a range, see
[VPC address ranges](/tir/tir-vpc/concepts/vpc-address-ranges/). To connect an instance or an inference service to a
VPC in your E2E MyAccount project, see [Reserved IPs](/tir/tir-reserved-ip/concepts/reserved-ips/) and reserve an IP of **Type** Private.