# Floating IPs

> Hold public IPv4 addresses and subnets on your account and attach them to instances and servers.

Source: https://www.coritan.com/docs/floating-ips/

In the dashboard:

- /solutions/floating-ips: https://www.coritan.com/solutions/floating-ips
- /dashboard/networking: https://www.coritan.com/dashboard/networking
- /dashboard/networking/ips: https://www.coritan.com/dashboard/networking/ips
- /dashboard/networking/ips/…/overview: https://www.coritan.com/dashboard/networking/ips

A *floating IP* is a public IP address that belongs to your account instead of to one machine. You attach it to a Cloud Compute instance or a Container Apps server, and you can move it to another one later while the address stays the same. A floating IP is either a single IPv4 address or a *subnet*, a block of addresses whose hosts you attach one at a time.

Use a floating IP when an address has to outlast the machine behind it, such as a mail server whose reverse DNS you want to keep or a game server address your players have saved.

## Your floating IPs

Select **Floating IPs** in the [dashboard](https://www.coritan.com/dashboard/networking) sidebar. The **IPs** tab lists every floating IP on your account. Each row shows the **Address** with its prefix length, such as `203.0.113.10/32`, its **Version**, **Region** and **Prefix**, what it is **Attached to**, and its **Status**. A subnet shows how many usable hosts it has and how many of them are attached.

- Filter the list with **All**, **Attached**, **Unattached** or **Pending**. `Pending` marks a floating IP whose service is not active, such as one that waits for payment or is suspended.
- Type in the search box to find a floating IP by its address, region, pool or what it is attached to.
- Select **Order floating IP** to order one, as [Order a floating IP](/docs/floating-ips/order-a-floating-ip/) describes.

The IPv4 address that comes with a Cloud Compute instance is a floating IP too, so it appears in this list. It ends when the instance ends.

Select a row to open the floating IP. The header shows the address, its status, whether it is an `IPv4 address` or a `Subnet block`, its region and what it is attached to. **Copy address** copies the address.

## Read the Overview tab

The **Overview** tab opens first. When a single address is not attached to anything, the tab starts with **Not attached to anything yet** and a link to attach it.

**Address**
: The address or subnet, its **Version**, **Prefix**, **Region** and **Pool**, and its **Gateway** when it has one. A single address shows what it is **Attached to**, **Attached since** and, on an instance, its **Role on instance**: `Primary address` or `Additional address`. A subnet shows **Hosts**: how many of its usable hosts are attached and how many are free. **Reverse DNS** shows the address's hostname, or **Set reverse DNS** when it has none.

**Service**
: The service that bills for the floating IP: its **Status**, **Product**, **Price**, **Next renewal**, when it was **Ordered**, and its **Service ID**. **Open Billing** opens the **Billing** tab.

**Tags**
: Labels to find the floating IP by, as [Tag your services](/docs/get-started/tags/) describes.

**Protection**
: A reminder that DDoS Shield filters traffic to the address. **Open Shield** opens the **Shield** tab.

## What you can do

Get an address:

- [Order a floating IP](/docs/floating-ips/order-a-floating-ip/), and follow the order on the **Orders** tab
- [IP pools and regions](/docs/floating-ips/pools/), the **Pools** tab

Use it:

- [Attach and detach a floating IP](/docs/floating-ips/attach-and-detach/), the **Attach** tab
- [Set reverse DNS for a floating IP](/docs/floating-ips/reverse-dns/), the **Reverse DNS** tab
- [How subnets work](/docs/floating-ips/subnets/), the **Hosts** tab
- [Change a floating IP's DDoS protection](/docs/floating-ips/shield-settings/), the **Shield** tab

Pay for it and fix problems:

- [Cancel a floating IP](/docs/floating-ips/billing/), the **Billing** tab
- [Troubleshoot floating IPs](/docs/floating-ips/troubleshooting/)

The public page at `https://www.coritan.com/solutions/floating-ips` describes the product. The **Pools** tab shows the sizes and regions you can actually order.

## How floating IPs are billed

Each floating IP is a service of its own, on the plan and billing cycle you order it on. A single address costs nothing while it is the primary address of a Cloud Compute instance. Anywhere else it bills at its plan's price: while it is unattached, as an additional address on an instance, or on a server. A subnet always bills at its plan's price.

[Cancel a floating IP](/docs/floating-ips/billing/) explains how the price follows the address. [Billing](/docs/billing/) covers invoices, credit and payment.

## Limits and availability

- Floating IPs are IPv4. You can order a single address, or a subnet from `/29` to `/24` where the **Pools** tab offers one.
- A floating IP attaches to a Cloud Compute instance or a Container Apps server.
- A single address attaches to one instance or server at a time. Each host of a subnet attaches on its own, so different hosts can go to different targets.
- A server holds one floating IP. An instance can hold several, and one of them is its primary address.
- DDoS Shield filters traffic to every floating IP on your account, attached or not.

## With the API

`GET /api/v1/client/ips` lists the floating IPs on your account, newest first, as `items` with a `total`.

```bash
curl https://api.coritan.com/api/v1/client/ips \
  -H "Authorization: Bearer $CORITAN_TOKEN"
```

```json
{
  "items": [
    {
      "service_id": 214,
      "service_status": "active",
      "amount": 4.0,
      "billing_cycle": "monthly",
      "next_due_date": "2026-10-25T00:00:00",
      "kind": "standalone",
      "address": "203.0.113.10",
      "cidr": "203.0.113.10/32",
      "version": "ipv4",
      "prefix_len": 32,
      "inventory_status": "assigned",
      "pool_id": 4,
      "pool_name": "Frankfurt 1",
      "region": "fra",
      "geo_label": "Frankfurt",
      "target_type": "vps",
      "target_service_id": 118,
      "attached_at": "2026-09-25T10:00:00",
      "is_primary": 1
    }
  ],
  "total": 1
}
```

Use `service_id` in every other floating IP request. `kind` is `standalone` for a single address and `block` for a subnet. `inventory_status` is `assigned` once the address is yours to attach. `amount` is what the next renewal costs.

For a single address, `target_type` is `vps` for an instance or `container` for a server, and `target_service_id` is that service's ID. Both are `null` when the address is not attached. `is_primary` is `1` when the address is its instance's primary address. On a server, `host_state` and `host_error` say whether the address reached the server's host.

A subnet has `null` in the attachment fields. It carries `hosts`, one entry for each address in the block, and the counts `hosts_total`, `hosts_attached` and `hosts_available`, as [How subnets work](/docs/floating-ips/subnets/) describes.

`GET /api/v1/client/ips/{service_id}` returns one floating IP with the same fields. A service that is not a floating IP on your account answers `404` with `IP service not found`.

The [Floating IPs API reference](/docs/api/reference/client/floating-ips/#op-get-api-v1-client-ips) lists every field.

## API

- `GET /api/v1/client/ips`: List account-owned floating IP / subnet services and attachment state (https://www.coritan.com/docs/api/reference/client/floating-ips/#op-get-api-v1-client-ips)
- `GET /api/v1/client/ips/{service_id}`: Get my IP (https://www.coritan.com/docs/api/reference/client/floating-ips/#op-get-api-v1-client-ips-service-id)