Vultr BYOIP Integration Overview
Worth Knowing
AS64515 is the private VPS BGP peer, not Vultr's public ASN. ROA is recommended, not stored here as a universal requirement. LOA is not established. Onboarding is a request and approval plus your routing configuration, not a fully automated import.
Searching for the best IP providers? Vultr supports IPv4 and IPv6 BYOIP through customer BGP. You submit a BGP request, complete prefix validation, and configure routing. A customer-owned ASN is optional: Vultr can use a private session ASN. Public AS20473 is Vultr's network ASN. AS64515 is the private VPS BGP peer, not a second public identity.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Vultr |
| Website | vultr.com |
| ASN(s) | AS20473, Vultr's public network ASN. VPS BGP sessions use private AS64515. That private peer is not the provider's public ASN. |
| Regions Supported | The BGP guide says you can use your own space across Vultr locations. The current region list, checked 6 October 2026, covers Australia, Brazil, Canada, Chile, France, Germany, India, Israel, Italy, Japan, Mexico, the Netherlands, Poland, Singapore, South Africa, South Korea, Spain, Sweden, the United Kingdom and the United States. Cities include Amsterdam, Frankfurt, London, Manchester, Paris, Madrid, Milan, Stockholm, Warsaw, Tokyo, Osaka, Seoul, Singapore, Sydney, Melbourne, Mumbai, Bangalore, Delhi NCR, Tel Aviv, Johannesburg, Toronto, São Paulo, Santiago, Mexico City, and US sites from Atlanta to Silicon Valley. |
| Tech Article & Date | BYOIP policy and BGP configuration - checked 6 October 2026 |
| BYOIP Scope | Customer IPv4 and IPv6 prefixes on Vultr via BGP, after a request and prefix validation. |
| Supported Versions | IPv4: /16 through /24. IPv6: /32 through /48. Up to five prefixes in total. |
| Supported Services | Vultr instances that can run the BGP session, including the floating-IP patterns in Vultr's high-availability guide. |
Caveats and Gotchas
- Onboarding is a request plus approval, then you configure routing. It is not a fully automated import.
- Vultr does not publish a managed reputation-monitoring product for BYOIP prefixes. Keeping the same addresses is not a reputation service.
- ROA is recommended, and the origin in the ROA has to match the ASN you actually announce from. That recommendation is not a universal requirement written as a hard gate for every prefix.
- Whether Vultr asks for an LOA is not established by the current policy pages. Do not read a missing LOA flag as a ban on LOAs.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | IPv4 /16 through /24. IPv6 /32 through /48. Up to five prefixes. |
| ASN Ownership Required | No. Your own ASN is supported. A private session ASN is available. |
| LOA | Not established as required or forbidden. |
| RPKI ROA | Recommended. Authorize the origin you will actually use. |
| IRR Route Object | RIR registration and appropriate routing authorization. The docs describe creating a RADb route object where one is needed. |
| Ownership Proof | The prefix must be registered to you at the RIR, with routing authorization that matches the announcement. |
Step-by-Step BYOIP Process
Step 1
Deploy the Vultr instance that will run BGP.
Step 2
Submit a BGP request and complete prefix validation.
Vultr's prefix onboarding note covers the timeline for that check.
Step 3
Create the IRR route object if the docs say one is required for your prefix.
Step 4
Configure the BGP session.
Use your ASN or the private session ASN, and announce only the validated prefixes.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Not restated here. Use Vultr's current price list rather than an older page. |
| Other Limitations | Five prefixes maximum. Prefix lengths above are the accepted ranges, not a promise that every length works on every product. |
Related Resources
Published 8 August 2025 · Updated 6 October 2026