Skip to content

HOSTKEY BYOIP Integration Overview

BYOIP SUPPORTER
ASN 395839
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: Singapore, Germany, Netherlands, United Kingdom

Searching for the best IP providers? HOSTKEY supports Bring Your Own IP (BYOIP) for dedicated and colocated servers. Current public documentation shows IPv4 BYOIP requests handled through the Invapi/My Networks workflow, while IPv6 announcements are requested separately via the website with an attached LOA. HOSTKEY supports announcements from its own ASN or from the customer’s ASN via BGP, offers free initial setup, and includes reverse DNS support. Below you’ll find the current setup flow, requirements, limitations, and support links.

Provider Details

FieldInformation
Provider NameHOSTKEY
WebsiteHOSTKEY Website
ASN(s)AS395839 (HOSTKEY ASN); custom ASN supported via BGP
Regions SupportedNot explicitly enumerated in HOSTKEY’s BYOIP documentation; available for corresponding HOSTKEY dedicated and colocated server locations
Support ContactHOSTKEY Support
Tech Article & DateMy Networks menu section and subnet management – February 27, 2026
Bring your IP addresses (BYOIP) or AS for free – Date not specified
BYOIP ScopeAvailable for dedicated and colocated servers; not available for VPS/VDS
Supported ServicesDedicated Servers, Colocated Servers

Technical Requirements

RequirementDetails
Supported VersionsIPv4 supported via Invapi/My Networks workflow; IPv6 requests handled separately via website BYOIP request with LOA
Prefix SizeIPv4: /23 or /24 in the documented Invapi flow; IPv6: size not explicitly stated in the public BYOIP docs
ASN Ownership RequiredOptional; customers may use HOSTKEY’s ASN (AS395839) or their own ASN via BGP
IRR or RADb ObjectNot explicitly stated in the public documentation
ROA or LOALOA required; public docs do not explicitly require ROA
RIR LimitationsSupport for ARIN and RIPE IP address ranges is explicitly mentioned

Step-by-Step BYOIP Process

  • Choose the Request Path: For IPv4, submit the request in Invapi via My Networks. For IPv6, use the website BYOIP request form with an attached Letter of Authorization (LOA).
  • Select Server and Subnet: In the IPv4 control-panel flow, choose the dedicated server and enter the subnet with mask /23 or /24. The subnet must end with .0.
  • Choose ASN and Routing: Use HOSTKEY’s ASN or specify your own ASN. Depending on the method, choose announcement via HOSTKEY routers or set up a BGP session with the server.
  • Upload LOA and Confirm: Upload the LOA in PDF format (up to 1 MB), confirm the request details, and submit. HOSTKEY reviews the request and may contact you for clarification.
  • Routing Completion: HOSTKEY either announces the block from its ASN or peers with your BGP speaker, then routes the block to your server directly or to your private VLAN, depending on the configuration.

Cost and Limitations

ItemDetails
FeesInitial setup: Free; monthly fee: €0; subsequent announcement changes: €70 per request
Bundled or StandaloneUsed with dedicated or colocated servers
Traffic/Peering RestrictionsAnnouncements may be terminated for Terms of Service violations or if the subnet appears in Spamhaus or other blocklists
Other LimitationsAvailable to verified clients only; IPv4 control-panel flow is limited to one /23 subnet or two /24 subnets per server; VPS/VDS not supported

Automation & Developer Access

  • Control Panel Integration: HOSTKEY states BYOIP is fully integrated into the control panel, and the current IPv4 onboarding flow is documented in Invapi/My Networks.
  • Routing Options: The documented flow supports static routing, gateway setup on HOSTKEY routers, or BGP session setup with the server, depending on the selected AS and announcement method.
  • Terraform/SDK/API: Public BYOIP automation endpoints are not explicitly documented; treat the process as control-panel-driven with manual review by HOSTKEY support.

Abuse & Reputation Management

  • Reverse DNS Support: Explicitly supported by HOSTKEY for BYOIP deployments.
  • Blacklist Handling: HOSTKEY may refuse or stop announcing subnets that are listed in Spamhaus or other blacklists.
  • IP Reputation Monitoring: No dedicated monitoring or blacklist-removal service is described in the public BYOIP documentation.

HOSTKEY Control Panel BYOIP / My Networks Documentation
HOSTKEY BYOIP Service Overview

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.