HostHatch BYOIP Integration Overview
Worth Knowing
AS65473 is a private session ASN, not the public provider identity. Locations must be confirmed with support. /32 and /128 are more-specifics inside an authorized prefix, not a minimum Internet prefix. Fees, a ROA requirement and a customer-ASN rule are not documented.
Searching for the best IP providers? HostHatch documents customer-prefix announcements through BGP on its virtual servers. Support must enable the service before you configure it. Availability depends on location and the feature is still under development, so do not treat the whole datacenter list as BYOIP coverage.
Provider Details
| Field | Information |
|---|---|
| Provider Name | HostHatch |
| Website | hosthatch.com |
| ASN(s) | The public provider ASN is not in the BGP section. AS65473 is a private session ASN, not the public network identity. |
| Regions Supported | Not published as a BYOIP country list. Confirm available locations with support. |
| Tech Article & Date | HostHatch networking, BGP section - checked 6 October 2026 |
| BYOIP Scope | Customer prefixes announced by BGP from a virtual server, after support enables the session. |
| Supported Versions | IPv4 and IPv6 are both in the BGP configuration. Default routes are supplied for both families. |
| Supported Services | Virtual servers, where support has enabled BGP. |
Caveats and Gotchas
- Do not copy HostHatch's datacenter footprint into a BYOIP location list. Ask support which sites can take the session.
- /32 and /128 routes are allowed inside an authorized prefix. They are not the minimum size you can advertise to the Internet. The full authorized prefix must also be announced from at least one server for Internet propagation.
- Fees, a ROA requirement and whether a customer ASN is mandatory are not established by this source.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | A minimum Internet prefix length is not established. More-specifics of /32 and /128 are allowed inside an authorized prefix. |
| ASN Ownership Required | Not established. Do not assume a customer ASN is required. |
| LOA | The guide refers to LOA-authorized prefixes. |
| RPKI ROA | Not documented. |
Step-by-Step BYOIP Process
Step 1
Contact support and ask for BGP on the virtual server.
The session is not self-serve.
Step 2
Receive activation and session details, including the private session ASN if one is assigned.
Step 3
Configure a BGP client.
Announce the full authorized prefix from at least one server if you also announce more-specifics.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Not documented in the BGP section. |
| Other Limitations | Location availability is limited and the feature remains under development. |
Related Resources
Published 6 October 2026
More BYOIP supporters
All BYOIP supporters- Akamai Prolexic BYOIP Integration Overview
- F5 Distributed Cloud DDoS Mitigation BYOIP Integration Overview
- Imperva DDoS Protection for Networks BYOIP Integration Overview
- Radware Cloud DDoS Protection BYOIP Integration Overview
- NETSCOUT Arbor Cloud BYOIP Integration Overview
- Link11 BYOIP Integration Overview