HypeHost BYOIP Integration Overview
Searching for the best IP providers? HypeHost announces customer IPv4 and IPv6 prefixes from its data centre in Brazil, across VPS, bare metal and colocation. BGP is included on every plan with no setup fee, and prefixes can be split across several HypeHost servers for anycast or redundancy. You can bring your own ASN, and the product page also offers announcement from the HypeHost ASN.
HypeHost's product page and its BGP help article disagree on some allowances and on whether an ASN is required, so match your order to a confirmed configuration. DDoS protection is a paid add-on, and without it an attacked prefix is blackholed.
Provider Details
| Field | Information |
|---|---|
| Provider Name | HypeHost, a brand of JSK CLOUD E INFRAESTRUTURA LTDA (CNPJ 53.748.621/0001-14) |
| Website | hypehost.com.br |
| ASN(s) | Own ASN or the HypeHost ASN. The HypeHost ASN number is not published on the BYOIP page. |
| BYOIP Scope | BGP and BYOIP on VPS, bare metal and colocation, including mixed setups across several servers. |
| Supported Versions | IPv4: yes. IPv6: yes. |
| Supported Services | VPS, bare metal servers, colocation. |
| Regions Supported | Brazil. The São Paulo business address (Avenida Paulista 1471) is a company contact, not a data centre location; confirm the facility for your order. |
| Support Contact | hypehost@jeskesolutions.net, the customer area and the control panel |
Caveats and Gotchas
- VPS allowance conflict: the product page gives two IPv4 plus two IPv6 prefixes free on VPS, while the help article gives two prefixes per server. Confirm the allowance for both address families.
- ASN conflict: the BGP help article requires your own ASN, while the product page offers announcement from the HypeHost ASN. Treat the no-ASN option as something to confirm in writing.
- Protected-prefix allowance: the product page says the AntiDDoS add-on unlocks one prefix and one ASN; the help article says one IPv4 and one IPv6 prefix with one ASN.
- Blackholing: a prefix without the paid AntiDDoS add-on is blackholed automatically if it is attacked.
- No remote shielding: an ordinary VPS must not be used to protect outside servers through tunnels or proxies, and reselling mitigation is prohibited. Remote protection is a separate service.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | Minimum /24 for IPv4 and /48 for IPv6, per the help article. Larger-block limits are not published. |
| ASN Ownership Required | Conflicting; see the caveats. The documented BGP path uses your own ASN. |
| Infrastructure | An active HypeHost server. |
| LOA | Not published. |
| RPKI ROA | Not published. |
| IRR Route Object | Not published. |
| RIR Limitations | Not published, including whether leased prefixes are accepted. |
| Routing Features | Traffic-engineering communities and blackhole. Downstreams are supported within a per-account limit; the limit itself is not published. |
Step-by-Step BYOIP Process
have an active server, an eligible prefix and, for the documented BGP path, your own ASN.
obtain the session IPs, ASN, password and authorised-prefix list from HypeHost.
run BIRD, FRR, GoBGP or OpenBGPD yourself, or ask for a managed session where HypeHost staff make the changes.
Withdrawal and Deprovisioning
No public withdrawal or cancellation procedure was found. Agree withdrawal timing, managed-session changes and authorisation cleanup with HypeHost before cancelling the infrastructure.
Cost and Limitations
| Item | Details |
|---|---|
| BGP Setup | No setup fee. Infrastructure is charged separately. |
| Extra VPS Prefixes | R$ 150.00/mo per prefix beyond the free allowance. |
| Bare Metal and Colocation | Unlimited free announced prefixes. That does not mean unlimited protected traffic. |
| AntiDDoS Add-On | R$ 800.00/mo base, then R$ 250.00/mo per protected prefix and R$ 500.00/mo per additional ASN. Confirm tax and whether these stack with the ordinary prefix fee. |
| Other Limitations | Activation time, the downstream limit and the exact facility are not published. |
Automation & Developer Access
- Portal: a customer area and control panel exist; BGP runs on your own routing software or as a staff-managed session.
- API: no BYOIP provisioning API or infrastructure-as-code module is published. The routing daemons are not a vendor API.
- Reverse DNS: delegation and PTR controls for imported space are not published.
Abuse & Reputation Management
- Not published: blocklist monitoring, delisting responsibility and an abuse-response time for imported blocks.
- Attack handling: the blackhole behaviour and remote-protection restrictions above still apply to imported prefixes.
Frequently Asked Questions
Related Resources
Published 29 September 2026