Skip to content

Hivelocity BYOIP Integration Overview

BYOIP SUPPORTER
ASN 29802
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: India, Japan, Singapore, United Arab Emirates, Hong Kong, France, Germany, Italy, Netherlands, Poland, Spain, Sweden, United Kingdom, Canada, Mexico, United States, Brazil, Chile, Colombia, Australia

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Hivelocity infrastructure. Hivelocity operates a global hosting platform (dedicated servers, VPS, private cloud and colocation) and supports Border Gateway Protocol (BGP) for route advertisements. In practice, BYOIP with Hivelocity is implemented as a classic BGP model: you bring a publicly routable IPv4 and/or IPv6 prefix (customer-owned space), Hivelocity enables BGP on your account, and your prefix is then advertised and used with Hivelocity services. Hivelocity supports BYOIP with IPv4 and IPv6, and you can advertise prefixes with or without your own ASN, depending on your routing design and the onboarding agreed with Hivelocity networking.

Provider Details

FieldInformation
Provider NameHivelocity
Website Hivelocity Homepage | Developer Docs: BGP (BYOIP & IPv4/IPv6 routing) | Developer Portal: Getting Started (API / account) | Products (Dedicated, Cloud, Colocation) | Knowledge Base | Legal / Policies
ASN(s) Hivelocity’s public ASNs and routing details vary by region and facility. For BYOIP, Hivelocity’s BGP design supports advertising your prefixes with or without your own ASN (customer ASN optional). Exact peering parameters (peer IPs, MD5, max-prefix, communities if used) are provided during onboarding by Hivelocity networking.
Regions Supported Hivelocity operates in 50+ global locations across multiple continents and offers dedicated servers, VPS, private cloud, and colocation. BYOIP availability is tied to BGP enablement and network capabilities in the target region(s). Confirm the exact BYOIP/BGP availability per facility during onboarding (especially for multi-region/anycast designs).
Support Contact BYOIP / BGP enablement requires coordination with Hivelocity. Start with:
– Email: sales@hivelocity.net (BYOIP/BGP enablement request)
Contact / Sales | – Knowledge Base (operations & platform docs)
Tech Article & Date Developer Docs: BGP — documents BGP support, confirms advertising IPv4 and IPv6, and explicitly states that customers can bring their own publicly routable IPv4 or IPv6 range and advertise it using BGP, with or without their own ASN. It also notes that IP subnets can be managed via the Hivelocity API and portal, and that customers should contact sales to enable the functionality.
BYOIP Scope Hivelocity BYOIP is a BGP-based hosting/colo BYOIP model (not a hyperscaler-style “import prefix” resource):
1) Customer-owned prefixes via BGP (classic BYOIP): You bring one or more publicly routable IPv4 and/or IPv6 prefixes and advertise them over BGP through Hivelocity. Your addresses are then used for services hosted at Hivelocity (dedicated servers, VPS, private cloud, gateways) while preserving your ownership and reputation controls.
2) Customer ASN optional: Hivelocity supports advertising BYOIP prefixes using BGP with or without your own ASN, depending on the design agreed with Hivelocity networking.
Supported Versions Hivelocity supports BYOIP for:
IPv4 — customer-owned publicly routable ranges announced via BGP.
IPv6 — customer-owned publicly routable ranges announced via BGP.
Minimum prefix sizes are not publicly standardized on their BGP page; expect typical global routing minimums (e.g., /24 for IPv4 and /48 for IPv6) unless Hivelocity confirms otherwise for your design.
Supported Services BYOIP concepts apply primarily to services that rely on publicly routable addressing at Hivelocity, including:
– Dedicated servers and bare metal deployments
– VPS / virtualized server products (where public IPs are supported)
– Colocation and hybrid deployments (customer routing into Hivelocity edge)
– Private cloud and custom architectures where BGP-routed prefixes are required for identity, allowlisting, reputation, or continuity

Technical Requirements

RequirementDetails
Prefix Size Hivelocity supports BYOIP for publicly routable IPv4 and IPv6 ranges. The BGP documentation does not publish fixed minimums; in practice, you should assume common internet routing minimums unless Hivelocity confirms exceptions:
– IPv4: typically /24 or larger
– IPv6: typically /48 or larger
Provide the exact prefixes to Hivelocity during onboarding so they can confirm acceptability and routing policy.
ASN Ownership Required Not strictly required. Hivelocity states you can advertise BYOIP prefixes using BGP with or without your own ASN. If you have your own ASN, you can typically maintain stronger routing control and multi-homing options; if you do not, Hivelocity can support alternate designs depending on their network policy.
IRR / Route Objects Expect standard routing hygiene requirements for third-party prefix advertisements:
– Maintain correct RIR registration for your organization and ensure the prefix is not in dispute.
– Maintain IRR route objects consistent with the intended origin ASN (your ASN or the ASN used in the agreed design).
These artefacts reduce onboarding friction and prevent upstream filtering.
ROA or LOA Prepare to provide common authorization artefacts during BYOIP onboarding:
RPKI ROA (recommended) authorizing the correct origin ASN(s).
Letter of Authorization (LOA) permitting Hivelocity to announce and use your prefix in its network, if requested.
Exact validation steps and preferred artefacts are confirmed by Hivelocity during onboarding.
RIR Limitations BYOIP space must be globally routable public IPv4/IPv6 and properly registered in an RIR (ARIN, RIPE, APNIC, LACNIC, AFRINIC). You must be able to update WHOIS/RDAP, IRR objects, and ROAs where needed. Overlapping announcements from other providers should be removed or coordinated to avoid routing conflicts.

Step-by-Step BYOIP Process

Estimated Setup Time: Typically a few days to a few weeks, depending on validation (RIR/ROA/IRR), network design (single site vs multi-site), and coordination between your routing team and Hivelocity networking.

Tested By Us: Not yet

A) BYOIP prefixes via BGP (standard model)

  • Engage Hivelocity sales/support to confirm BYOIP/BGP is enabled for your account and to scope the deployment (dedicated servers, VPS, private cloud, colo; single facility vs multi-facility; anycast requirements if applicable).
  • Prepare your public IPv4 and/or IPv6 prefixes and verify that the space is registered to your organization, is publicly routable, and aligns with standard global routing minimums. Collect any existing IRR route objects and RPKI ROAs for the prefixes.
  • Decide whether you will advertise prefixes with your own ASN or use a design where a customer ASN is not required. Provide the intended origin ASNs and routing policy details to Hivelocity for review.
  • Exchange BGP parameters with Hivelocity networking: peer IPs, ASNs, authentication (MD5 if used), maximum-prefix limits, and any operational controls (for example blackhole handling under DDoS). Provide LOA/ROA/IRR artefacts as requested.
  • Bring up BGP in a staging environment first, announce test routes (or limited prefixes), and validate reachability, failover behaviour, geolocation expectations, and application allowlists. Adjust policies as needed with Hivelocity.
  • Once stable, move to production: announce the intended BYOIP prefixes, attach BYOIP addresses to servers/services, and manage IP subnets through the Hivelocity portal and API as part of normal day-2 operations. Monitor BGP session health and prefix visibility continuously.

References: Hivelocity Developer Docs: BGP, Developer Portal: Getting Started, Hivelocity Products, Resources, Knowledge Base.

Cost and Limitations

ItemDetails
Fees Hivelocity does not publish a universal public BYOIP price list in the BGP documentation. In practice, BYOIP/BGP enablement may involve:
– Setup and/or monthly recurring fees (design dependent).
– Cross-connects or port fees for colocation routing designs.
– Bandwidth / commit charges for transit and DDoS-related services, if applicable.
Confirm exact pricing and commercial constraints with Hivelocity sales when requesting BYOIP/BGP enablement.
Bundled or Standalone BYOIP at Hivelocity is typically bundled with hosting, cloud, or colocation usage. It is not generally a standalone route-origin service; you use BYOIP addresses in conjunction with servers, private cloud, gateways, or colo infrastructure hosted at Hivelocity.
Traffic/Peering Restrictions – BYOIP prefixes must be legitimate and cleanly routable; Hivelocity may refuse prefixes with heavy abuse history or routing conflicts.
– Route filtering, maximum-prefix limits and deaggregation controls are typically enforced to protect network stability.
– Use of certain traffic types may be restricted by acceptable use policies and abuse handling requirements.
Other Limitations – BYOIP/BGP requires networking coordination and is therefore not fully self-service; expect enablement via sales/support tickets.
– Multi-site announcements (anycast or multi-region) require explicit design and validation by Hivelocity networking.
– Customers remain responsible for IP reputation, upstream allowlists, and maintaining RIR/IRR/RPKI correctness for their prefixes.

Automation & Developer Access

  • API Access: Yes — Hivelocity provides a public Developer Portal and API. Once BYOIP/BGP is enabled and your prefixes are onboarded, you can manage IP subnets through the Hivelocity API and portal as part of normal operations.
  • Portal: Hivelocity’s management portals (including myVelocity) support operational workflows such as IP management, monitoring and account administration. BYOIP day-2 operations are typically performed through the same tooling used for standard IP allocations.
  • BGP as control plane: For BYOIP routing policy itself, automation is normally implemented by the customer through BGP configuration management (for example Ansible/NetBox/GitOps for router configs) using the peering parameters supplied by Hivelocity.
  • Support-assisted onboarding: Prefix onboarding and BGP enablement are coordinated with Hivelocity networking; once enabled, ongoing IP/subnet management can be automated through API and standard network automation practices.

Abuse & Reputation Management

  • For BYOIP prefixes, the customer retains responsibility for long-term reputation, blacklist status and compliance for traffic originating from the prefix. Hivelocity may provide abuse notifications and operational assistance, but delisting, reputation recovery and upstream allowlist coordination remain customer tasks.
  • Maintain strong routing security hygiene: keep RIR registrations current, publish accurate IRR route objects, and maintain RPKI ROAs that authorize the correct origin ASN(s). Misconfigured ROAs or invalid registry data can cause reachability failures or route filtering.

Hivelocity Homepage
Developer Docs: BGP (BYOIP, IPv4/IPv6, ASN optional)
Developer Portal: Getting Started
Products (Dedicated, VPS, Cloud, Colocation)
Company History
Resources
Knowledge Base
Legal / Policies

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.