HOSTKEY BYOIP Integration Overview
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
| Field | Information |
|---|---|
| Provider Name | HOSTKEY |
| Website | HOSTKEY Website |
| ASN(s) | AS395839 (HOSTKEY ASN); custom ASN supported via BGP |
| Regions Supported | Not explicitly enumerated in HOSTKEY’s BYOIP documentation; available for corresponding HOSTKEY dedicated and colocated server locations |
| Support Contact | HOSTKEY Support |
| Tech Article & Date | My Networks menu section and subnet management - February 27, 2026 Bring your IP addresses (BYOIP) or AS for free - Date not specified |
| BYOIP Scope | Available for dedicated and colocated servers; not available for VPS/VDS |
| Supported Services | Dedicated Servers, Colocated Servers |
Technical Requirements
| Requirement | Details |
|---|---|
| Supported Versions | IPv4 supported via Invapi/My Networks workflow; IPv6 requests handled separately via website BYOIP request with LOA |
| Prefix Size | IPv4: /23 or /24 in the documented Invapi flow; IPv6: size not explicitly stated in the public BYOIP docs |
| ASN Ownership Required | Optional; customers may use HOSTKEY’s ASN (AS395839) or their own ASN via BGP |
| IRR or RADb Object | Not explicitly stated in the public documentation |
| ROA or LOA | LOA required; public docs do not explicitly require ROA |
| RIR Limitations | Support for ARIN and RIPE IP address ranges is explicitly mentioned |
Step-by-Step BYOIP Process
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).
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.
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 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.
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
| Item | Details |
|---|---|
| Fees | Initial setup: Free; monthly fee: €0; subsequent announcement changes: €70 per request |
| Bundled or Standalone | Used with dedicated or colocated servers |
| Traffic/Peering Restrictions | Announcements may be terminated for Terms of Service violations or if the subnet appears in Spamhaus or other blocklists |
| Other Limitations | Available 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.