Explains how to use customer-owned IP addresses with Vultr instances through BGP sessions and routing coordination
Using your own IP address space with Vultr instances requires establishing a BGP session. Vultr does not allow direct assignment of customer-owned IPs to instances without BGP because IP advertisement and routing must be coordinated with Vultr’s network infrastructure to ensure proper propagation and reachability.
Organizations with registered IP prefixes and an associated Autonomous System Number (ASN) can peer with Vultr’s network using either the public ASN (AS20473) or their own ASN. This setup allows you to advertise your IP prefixes across Vultr’s backbone while maintaining control over routing policies, such as AS_PATH prepending, selective advertisement, and traffic engineering. Both IPv4 and IPv6 prefixes are supported, but the instances themselves must participate in BGP to handle route announcements.