Skip to main content
All virtual servers come with a 1 Gbps shared port by default. Our looking glass covers all our locations.

BGP sessions

We allow BGP sessions for free on all services in these locations:
  • Los Angeles, CA
  • Nuremberg, DE
  • Miami, FL
  • Kansas City, MO
  • Johor Bahru, MY

Requirements

Every prefix you announce must have:
  • A valid IRR record: a route object (or route6 object for IPv6) in an IRR database, with the announcing ASN as the origin.
  • A valid ROA: an RPKI ROA that authorizes the announcing ASN, so the prefix validates as RPKI valid.
We don’t accept prefixes missing either one. We may also ask for an LOA for prefixes you want to announce.

Private ASNs

You can use your own public ASN or a private ASN. With a private ASN, your prefixes are announced from our network as AS22295, so their IRR records and ROAs must name AS22295 as the origin. Setting up a session with a private ASN can take longer. Prefix list updates for a private ASN are manual, so how often we can refresh them is limited.

Prefix sizes

You can announce IPv4 prefixes as small as a /32 and IPv6 prefixes as small as a /48, for any purpose, such as high availability or failover. If you announce an IPv4 prefix smaller than a /24, every session must also announce its covering /24 alongside the more specific route. Your ROA’s maximum length must allow the more specific prefix, or it won’t validate.

Communities and routes we send

We don’t currently support BGP communities, either for actions (such as prepending or blackholing) or for information. Sessions are announce-only. We don’t send you any routes, including a default route, so your server should keep using its normal gateway for outbound traffic. If you have a use case that needs routes from us, contact us. Where the monthly spend supports it, we can look at a custom setup.

Getting started

Contact us before you buy a service to check your requirements are possible. Processing a BGP session can take 1 to 2 weeks.

Bring your own IP (BYOIP)

We can route your own IP addresses to dedicated servers. BYOIP isn’t available on virtual servers or other services. Your addresses are delivered on their own VLAN to each dedicated server’s port. You choose how the port receives that VLAN:
  • Access: the port carries only your BYOIP VLAN, untagged. Your server needs no VLAN configuration.
  • Trunk: the VLAN arrives tagged, so you configure a VLAN interface on your server. Use this if the port also needs to carry other VLANs.
Contact us before you buy a service to check your requirements are possible, and say whether you want the port set as access or trunk.

IPv6

Your server’s “Networking” page shows the on-link address, gateway and any routed subnet. Many locations give an on-link address plus a routed range, and some use an on-link subnet. Use the values shown for your server. Only the primary on-link address can be configured automatically. Addresses from a routed subnet need configuration inside the operating system. See Networking.

Additional IPv4 addresses

Buy and attach addresses through Floating IPs. The panel updates the managed network configuration and tries to apply it in the guest. Custom images or manually managed networks may need extra configuration. To replace the primary IPv4, swap in an attached floating IPv4. A normal swap needs no reinstall and no support ticket. Use the prefix, gateway and interface assigned to your server, and don’t overwrite working network files with another server’s settings. Keep VNC open while you change networking.