Netrouting BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) and Bring Your Own ASN (BYOASN) with Netrouting infrastructure. Netrouting supports two primary models: (1) provider-announced BYOIP/BYOASN (Netrouting’s ASN 6206 originates your IPv4/IPv6 prefixes and, optionally, your ASN) and (2) customer-managed BGP sessions using virtual routers (you run Nokia VSR or VyOS on Netrouting’s optimized cloud compute and announce your prefixes yourself).
Provider Details
| Field | Information |
|---|---|
| Provider Name | Netrouting |
| Website | BYOIP & BYOASN on Netrouting (No Router Required) | Reseller Program (white-label + BYOIP/BYOASN) | Data Centers | Service & Support |
| ASN(s) | AS6206 (Netrouting B.V.) is the primary backbone ASN for BYOIP/BYOASN announcements. |
| Regions Supported | Global backbone with data centers in: Amsterdam (NL), The Hague/Rotterdam (NL), Frankfurt (DE), Stockholm (SE), Bucharest (RO), Miami (US), Hong Kong (HK). BYOIP/BYOASN is available across Netrouting’s bare metal footprint in these locations (subject to design and approval). |
| Support Contact | Contact Netrouting | Phone: +31 (0)88-045-4600 (EU) / +1-305-705-6983 (US) | Email: sales@netrouting.com | Abuse desk: abuse@netrouting.com |
| Tech Article & Date | BYOIP & BYOASN on Netrouting: Bring Your Own IPs and ASN - No Router Required (Knowledge Base, Aug 13, 2025). |
| BYOIP Scope | Provider-announced BYOIP/BYOASN: Netrouting originates your IPv4/IPv6 prefixes on AS6206; you supply LOA and (optionally/ideally) ROAs. You do not need to run your own router. Customer-managed BGP: Run Nokia VSR or VyOS as virtual routers on Netrouting’s Optimized Cloud Compute and establish eBGP sessions with AS6206 to originate your prefixes under your own ASN and routing policy. |
| Supported Versions | IPv4 & IPv6. BYOIP article explicitly references “your IPv4/IPv6 prefixes”. RPKI/ROA support is recommended and supported for both. |
| Supported Services | Bare Metal Dedicated Servers (all bare metal customers can use BYOIP/BYOASN; free for resellers), with the option to deploy virtual routers (Nokia VSR, VyOS) on Optimized Cloud Compute for full BGP control. BYOIP is also relevant to reseller/white-label hosting, VPN providers, gaming, streaming and other high-bandwidth use cases described by Netrouting. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | The BYOIP/BYOASN article describes support for IPv4/IPv6 prefixes but does not specify minimum prefix sizes. In practice, customers should expect standard global routing constraints (e.g. IPv4 /24 or larger, IPv6 /48 or larger) and confirm acceptable sizes with Netrouting during onboarding. |
| ASN Ownership Required | Provider-announced BYOIP: No - you can use your own IP space without operating your own ASN; Netrouting originates your prefixes from AS6206. BYOASN / ASN branding: Yes - if you want your own ASN to appear as origin, you must own an ASN; Netrouting can announce via their backbone “without deploying your own edge router”, or you can run full BGP yourself on VSR/VyOS. |
| IRR / Route Objects | Netrouting requires proof of IP prefix ownership (such as RIR/WHOIS registry objects). Standard IRR best practices apply. The LOA template explicitly authorizes Netrouting (AS6206) to originate your listed prefixes/ASNs; customers should ensure their IRR/RPKI objects match the intended origin. |
| ROA or LOA | LOA: Required. A signed Letter of Authorization on company letterhead is required before Netrouting will announce your prefixes or ASN. The KB provides a full LOA template and states that AS6206 must be authorized to originate the space. ROA (RPKI): Strongly recommended. Netrouting recommends publishing ROAs for your ASN and prefixes; the quick-start flow explicitly mentions providing ROA details “if applicable”. |
| RIR Limitations | Prefixes must be properly registered with a recognized RIR and clearly associated with the customer. Netrouting validates ownership via WHOIS/registry data and requires that authorization in the LOA be consistent with registry records. No further region-specific RIR limitations are documented. |
Step-by-Step BYOIP Process
Estimated Setup Time:Not explicitly documented. Operationally, once LOA is approved and announcements are configured on Netrouting’s edge, global BGP convergence typically occurs within < 24 hours.Tested By Us:Not yet
A) Provider-Announced BYOIP/BYOASN (No Router Required)
Step 1
Prepare and sign a Letter of Authorization (LOA) on your organization’s letterhead, authorizing Netrouting (AS6206) to originate your specified IP prefixes and, if desired, your ASN.
Step 2
Open a support ticket via the Netrouting client portal and attach the LOA (and RPKI/ROA details if already published).
Step 3
In the ticket, specify origin ASN, any requested BGP communities, and routing policy preferences (prepends, export preferences, etc.).
Step 4
Netrouting validates ownership and authorization, configures announcements on its edge routers, and enables your prefixes for use across your bare metal footprint.
Step 5
You verify reachability (BGP looking glasses, RIPEstat, etc.), update DNS/reverse DNS and any geolocation or allowlists to reference your new Netrouting-hosted paths.
Step 6
Order Optimized Cloud Compute instances sized for network-function workloads and deploy Nokia VSR or VyOS images provided by Netrouting (Proxmox VE with dedicated NICs/SR-IOV).
Step 7
Request eBGP peering with AS6206 via a ticket, specifying your ASN, prefixes to be originated, and desired BGP communities/routing policies.
Step 8
Configure BGP on your VSR/VyOS virtual router to peer with Netrouting’s edge (neighbor IPs, ASN, passwords, communities, local-pref, etc.).
Step 9
Announce your BYOIPv4/BYOIPv6 prefixes under your ASN; Netrouting propagates these announcements across its backbone and upstream peers.
Step 10
Monitor global propagation using public BGP and routing tools; fine-tune communities and prepends as needed for traffic engineering.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | The BYOIP/BYOASN feature is explicitly listed as free for resellers and available to all bare metal customers. The article does not list extra recurring BYOIP surcharges; any non-standard routing or engineering work should be confirmed with Netrouting Sales. |
| Bundled or Standalone | Offered as part of Netrouting’s infrastructure stack: not sold as a standalone network-only product. BYOIP/BYOASN is tied to bare metal dedicated servers, with optional virtual routers on Optimized Cloud Compute, and is heavily integrated into the reseller/white-label hosting model. |
| Traffic/Peering Restrictions | Customers must comply with Netrouting’s Acceptable Use Policy. Netrouting runs a global multi-upstream backbone (AS6206) with network-level DDoS protection; abuse or policy violations may result in mitigation measures (including null-routing of specific IPs). |
| Other Limitations | BYOIP/BYOASN is documented for bare metal servers and reseller use cases. Customers who want full routing control should deploy VSR/VyOS; otherwise Netrouting manages announcements. Exact prefix size/quantity limits and any per-deployment constraints are set during solution design and may depend on network capacity and abuse/risk profile. |
Automation & Developer Access
- API Access: Yes - Netrouting highlights a “versatile API access” and a dedicated <a href="https://netrouting.com/product-api-docs/" target="_blank" rel="noreferrer noopener">Product & API Docs</a> section; automation is generally done via the client portal + API and support tickets for BYOIP/BYOASN onboarding.
- Client Portal: Full management of bare metal, cloud, tickets, and networking features; BYOIP/BYOASN configuration is coordinated via tickets and Netrouting engineers.
- Virtual Routers: Nokia VSR and VyOS images on Optimized Cloud Compute provide programmable BGP edge devices for advanced policy control and automation (communities, prepends, filtering).
- No public Terraform/SDK specifically documented for BYOIP as of the article date; infrastructure automation is typically via API + standard router automation (Ansible, scripts) on VSR/VyOS.
Abuse & Reputation Management
- Netrouting has a formal abuse process documented in “How to report Network Abuse to Netrouting”; abuse reports are sent to <a href="mailto:abuse@netrouting.com" target="_blank" rel="noreferrer noopener">abuse@netrouting.com</a> and processed by an automated system.
- Customers are required to respond and take corrective action within defined timeframes (e.g. 48 hours per abuse documentation); failure to comply may lead to traffic mitigation such as null-routing the reported IPs.
- BYOIP holders remain responsible for the <strong>reputation and cleanliness</strong> of their prefixes (SPAM/abuse listings, geolocation records, allowlists, etc.); Netrouting provides network-level DDoS protection but does not manage third-party reputation databases on behalf of the customer.