Use your own IP prefixes on a VPS with BGP

Most VPS customers use the IPv4 and IPv6 addresses included with the server. BGP is for teams that already operate an ASN and address space and need to announce their own prefixes from a virtual machine.

When BGP fits

Typical uses include retaining the same address space across providers, building an anycast service, testing routing software, or connecting a VPS to a wider network design. It is an advanced option and is not needed for ordinary websites, APIs, or VPN servers.

sharptech operates its own autonomous system, owns IP space, and is a RIPE member. Virtual server customers can request a BGP session for their own prefixes at no extra cost.

What must be agreed first

The request needs your ASN, exact IPv4 and IPv6 prefixes, intended origin ASN, address families, topology, and routing goal. Prefix lengths, peer addresses, maximum-prefix limits, routing policy, RPKI, communities, and optional features must be agreed with sharptech.

The session is arranged directly and is not a self-service option in the billing portal. Contact sharptech networking before ordering if BGP is required.

What you manage

You configure and monitor the routing daemon, route filters, registry objects, RPKI authorization, and recovery access. A bad route policy can disconnect the VPS or advertise an unintended prefix, so this work needs an experienced network operator.