Virtua.Cloud BYOIP Integration Overview
Provider Details
| Company | Virtua.Cloud |
| Homepage | https://www.virtua.cloud |
| BYOIP Documentation | https://www.virtua.cloud/features/bring-your-own-ip |
| Primary Products | BGP-enabled VPS hosting |
| Announcing ASN (managed option) | AS35661 |
| Supported Locations | Paris, Lille, Frankfurt, Amsterdam, Fremont |
Technical Requirements
| Minimum IPv4 Prefix | /24 |
| Minimum IPv6 Prefix | /48 |
| ROA/RPKI Required | Yes, valid ROA/RPKI records or IRR route objects required |
| LOA Required | Not publicly documented |
| ASN Requirement (self-managed BGP) | Customer must hold their own ASN, or Virtua.Cloud can handle ASN registration on the customer's behalf |
| Supported BGP Software | FRR, Quagga, BIRD, VyOS, pfSense, Mikrotik CHR |
Step-by-Step BYOIP Process
Step 1
Ensure the IP prefix (owned or rented, e.g. via IPXO) has a valid ROA/RPKI record or a matching IRR route object.
Step 2
Choose between two models
self-managed BGP sessions (bring your own ASN) or managed BYOIP (Virtua.Cloud announces the prefix under AS35661, no ASN required).
Step 3
For self-managed BGP, configure a BGP session using supported routing software (FRR, Quagga, BIRD, VyOS, pfSense, or Mikrotik CHR); redundant sessions are available for maximum availability.
Step 4
Assign individual IPs or entire blocks to VMs from the customer area or via API, with changes taking effect automatically.
Cost and Limitations
| Setup Fees | None, no setup fees or recurring charges |
| Included With | Every VPS plan |
| Minimum Prefix Size | /24 (IPv4), /48 (IPv6) |
| Additional Notes | Not publicly documented |
Troubleshooting & Gotchas
- Prefixes without a valid ROA/RPKI record or a matching IRR route object will not be accepted for BYOIP.
- Not publicly documented for other common BYOIP failure scenarios (e.g. propagation delays, RIR-specific quirks).
Related Resources
Published 9 September 2026