IONOS Cloud BYOIP Integration Overview
Location
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) and Bring Your Own ASN (BYOASN) with IONOS Cloud infrastructure. IONOS currently supports IPv4 BYOIP with two deployment models: (1) provider-announced BYOIP, where IONOS originates your public IPv4 prefixes from its global backbone ASN (AS8560) and makes them available in VDC Networking and Private Cloud, and (2) BYOASN, where your own ASN participates in BGP, originates your prefixes, and uses AS8560 as an upstream. The latest BYOIP/BYOASN tutorial (November 2025) formalises the IPv4-only scope, a minimum prefix size of /24, and a typical activation time of up to five business days from approval.
Provider Details
| Field | Information |
|---|---|
| Provider Name | IONOS Cloud |
| Website | VDC Networking (Network Services) | Bring Your Own IP (BYOIP) address to IONOS Cloud (VDC tutorial) | Requirements for BYOIP & BYOASN (Private Cloud) | Private Cloud: Using BYOIP in NSX | Letter of Authorisation (LoA) |
| ASN(s) |
Global backbone ASN: AS8560 (IONOS SE global backbone; used as origin for provider-announced BYOIP in IRR/RPKI and on the Internet). BYOASN: uses the customer’s own ASN as BGP origin, with AS8560 configured as an upstream / transit ASN and explicitly authorised in your AUTNUM (RPSL) policy. |
| Regions Supported |
BYOIP/BYOASN is documented for both IONOS Private Cloud powered by VMware and VDC Networking (Compute Engine). The 2025 BYOIP tutorial states that onboarded prefixes can be used across all IONOS infrastructure locations worldwide; key cloud data centers (per current Service Catalog) include: DE: Berlin (DE/TXL), Frankfurt (DE/FRA, DE/FRA/2), Karlsruhe (DE/FKB – legacy only for new VDC/Private Cloud) UK: London (GB/LHR), Worcester (GB/BHX) | FR: Paris (FR/PAR) | ES: Logroño (ES/VIT) | US: Las Vegas (US/LAS), Newark (US/EWR), Lenexa / Kansas City (US/MCI). Private Cloud clusters are currently provisionable in Berlin, Worcester, and Logroño (Karlsruhe remains available only for existing tenants). Always confirm current BYOIP/BYOASN availability per region and product with IONOS Cloud Support. |
| Support Contact | IONOS Cloud Support (24/7 Enterprise Level Support via tickets/portal) | Email (per LoA): support@cloud.ionos.co.uk |
| Tech Article & Date |
Bring Your Own IP (BYOIP) address to IONOS Cloud (VDC Networking tutorial; published November 2025; details IPv4-only BYOIP/BYOASN, /24 minimum and ~5 business day onboarding). Requirements for Bring Your Own IP (BYOIP) and Bring Your Own ASN (BYOASN) (Private Cloud IRR/RPKI/RPSL requirements). Private Cloud: Using BYOIP in NSX (NSX implementation). VDC Networking (networking overview; links to BYOIP/BYOASN tutorial and IP Management docs). |
| BYOIP Scope |
Provider-announced BYOIP: you remain the owner of your public IPv4 range; IONOS onboards the prefix (IPv4 /24 or larger) into IP Management, configures IRR/RPKI with AS8560 as the origin, and announces it on the Internet from AS8560. The addresses then behave like standard public IPv4 blocks inside IONOS Cloud and can be assigned to supported services in VDC Networking and Private Cloud (e.g. NSX segments, NAT/VPN endpoints, public NICs, load balancers, Managed NAT Gateway, etc.). BYOASN (Bring Your Own ASN): after BYOIP prerequisites are met, IONOS establishes one or more BGP sessions between AS8560 and your ASN; you originate your prefixes from your ASN with AS8560 as upstream. The same IRR/RPKI/RPSL requirements apply, with additional policy updates to authorise AS8560 as an upstream in your AUTNUM object. BYOIP/BYOASN for Private Cloud and VDC Networking share the same approval letter (LoA) and validation workflow. |
| Supported Versions | IONOS networking and most services are dual-stack (IPv4 and IPv6) in general. However, the current BYOIP/BYOASN onboarding tutorial explicitly supports IPv4 only: you must provide an IPv4 address range of at least /24 (256 addresses) with correct IRR and RPKI registration. IPv6 BYOIP/BYOASN is not available as of November 2025; customers who require IPv6 should use platform-assigned IPv6 ranges and monitor IONOS documentation for potential future IPv6 BYOIP support. |
| Supported Services |
VDC Networking / Compute Engine: BYOIP/BYOASN onboarding is integrated with VDC Networking. Once your IPv4 range is approved, it appears as an IP block in IP Management and can be consumed by services that support public IPv4 addresses (VM NICs, public LANs, load balancers, Managed NAT Gateway, VPN Gateway, etc.), subject to regional availability. Private Cloud (NSX): BYOIP ranges can back NSX segments and are used in SNAT/DNAT and VPN endpoints in the IONOS Private Cloud environment, following the same BYOIP/BYOASN IRR/RPKI/LoA requirements as the VDC tutorial. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size |
Public, globally routable IPv4 ranges registered in a RIR (RIPE, ARIN, etc.) with correct IRR and RPKI data. The 2025 BYOIP/BYOASN tutorial specifies that onboarding is currently limited to IPv4 prefixes of at least /24 (256 addresses). Smaller subnets (e.g. /25) are not eligible and are typically filtered by Internet routers. RPKI ROAs must use a maximum prefix length of /24 to match BGP best practice. |
| ASN Ownership Required |
Provider-announced BYOIP: ASN ownership not required; IONOS announces your prefix using AS8560 under a signed LoA once IRR/RPKI prerequisites are met. BYOASN: ASN ownership required; your ASN is origin, with AS8560 configured as upstream. Your AUTNUM object must explicitly authorise AS8560 as an upstream in RPSL, and ROAs must list your ASN as the origin. |
| IRR / Route Objects |
Customers must ensure that relevant IRR databases (e.g. RIPE, ARIN, APNIC) contain accurate, up-to-date information: – IP range correctly registered (start/end addresses). – Route objects created and maintained with correct origin AS: • BYOIP: origin AS must be AS8560 (IONOS). • BYOASN: origin AS is your ASN. – AS-SET information maintained where applicable. The official BYOIP/BYOASN requirements article and the 2025 tutorial walk through creating and updating these objects before IONOS will accept announcements. |
| ROA or LOA |
RPKI ROAs: Required. Customers must create and keep correct ROAs for their prefixes with the right prefix lengths and origin AS (AS8560 for BYOIP, customer ASN for BYOASN). For IPv4, the maximum prefix length is /24. Letter of Authorisation (LoA): Required. The signed LoA grants IONOS permission to announce your BYOIP ranges via AS8560 and/or establish BGP sessions with your ASN for BYOASN. The template explicitly lists these permissions and remains valid until revoked or the underlying contract is terminated. |
| RIR Limitations | No specific RIR is mandated; IP ranges and ASNs must be properly registered in the appropriate RIR and IRR databases. The tutorial uses RIPE NCC as the worked example, but the same principles apply to ARIN, APNIC, etc. Customers are responsible for registration and ongoing management with the relevant registries and for keeping IRR/RPKI data accurate and up to date. |
Step-by-Step BYOIP Process
Estimated Setup Time: The IONOS BYOIP/BYOASN tutorial indicates that, after IONOS has received a correctly completed approval letter and validated your IRR/RPKI configuration, onboarding and routing are typically activated within up to five business days. Actual timelines can vary, so confirm lead times with IONOS Cloud Support for your specific deployment.
Tested By Us: Not yet
A) Provider-announced BYOIP (IONOS originates your prefixes from AS8560)
B) BYOASN + Prefixes (you originate; IONOS as upstream)
References: Bring Your Own IP (BYOIP) address to IONOS Cloud (VDC tutorial, Nov 2025), Requirements for BYOIP/BYOASN, Private Cloud: Using BYOIP in NSX, VDC Networking FAQ (BYOIP/BYOASN question), Letter of Authorisation (LoA), IONOS Cloud Release Notes – November 2025 (BYOIP/BYOASN tutorial announcement).
Cost and Limitations
| Item | Details |
|---|---|
| Fees | No separate BYOIP/BYOASN price list is published in the referenced docs. BYOIP/BYOASN is an add-on to an existing IONOS Cloud contract (Private Cloud and/or VDC). Standard charges for Private Cloud resources, reserved IPs, traffic, and support apply. The BYOIP/BYOASN tutorial highlights using your own IP space and ASN to avoid additional IP rental fees and states that traffic to and from BYOIP/BYOASN addresses is billed at the same rates as platform-managed IPs. Confirm any one-time or recurring BYOIP/BYOASN fees with IONOS Sales. |
| Bundled or Standalone |
BYOIP/BYOASN is integrated with IONOS networking and IP Management: – VDC Networking / Compute Engine: onboarded IPv4 prefixes appear as IP blocks that you can assign to servers and network services like any other public IPv4 block. – Private Cloud: implemented via NSX (segments, VPN local endpoints, NAT rules) using the same BYOIP/BYOASN approval and validation workflow. BYOIP/BYOASN is not a stand-alone transit or routing product; it is tied to IONOS infrastructure and services. |
| Traffic/Peering Restrictions | Prefixes must be correctly registered and routable and must comply with IONOS terms and acceptable-use policies. BYOIP IPv4 ranges must not be simultaneously advertised by other providers or networks while onboarded at IONOS; any previous external announcements should be withdrawn before the process starts to avoid unintended anycast routing and potential outages. AS8560 must be listed as origin (BYOIP) or as an authorised upstream (BYOASN) in IRR/RPSL, and prefixes must be RPKI-valid. IONOS reserves the right (per LoA) to decline requests, request additional documentation, or filter problematic routes. |
| Other Limitations |
– BYOIP/BYOASN currently applies only to public IPv4 prefixes /24 or larger; private RFC1918 space and IPv6 addresses are configured using standard platform networking features. – In NSX, BYOIP-backed segments must be more specific than the parent BYOIP range (e.g. a /24 BYOIP can be split into /25, /26, etc. for individual segments). – BYOASN requires functional BGP and correct RPKI/IRR/RPSL; misconfigured prefixes may be rejected or filtered until corrected. – Service availability (BYOIP and BYOASN) may vary by data center and product variant, and most official examples use RIPE NCC; customers using other RIRs should expect similar conceptual steps but slightly different tooling. All combinations should be validated with IONOS for each deployment. |
Automation & Developer Access
Abuse & Reputation Management
Related Resources
IONOS Cloud Homepage
VDC Networking (Network Services overview)
Bring Your Own IP (BYOIP) address to IONOS Cloud (VDC tutorial)
VDC Networking FAQ (includes BYOIP/BYOASN question)
Service Catalog (locations, IP Management, External Network capacity)
Private Cloud Documentation Hub
Requirements for BYOIP & BYOASN
Private Cloud: Using BYOIP in NSX
Letter of Authorisation (LoA, UK example)
Cloud API SDKs (Go, Java, Ruby, Python, NodeJS)
IonosCloud Terraform Provider
ionosctl CLI Documentation
IONOS Cloud Support