Tempest Hosting BYOIP Integration Overview
Searching for the best IP providers? Tempest Hosting documents BGP and BYOIP on its Enterprise Dedicated servers, set up through a ticket in its customer portal, and allows customers to announce their own ASN and address space. Plan eligibility is where the evidence is weakest: Tempest's help centre carries two conflicting versions of its BGP/BYOIP article, and both exclude Virtual Dedicated Servers.
Very little else is published. Prefix requirements, authorisation documents, fees and setup time all need to be confirmed with Tempest before you order.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Tempest Hosting, LLC, as named in the help centre. Confirm the entity that signs your order. |
| Website | tempest.net |
| ASN(s) | Not published in the BYOIP material. Announcing your own ASN is permitted. |
| BYOIP Scope | BGP and BYOIP on Enterprise Dedicated servers, arranged through a support ticket. |
| Supported Versions | IPv4: yes, per older guidance with a /24 minimum. IPv6: not published for BYOIP. |
| Supported Services | Enterprise Dedicated servers. |
| Not Supported | Virtual Dedicated Servers. Cost-optimised or budget dedicated plans are unresolved; see the caveats. |
| Regions Supported | Not published for BYOIP. The ordinary server inventory lists London, Dallas, Miami, Amsterdam and Sydney, but these are not individually confirmed BYOIP locations. |
| Support Contact | Tempest contact page and the customer portal for setup tickets |
Caveats and Gotchas
- Conflicting help-centre versions: the newer indexed version of the BGP/BYOIP article supports Enterprise Dedicated only. An older retrieved version supported dedicated servers generally and allowed budget dedicated plans with a three-server minimum. Get written confirmation for any plan other than Enterprise Dedicated.
- Low-confidence evidence: the help centre could not be opened directly during research, so the plan wording above rests on indexed and previously retrieved copies of the article.
- Older terms: the /24 minimum and the statement that own AS and IP use carries no extra charge come from a 2022 article. Reconfirm both against the current Enterprise service.
- Delivery time: the ordinary server delivery estimate is not a BYOIP setup time.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | /24 minimum, per older official guidance. Reconfirm. |
| ASN Ownership Required | Announcing your own ASN is permitted. Whether an ASN is mandatory, or Tempest can originate for you, is not published. |
| LOA | Not published. |
| RPKI ROA | Not published. |
| IRR Route Object | Not published. |
| RIR Limitations | Not published, including whether leased prefixes are accepted. |
| Ownership Proof | Not published. |
| Contract or Commit | An eligible dedicated server; server charges are separate. |
Step-by-Step BYOIP Process
The documented entry point is a portal ticket. The preparation below is editorial guidance rather than a published Tempest runbook.
identify the exact Enterprise Dedicated plan and location.
request confirmation of prefix size, address family, origin ASN, leased-space eligibility and fees.
ask support which authorisation documents and routing configuration the order needs.
agree an activation window and verify routing before moving production traffic.
Withdrawal and Deprovisioning
No public BYOIP withdrawal procedure was found. Agree withdrawal timing, cancellation and removal of routing authorisations with support before moving the prefix, and do not assume cancelling a server removes every announcement straight away.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Not published as current terms. A 2022 article says own AS and IP use has no additional charge; treat that as unconfirmed. |
| Bundled or Standalone | Tied to an eligible dedicated server. |
| DDoS Protection | Tempest markets always-on protection for its servers. Coverage of an imported prefix, and its limits, need confirming per order. |
| Other Limitations | Setup time, allocation model, BGP session parameters, maximum prefix count, anycast and multihoming are not published. |
Automation & Developer Access
- Portal: setup runs through a support ticket. Self-service route provisioning is not documented.
- API: no BYOIP API, CLI, Terraform provider or SDK is published.
- Reverse DNS: general help-centre guidance offers PTR setup by ticket once a forward A record exists. Delegation for customer space needs confirming.
Abuse & Reputation Management
- Not published: blocklist monitoring, remediation duties and abuse-response commitments for imported space. Ask for the current service terms and abuse process with the order.
Related Resources
Published 29 September 2026