---
title: "Reserved IPs"
description: "Reserved IPs in TIR come in two types, public and VPC. See how they differ, the states they move through, the limits, and the billing."
content_type: "concept"
product: "tir-reserved-ip"
platform: "TIR"
url: "/tir/tir-reserved-ip/concepts/reserved-ips/"
topic: ["reserved-ips"]
---

# Reserved IPs

A reserved IP is an IP address kept for your account until you delete it. The **Type** column of
the **Manage Reserved IP** list shows which of the two types it is.

A **Public** reserved IP is a static public address. You can point DNS at it, reach a resource at
the same outside address every time, and move it to another resource when you need to fail over.

A VPC IP has the **Type** **Private**. It is a private IP reserved from a VPC in your E2E MyAccount
project, which you attach to an instance or an inference service in TIR. To make a VPC there, see
[Create a VPC](/myaccount/vpc/how-to/create-a-vpc/). The resource then talks to that VPC over
private addresses only, away from the public internet.

## The two types

|                             | Public                                                      | VPC IP (**Type** Private)                               |
| --------------------------- | ----------------------------------------------------------- | ------------------------------------------------------- |
| Reserve it with             | **Reserve New IP**                                          | **Reserve from VPC**                                    |
| What it is                  | A static public address                                     | A private IP allocated inside the VPC you chose         |
| Attach it to                | An instance, a VM, a Slurm cluster, or a Kubernetes cluster | An instance or an inference service                     |
| How many a resource holds   | One instance can hold several                               | An instance or an inference service holds one at a time |
| Transfer to another project | Yes                                                         | No; delete it and reserve a new one there               |
| Billing                     | Charged monthly until you delete it                         | Free in TIR                                             |

Reserving a VPC IP takes two addresses from the VPC: the IP and an **Egress IP**. The list shows
both, with the VPC under **VPC Name**. You can attach, detach, and delete either type.

## How a public reserved IP differs from a default public IP

An instance gets a public IP by default. It keeps that IP through a restart, but a stop gives it
back, so the next start can bring a different address. A reserved IP keeps its address through a
stop and a start, because it stays reserved for you. See
[Manage IP addresses on an instance](/tir/tir-instance/how-to/manage-ip-addresses-on-an-instance/).

## States

| State    | What it means                                                                                           |
| -------- | ------------------------------------------------------------------------------------------------------- |
| Reserved | The IP is allocated to your account and free to attach. The list shows **Available**.                   |
| Attached | The IP is assigned to a resource and traffic to it reaches that resource. The list shows **Attached**.  |
| Detached | The IP is still allocated to your account and free to attach again. The list shows **Available** again. |
| Released | The IP is deleted and released from your account. It leaves the list.                                   |

The **Manage Reserved IP** list shows only **Available** and **Attached**, so a newly reserved IP
and a detached one both read **Available**.

### VPC IP connection status

After you attach a VPC IP, the status moves from **Connecting** to **Connected**, or to
**Connection Failed** when the connection fails. **Idle** means the VPC IP is free
to attach, which is how a newly reserved or a detached VPC IP reads.

## Where the VPC comes from

You choose the VPC when you reserve a VPC IP, in **My Account Region**, **My Account Project**,
and **VPC**. The region is fixed to match your TIR project: Delhi-NCR in Delhi, Chennai in
Chennai. Choose a VPC that is **Active** and uses an address range E2E assigned; a VPC with a
custom range is refused. You need MyAccount VPC permission to see the list of VPCs.

**Networking** > **VPC** is a different product: a VPC you create in TIR, with a range you choose,
for a virtual machine on a CPU plan. A VPC IP comes only from a MyAccount VPC, so those are the
only VPCs listed when you reserve one. A virtual machine on a CPU plan uses a VPC from
the **VPC** page instead of a VPC IP. See [VPCs](/tir/tir-vpc/concepts/vpcs/).

## Limits and billing

Your account can hold five reserved IPs in each region by default, counted across all of its
projects, and E2E can raise the number. A public reserved IP is charged monthly until you delete
it, even while it is **Available**, so delete the ones you have finished with. A VPC IP is free in TIR. See
[Reserved IP billing](/tir/tir-reserved-ip/concepts/reserved-ip-billing/).

## What you can do

[Reserve an IP](/tir/tir-reserved-ip/how-to/reserve-an-ip-address/),
[attach it](/tir/tir-reserved-ip/how-to/attach-a-reserved-ip/) and
[detach it](/tir/tir-reserved-ip/how-to/detach-a-reserved-ip/),
[transfer a public one](/tir/tir-reserved-ip/how-to/transfer-a-reserved-ip/) to another project,
or [delete it](/tir/tir-reserved-ip/how-to/delete-a-reserved-ip/).