---
title: "Limits and Quotas - Elastic IP"
description: "Exoscale Elastic IP limits and quotas, including incoming-only traffic, health checks, IPv6 prefixes, and zone availability."
url: https://community.exoscale.com/product/networking/eip/service-boundaries/limits-and-quotas/
product: "EIP"
section: product
last_updated: 2026-09-14
---
> For AI agents: the documentation index is at https://community.exoscale.com/llms.txt. Every page is available as markdown at `<page URL>index.md` or with `Accept: text/markdown`.

# Limits and Quotas - Elastic IP

## Limits


| Usage | Limit |
| -------------------------------------------------------- | ------------- |
| EIP description maximum characaters | 255 |


* HTTP health checks do not follow redirects.
* Elastic IPv6 prefixes have the same limitations as Elastic IPs.
* Elastic IP will natively work only for incoming traffic. Outgoing traffic will still use the native instance's IP address as a source. This behavior can be partially circumvented manually with manual Elastic IPs.
* Instances associated with a managed Elastic IP will see incoming Elastic IP traffic destined to their primary interface IP address.
* With managed Elastic IPs, it is currently not possible to retrieve the health status of an instance: while the system will not direct traffic to a unhealthy instance, there is no information about which instance is in an unhealthy state.
* For managed Elastic IPv6 prefixes, only the first-plus-one IPv6 address of that prefix is transparently forwarded to the associated instances.



## Quotas

| Usage | Quota |
| :------ | :------: |
| Elastic IP adresses count | 5 |

## Availability
EIP is available in all zones.