Vultr's Private ASN - AS64515

2 min readUpdated 23 October 2026

Route Reserved IPs over internal BGP sessions with Vultr private ASN AS64515, which works on Cloud Compute only.

Vultr offers Private ASN (AS64515) for internal routing and network management within its infrastructure. This ASN is specifically designed for use with Vultr's network services, and it ensures private, isolated routing of your IP addresses within Vultr's infrastructure.

Follow this guide to configure and use AS64515 as your private ASN with Vultr's network, focusing on internal routing and BGP peering.

Understanding Vultr Private ASN - AS64515

Private ASN: An ASN used within a private network for internal routing and network management.

AS64515 is an ASN designated for private use within Vultr's internal network infrastructure.
It is assigned for customers who wish to use private peering for managing their reserved IPs and internal routing within Vultr's infrastructure.
If you do not have your own ASN, AS64515 is automatically assigned when you choose to broadcast your Reserved IPs.

Note

Private ASN (AS64515) can only be used for peering with Vultr Cloud Compute instances for internal routing. It is not available for Vultr Bare Metal instances.

Peering with Vultr Using AS64515

When peering using AS64515, you will establish BGP sessions for private, internal routing. The AS64515 ASN will only be used within Vultr's network for managing IPs, ensuring a secure and private routing setup.

Private ASN Peering:

Customers using AS64515 will only perform internal BGP routing within Vultr's infrastructure.
AS64515 does not allow public ASN peering and is not used for advertising to external networks or the public internet.
All routing with AS64515 will be confined to Vultr's internal network, offering private and secure connectivity for your resources.

Example: When using AS64515, you will be able to configure your private BGP sessions, and the AS_PATH will only include AS64515, with no modifications for external network peering.

RPKI and Prefix Validation

Vultr uses Resource Public Key Infrastructure (RPKI) to validate BGP announcements and ensure the integrity of network prefixes. When using AS64515, it's crucial to ensure that only valid RPKI prefixes are announced within Vultr's internal network to minimize the risk of misrouting or hijacking.

0 Comments

Start the conversation

Be the first to comment and share your perspective with the community.

Understanding Vultr Private ASN - AS64515

Private ASN: An ASN used within a private network for internal routing and network management.

AS64515 is an ASN designated for private use within Vultr's internal network infrastructure.

It is assigned for customers who wish to use private peering for managing their reserved IPs and internal routing within Vultr's infrastructure.

If you do not have your own ASN, AS64515 is automatically assigned when you choose to broadcast your Reserved IPs.

Note

Private ASN (AS64515) can only be used for peering with Vultr Cloud Compute instances for internal routing. It is not available for Vultr Bare Metal instances.

Peering with Vultr Using AS64515

Private ASN Peering:

Customers using AS64515 will only perform internal BGP routing within Vultr's infrastructure.

AS64515 does not allow public ASN peering and is not used for advertising to external networks or the public internet.

All routing with AS64515 will be confined to Vultr's internal network, offering private and secure connectivity for your resources.

Example: When using AS64515, you will be able to configure your private BGP sessions, and the AS_PATH will only include AS64515, with no modifications for external network peering.