Reserved IPs

Quake AI concept: Floating IPs

• Vultr models the resource as an account-scoped Reserved IP rather than an OpenStack-style floating IP pool object. The doc says Reserved IPs remain assigned to your account even when not attached to a server, and they can be detached and reattached later within the same region. (Reserved IPs - Vultr Docs)
• Reserved IPs are billed as a separate hourly charge of $0.004 per hour ($3/month). OpenStack floating IP behavior is typically quota-based networking allocation, whereas Vultr explicitly documents ongoing pricing for the static address itself. (Reserved IPs - Vultr Docs)
• Vultr says you cannot choose a specific public IPv4 to reserve from scratch; Reserved IPs are either automatically allocated or created by converting an existing instance IP. That is different from an OpenStack Neutron floating IP workflow where addresses are normally allocated from a project network pool. (Reserved IPs - Vultr Docs)
• A Reserved IP can only be attached to one instance at a time, and Vultr limits reassignment to the same region. OpenStack floating IPs are generally associated to ports/instances within Neutron networking rather than described in Vultr's account-centric terms and regional reuse model. (Reserved IPs - Vultr Docs)