# IP Blocks

IP Blocks allow you to request additional IPv4 addresses beyond the primary IP assigned to each service. This is useful for running multiple services, failover configurations, or applications that require dedicated IPs.

### Accessing IP Blocks

Navigate to **IP Blocks** in the sidebar to manage your IPv4 allocations.

### Requesting IP Blocks

#### Start the Request

1. Go to **IP Blocks**
2. Click **Request IP Block**

#### Choose a Region

Select the region for your IP block:

| Region     | Country        | Status    |
| ---------- | -------------- | --------- |
| Frankfurt  | Germany        | Available |
| Pittsburgh | United States  | Available |
| Amsterdam  | Netherlands    | Available |
| London     | United Kingdom | Available |
| Singapore  | Singapore      | Available |
| Tokyo      | Japan          | Available |

IP blocks must be in the same region as the services you'll attach them to.

#### Choose a Datacenter

Select the specific datacenter within your chosen region. Some datacenters are marked:

* **New Availability Zone**: Recently added capacity

#### Select Block Size

Choose the number of IPs you need:

| Block Size | IPv4 Addresses | On Demand Pricing       |
| ---------- | -------------- | ----------------------- |
| /27        | 32             | $0.219/hr (\~$160/mo)   |
| /28        | 16             | $0.110/hr (\~$80/mo)    |
| /29        | 8              | $0.055/hr (\~$40/mo)    |
| /30        | 4              | $0.027/hr (\~$20/mo)    |
| /32        | 1              | $0.007/hr (\~$5/mo)     |
| /24        | 256            | $1.397/hr (\~$1,020/mo) |

Prices vary by region. The console shows current pricing for your selected location.

#### Select Service

Choose which service to attach the IP block to:

* Shows compatible services in the selected region
* Displays service name, type, and status
* Only active services can receive IP blocks

#### Configure Display Name and Tags

1. **Display name**: Enter a name to identify this IP block
2. **Tags**: Add tags for organization

#### Submit Request

Click **Proceed to IP Block Order Summary** to review and submit.

### Managing IP Blocks

#### View IP Blocks

The IP Blocks page shows all your allocations:

| Column      | Description               |
| ----------- | ------------------------- |
| Block       | IP range or individual IP |
| Region      | Datacenter location       |
| Attached To | Service using this block  |
| Status      | Active, Pending, etc.     |

#### Attach to Service

To attach an unattached IP block:

1. Find the IP block
2. Click **Actions** > **Attach**
3. Select the target service
4. Confirm attachment

#### Detach from Service

To detach an IP block:

1. Find the attached IP block
2. Click **Actions** > **Detach**
3. Confirm detachment

The IP block remains in your account for reattachment.

#### Release IP Block

To permanently release an IP block:

1. Ensure it's not attached
2. Click **Actions** > **Release**
3. Confirm release

{% hint style="warning" %}
Released IP blocks cannot be recovered. The IPs return to the general pool.
{% endhint %}

\## Using IP Blocks

#### On Metal Services

After attaching, configure the additional IPs in your OS:

```bash
# Ubuntu/Debian example - add to /etc/netplan/99-custom.yaml
network:
  version: 2
  ethernets:
    enp65s0f0np0:
      addresses:
        - 192.0.2.10/32
        - 192.0.2.11/32
```

Apply with:

```bash
sudo netplan apply
```

#### Verifying Configuration

Test that additional IPs are working:

```bash
# Check IP is configured
ip addr show

# Test connectivity from the IP
curl --interface 192.0.2.10 https://api.ipify.org
```

### Use Cases

#### Multiple Websites

Host multiple SSL websites with dedicated IPs:

* Each site gets its own IP
* Required for some SSL configurations
* Easier certificate management

#### High Availability

Configure failover between instances:

* IP can float between servers
* Fast failover capability
* No DNS propagation delay

#### IP Reputation

Separate IPs for different purposes:

* Email sending
* API endpoints
* Customer-facing services

#### Compliance

Meet requirements for dedicated IPs:

* PCI compliance
* Customer isolation
* Audit requirements

### Best Practices

#### Planning

* Request blocks in the same region as services
* Consider future growth when sizing
* Document IP assignments

#### Security

* Configure firewall rules for additional IPs
* Monitor traffic per IP
* Use separate IPs for sensitive services

#### Cost Management

* Release unused IP blocks
* Right-size blocks to actual needs
* Monitor usage and justify allocations

### Pricing

IP blocks are billed:

* Per hour (prorated)
* Based on block size
* Region-specific pricing

Blocks are billed whether attached or unattached.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.teraswitch.com/compute/metal/ip-blocks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.