Most hosting journeys start with a single VPS. You deploy a server, point DNS at it, install your application and get online. For a website, Discord bot, small API, VPN, monitoring tool or personal project, that is often enough.

As projects grow, the network starts to matter. You may need your own ASN, routed IPv6, an IP transit session, customer prefixes, private networking or more control over how traffic enters and leaves your infrastructure.

That is where BGP comes in, and that is why HYEHOST built BGP and network automation directly into the custom HYEHOST panel. This guide explains how customers can move from a normal VPS setup to more advanced routing using HYEHOST services and panel-managed workflows.

What BGP does

BGP, or Border Gateway Protocol, is the routing protocol used between networks on the internet. Instead of simply pointing a domain name at one server, BGP allows networks to announce that an IP prefix is reachable through a specific autonomous system number, known as an ASN.

The important terms are worth getting comfortable with before enabling a session:

  • ASN: your network identity, such as AS47272 for HYEHOST.
  • Prefix: the IPv4 or IPv6 range being routed.
  • Peer: the router or network you exchange routes with.
  • IRR: Internet Routing Registry records used by networks to validate routing policy.
  • RPKI / ROA: cryptographic route authorization used to prove an ASN is allowed to announce a prefix.
  • Import limit: a safety limit controlling how many routes your session can send to HYEHOST.
  • Export policy: the routes HYEHOST sends to your session, such as default route, default plus local routes or full table where available.

BGP is powerful, but it should be used only when you actually need routing control. If DNS and a single VPS solve the problem, keep the design simple.

When a normal VPS is enough

If you are hosting one application, one website, one bot or one simple service, you usually do not need BGP. A normal HYEHOST Cloud VPS, Budget VPS, Windows VPS or VDS Hosting gives you the basics: power controls, OS reinstall, serial or VNC console, bandwidth graphs, add-on options, billing controls, support tickets and optional private LAN features.

For many users, DNS plus a VPS is the right starting point. Start with BGP only when the routing problem is real.

When BGP starts to make sense

BGP becomes useful when you are operating a network rather than just hosting an app. You may need BGP if you have your own ASN, own an IPv4 or IPv6 prefix, lease IPv6 space and want to announce it, operate downstream customers, want IP transit over a tunnel, or need to route prefixes to dedicated servers, colocation, VDS or VPS services.

BGP also matters when you need route export options such as default route, default plus local routes or full table where available. If you are managing IRR and RPKI records, BGP is probably part of the operational picture too.

HYEHOST note: The panel is built to make these routing tasks easier without turning every small change into a manual support ticket.

Where BGP lives in the HYEHOST panel

HYEHOST has several panel areas that can involve BGP or routing. The exact controls depend on the product, but the goal is consistent: keep routing, billing, service status and support attached to the correct customer service.

  • BGP management: available for eligible VPS and VDS services.
  • IP Transit: free IPv6 transit and paid transit via tunnel where available.
  • RIPE IPv6: RIPE prefix leasing, IRR, ROA and reverse DNS controls.
  • ARIN IPv6: ARIN prefix leasing and reassignment workflows.
  • IPv4 via tunnel: routed IPv4 without requiring customer BGP.
  • Dedicated servers and colocation: physical infrastructure for customers building larger network designs.

Enabling BGP on a VPS or VDS

For supported VPS and VDS services, the BGP controls are available from the service area in the HYEHOST panel. A typical flow looks like this:

  1. Log in to the HYEHOST panel.
  2. Open your VPS or VDS service.
  3. Go to the BGP or network section.
  4. Enter your ASN.
  5. Add the prefixes you want to announce.
  6. Confirm the required route objects and authorization exist.
  7. Save or apply the BGP configuration.
  8. Use the session details shown in the panel to configure your router.

The panel stores the BGP settings against your service, so you do not need to search through old support tickets for peer details. That is especially useful when you manage multiple services or need to hand configuration to another engineer.

Ordering IP transit through the panel

HYEHOST IP transit via tunnel is ordered from the IP Transit page. The panel supports free IPv6-only transit where available and paid transit plans for users who need more features.

During ordering, you can select the location, tunnel type, ASN, routing option, address family support, commit level where applicable and endpoint details. Supported tunnel types can include WireGuard, GRE, SIT, GRETAP or VXLAN depending on location and product availability.

Routing options may include default only, default plus local, or full table where available and allowed by the plan. Free IPv6 transit is designed to help users get started with BGP without paying for a full transit service. It is still monitored for abuse and misconfiguration.

Free transit per ASN and location

HYEHOST allows free IPv6 transit on a per-ASN and per-location basis where available. That means a user can order one free transit session for a given ASN in a given location. If the same user has multiple ASNs, each ASN may be treated separately. If HYEHOST offers multiple free transit locations, availability is checked per location.

This keeps the free service useful while reducing abuse and duplicate sessions.

Tunnel details and endpoint information

After a transit session is provisioned, the HYEHOST panel shows the tunnel details needed to configure your side. Depending on the tunnel type, the panel may show the HYEHOST endpoint IP, customer endpoint IP or hostname, tunnel IPv4 or IPv6 addressing, WireGuard public key, WireGuard port, BGP neighbor details, local and remote ASN, allowed address families and example configuration guidance.

For endpoint hostnames, the panel can resolve the address family needed for the tunnel where supported. If you need IPv4 or IPv6 specifically, make sure your endpoint DNS and selected address family match the tunnel you are trying to build.

IRR and RPKI in the panel

For BGP to work reliably, route authorization matters. HYEHOST uses IRR and RPKI information to help validate announcements and reduce routing mistakes.

For RIPE IPv6 services, the panel can help manage route6 objects, ROAs, prefix metadata, sub-prefixes and reverse DNS. For ARIN IPv6 services, the workflow is different because ARIN handles registry data differently, but the panel still aims to provide a similar customer experience.

If you create a ROA with a maximum length that is too strict, a more specific announcement may become invalid. For example, a ROA for a /40 with max length /40 will not authorize a /48 announcement. The panel includes protections to help prevent this kind of conflict.

Informational IRR lists versus live BGP filters

The HYEHOST panel may show IRR information on BGP or transit pages. This list is informational. It helps customers see what the panel has collected or validated, but it does not directly change the live BGP session by itself.

HYEHOST BGP filters update regularly. Upstream networks may also need time to update their own prefix filters. In some locations, upstream filters can take up to 12 hours or more to fully accept newly added prefixes.

If your BGP session is established but traffic is not flowing immediately for a newly announced prefix, check your ROA max length, IRR route object, announced prefix, BGP export policy and whether upstream filters have had time to update.

Import limits and safety

BGP mistakes can cause real problems. That is why the HYEHOST panel uses import limits. Import limits control how many IPv4 and IPv6 routes a customer session can send to HYEHOST.

For normal sessions, default limits are kept conservative. Admins can adjust limits where needed, but the goal is to stop accidental full-table leaks or misconfigured routers from causing unnecessary routing churn. If your session needs higher limits, open a ticket and explain what you are announcing.

Hold timer monitoring

The panel also monitors repeated BGP hold timer expiry events. A hold timer expiry usually means a BGP session is repeatedly dropping and reconnecting, which can create unnecessary routing update spam.

If a free transit session repeatedly causes hold timer expiry events, HYEHOST may suspend the session and open a support ticket asking the customer to fix the configuration. If the issue is ignored, the free transit service may be removed and the user may be blocked from ordering free transit again.

This does not exist to punish normal users. It exists to protect the network from broken sessions that repeatedly flap.

Customer-side BGP example

The exact configuration depends on your router software, tunnel type, ASN and session details. A generic IPv6 BGP example may look like this:

router bgp 64512
 neighbor 2001:db8:472:72::1 remote-as 47272
 neighbor 2001:db8:472:72::1 update-source 2001:db8:472:72::2
 !
 address-family ipv6 unicast
  network 2001:db8:1000::/48
  neighbor 2001:db8:472:72::1 activate
 exit-address-family

This is only an example. Always use the real values shown in your HYEHOST panel.

Before bringing a session online

Before enabling a BGP session, check the basics: your ASN is correct, your tunnel is up, you can reach the HYEHOST tunnel endpoint, your router uses the correct source address, you are only announcing approved prefixes, your IRR route objects exist, your ROAs authorize the exact prefix length you want to announce, your import limits are suitable and you have console access if the router is a VPS.

If you are configuring BGP on a VPS, keep serial or VNC console available from the panel. If you break normal network access, console access may be the easiest way back in.

IPv4 via tunnel is different

HYEHOST also offers IPv4 via tunnel. This is not the same as IP transit. With IPv4 via tunnel, HYEHOST routes assigned IPv4 space to your tunnel. You do not need your own ASN and you do not need to run BGP.

Use IPv4 via tunnel if you need routed IPv4, do not have an ASN, do not want to manage BGP or want HYEHOST to route assigned IPv4 to your tunnel. Use IP transit if you want BGP, have your own ASN, want to announce your own prefixes or need routing policy control.

How HYEHOST helps customers grow

The HYEHOST panel is designed so customers can start simple and grow into advanced networking when they need it. A typical path might start with a Cloud VPS, add private LANs or extra storage, move to VDS or VPS pools as resource needs grow, lease RIPE or ARIN IPv6 space, add BGP to a VPS, VDS, dedicated server or colocation service, then order IP transit via tunnel.

Not every customer needs every step. The important part is that HYEHOST can support both simple hosting and advanced routing from the same panel.

Final thoughts

BGP is not something every VPS customer needs on day one. But when your project grows from a single server into a network, the HYEHOST panel gives you a practical way to manage that growth.

You can order services, configure sessions, review tunnel details, manage IRR and RPKI records, monitor traffic, handle billing and open support tickets from one place. If you only need a server, start with a HYEHOST VPS. If you need routing control, IPv6 leasing, tunnel-based transit or BGP automation, the HYEHOST panel is built to help you move from basic hosting to real network operations.