Elastic Addressing

  • Distribute requests across Packet servers & facilities

  • Deploy and configure via portal or API

  • Automatically route requests based upon geography

  • Simple pricing starting at $.005 per hour

Elastic Addressing

How do I configure additional elastic IPs on my server?

Packet was built for production workloads, and having the ability to manage a pool of IPs across your servers is a crucial piece to fulfilling that purpose. With Packet elastic IPs, you can assign an IP to any server on the Packet network and have it instantly routable.

We recommend using Elastic IPs for any workload where permanent reachability is required, for example, hosting a public-facing web site behind a load balancer, or directing clients to a clustered database server internally. Move IPs from one server to another if one fails, or move workload to a bigger (or smaller!) server to respond to traffic demands.

We give you a nice big block of public IPv6 and private IPv4 to play with by default, if you need some public IPv4 that's available as well for a nominal monthly fee per IP. We also have the option to announce your IP space and make it available for you to manage using the same Packet tools! Pretty neat if we do say so ourselves.

By default we assign each project a /25 of "internal" IPs (10.x.x.x) which automatically replenish with additional /25 pools as you use them. We also assign each project a publicly routed /56 of IPv6, which is 256 /64 "LAN subnets".

We provide one public IPv4 IP on each server you provision as a "management" IP, which can be used for anything you like, but can't be moved to another server, and is not guaranteed to be re-assigned to you if you redeploy a server. To ensure you retain your public v4 IPs, you can use our customer portal to order additional public address space, ranging from a /32 (a single IP) through a /24 (256 IPs)

You can read all the technical details on how elastic IPs on Packet work by visiting our knowledge base article.