IP Addresses

In order to get any sort of ingress traffic to a server or an environment, Cycle needs to allocate IP addresses at the respective providers.

IP addresses are allocated in blocks, which the platform refers to as IP pools, using the respective infrastructure provider integration.

IP Pools

Each provider offers different mechanics for allocating IPv6 address space. AWS allocates a single IPv6 address per pool while GCP gives a full 32 bit space (around 4 billion IP's).

Each pool represents a group of either assigned or available IPs.

All providers allocate a single IPv4 per request due to its limited availability and cost.

Public IP Allocation

A public IPv4 and IPv6 is assigned to each load balancer instance. Cycle will automatically manage the IP pools as new load balancer instances are created and deleted.

Managing IPs

IP pools can be manually deleted. This is often done for IPv4 blocks that Cycle is currently holding on to but aren't assigned, since these generally have an additional monthly charge via the provider.

To manage IP blocks, see the interface-specific documentation below:

• Portal
• API