> For the complete documentation index, see [llms.txt](https://doc.cloudbit.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cloudbit.ch/products/compute/networking/elastic-ips.md).

# Elastic IPs

Elastic IPs (Floating IPs) are publicly-accessible static IP addresses that you can assign to Instances and instantly remap between other Instances in the same region.

You can use elastic IPs to create server infrastructures without single points of failure, but a elastic IP alone does not automatically provide high availability. For a setup to be highly available, you need to implement a failover mechanism to automate the process of detecting failures of the active server and reassigning the elastic IP to a passive server.

## Plans and Pricing

One Elastic IP is free when assigned to a Instance. For pricing details please consult our [pricing page](https://doc.cloudbit.ch/platform/pricing/elastic-ips.md).

## Regional Availability

Elastic IPs are available in all regions. They are region-specific resources and can only be assigned within the same region.

## Limits

* Elastic IPs cannot be assigned to more than one instances at a time.<br>
* At the moment, we do not support IPv6 elastic IPs. All elastic IPs are IPv4.<br>
* Reverse DNS Records (rDNS) have to be requested via support ticket.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.cloudbit.ch/products/compute/networking/elastic-ips.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
