Catalyst Host BYOIP Integration Overview
Searching for the best IP providers? Catalyst Host supports BYOIP on its vDedi VPS plans through two separate routes: a portal import that announces your IPv4 block from Catalyst's own AS393336, and a customer BGP option for announcing from your own ASN. The two are documented differently, so choose the route before planning authorisation, allocation and migration.
BYOIP is included with vDedi plans, which start at $29/mo, with no separate setup fee. The portal import takes a /20 to /24 at a single location and caps how many addresses each VM can hold.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Catalyst Host LLC |
| Website | catalysthost.com |
| ASN(s) | AS393336 for the portal import, registered to Catalyst Host LLC at ARIN. Customer BGP uses your own ASN. |
| BYOIP Scope | vDedi VPS plans. The BYOIP claims are made for vDedi; do not assume they extend to every Catalyst VPS line. |
| Supported Versions | IPv4: yes, through the portal import. IPv6: the BGP product advertises /48 support, but the import guide covers IPv4 only. |
| Regions Supported | Not published as a list. The portal marks which locations can announce BYOIP space when you pick a VM. |
| Support Contact | Catalyst Host contact page |
Caveats and Gotchas
- Two workflows, two rulebooks: the BGP product page mentions an LOA and matching IRR records, while its description of the portal says no LOA paperwork is needed. Confirm which applies to the route you choose.
- One location per block: every subnet of an imported block stays at the location where it was first routed. Multi-POP announcement is described for the BGP product, not for the portal import.
- Per-VM caps: VMs with 32 GB of RAM or more take up to 1,536 addresses, 16 GB up to 1,024, 8 GB up to 512 and smaller VMs up to 128, in subnets no larger than /25.
- Leased space: the BGP page mentions leased or RIR-assigned space and names ARIN, RIPE and APNIC as examples. A complete acceptance policy is not published.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | /20 to /24 for the portal import. A /24 is the smallest. |
| ASN Ownership Required | No for the portal import, which is originated from AS393336. Customer BGP is a separate option for your own ASN. |
| RPKI ROA | Required for the portal import: a valid ROA authorising AS393336, created at your RIR before you start. |
| LOA | Conflicting. The BGP product page mentions one; the portal description says no LOA paperwork. |
| IRR Route Object | Matching IRR records are mentioned for the BGP product. Not stated for the portal import. |
| Validation | The portal checks the ROA, prefix format and reserved space, and warns if the prefix is still announced elsewhere. |
| RIR Limitations | Not published as a complete list. |
| Ownership Proof | The ROA check is the documented control test for the portal import. Any further documentation for leased prefixes is not published. |
Step-by-Step BYOIP Process
activate an eligible vDedi VPS and decide between the portal import and customer BGP.
for the portal import, create a ROA for AS393336 at your RIR.
stop any existing announcement of the prefix.
add the block in the BYOIP portal and let it run its checks.
route the block to one VM or split subnets across eligible VMs at the same location, then deploy the pending changes.
Withdrawal and Deprovisioning
Remove a block's subnets before deleting the block. Deleting it withdraws the routes and removes its reverse DNS zones. A withdrawal time and the steps for ending a customer BGP session are not published.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Included with vDedi plans, with no separate BYOIP setup fee. |
| Required Infrastructure | A vDedi plan, from $29/mo. Confirm tax treatment and the order total at checkout. |
| DDoS Protection | Coverage of imported prefixes is not published. |
| Other Limitations | Eligible locations, the maximum number of blocks per account and IPv6 limits are not published. Setup time is not published. |
Automation & Developer Access
- Portal: block validation, routing, subnet allocation and deployment are handled in the BYOIP portal.
- API: no BYOIP-specific API, CLI, Terraform provider or SDK is published.
- Reverse DNS: the portal creates one reverse zone per /24. Delegate those zones at your RIR to the nameservers shown, then edit PTRs in the portal or point the zone at your own nameservers. Switching to your own removes portal-managed PTR records.
Abuse & Reputation Management
- Acceptable use: the published AUP prohibits spam and open relays, restricts Tor relays and exits on VPS, and makes the customer responsible for downstream activity. Its revision date is 8 December 2014, so confirm it is the policy that applies to your order.
- Reputation: reputation cleanup and an abuse-response time for imported space are not published.
Frequently Asked Questions
Related Resources
Published 29 September 2026