TermRat Network BYOIP Integration Overview
Worth Knowing
Eligible for supported non-Cloud services in Hong Kong only; TermRat explicitly excludes its Cloud product from BYOIP. Requires IPv4 /24 minimum and valid RPKI ROA.
Searching for the best IP providers? TermRat Network offers announcement of customer-held IPv4 space for supported non-Cloud services. Customers submit routing details through a ticket and must maintain valid RPKI authorization for the intended origin. Its published infrastructure location is Hong Kong. TermRat explicitly excludes its Cloud product from BYOIP eligibility.
Provider Details
| Field | Information |
|---|---|
| Provider Name | TermRat Network |
| Website | TermRat Network |
| ASN(s) | AS154648 (network identity; confirm the agreed route origin with TermRat before creating a ROA) |
| Regions Supported | Hong Kong |
| Tech Article & Date | TermRat BYOIP offering; Company & infrastructure overview - checked 6 November 2026 |
| BYOIP Scope | Supported non-Cloud services only (TermRat explicitly excludes its Cloud product from BYOIP) |
| Supported Versions | IPv4 (/24 minimum). IPv6 BYOIP is not established in the reviewed offering. |
Caveats and Gotchas
- Cloud product excluded: TermRat explicitly states that its Cloud product is not currently eligible for BYOIP; only supported non-Cloud services qualify.
- Valid RPKI authorization (ROA) for the intended origin ASN is required before allowlisting.
- TermRat does not charge a separate prefix-allowlisting fee, but underlying non-Cloud service charges apply separately.
- The published 1-2 business day allowlisting target applies after complete routing details and valid RPKI are in place; it is a target, not a completion SLA.
- Infrastructure footprint is Hong Kong; do not treat upstream reach through HKBGP or HKBGP-CN as multi-country deployment locations.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | IPv4: /24 minimum. IPv6 BYOIP is not established. |
| RPKI ROA | Required: valid RPKI authorization for the intended route origin. |
| LOA / IRR / Customer ASN | Exact requirements not established in the summary page; confirm in your client-account ticket. |
| Fees | No separate TermRat prefix-allowlisting fee; underlying service charges apply. |
| Timing | 1-2 business days allowlisting target once complete details and valid RPKI are verified. |
Step-by-Step BYOIP Process
Step 1
Verify that your deployment uses an eligible non-Cloud TermRat service in Hong Kong (Cloud instances are excluded).
Step 2
Publish a valid RPKI ROA for your IPv4 /24 (or larger) prefix matching the agreed origin ASN.
Step 3
Open a ticket in your TermRat client account with your prefix and routing details.
Step 4
Wait for prefix allowlisting (targeted within 1-2 business days after RPKI verification) and confirm route announcement.
Related Resources
Published 6 November 2026