1. Home
  2. Docs
  3. BGP
Guide

BGP

Your servers can announce addresses to our router with BGP. Use it to move an address between servers without waiting for us, or to bring your own IP range. It's free.

1What it's for

  • Failover: two of your servers announce the same extra IP. If one goes down, its session drops within about 90 seconds and traffic goes to the other.
  • Anycast: several servers announce one address and our router picks one. Your setup decides which.
  • Your own range: you hold an IP range and an AS number, and we announce the range to the internet from our network.

For our addresses, buy them as Extra IPs on any server first. A session can announce any of your extra IPs at the same location.

2Add a session

In the console, open BGP from the Overview and choose Add a session. Pick the server, IPv4 or IPv6, your AS number and what it announces.

  • For our addresses, use a private AS number: 64512 to 65534, or 4200000000 to 4294967294. It never leaves our network.
  • For your own range, use the AS number the range belongs to.

A password (TCP MD5) is optional. If you add one, the page shows it.

3Set up your server

Choose Server config on the session for a config to paste into BIRD 2 or FRR. It peers from your server's main address with our router (AS32819) and announces your list.

Put each announced address on the server's loopback so the server answers for it without claiming it on the network:

ip addr add 142.248.4.50/32 dev lo

Our router sends you no routes. Your server keeps its normal gateway.

The session shows Up on the BGP page once it connects, with how many routes were accepted and how many were refused.

4What our router accepts

  • Exactly the addresses and ranges on the session's list. Nothing more specific or less specific.
  • Routes that come from your AS only (prepending is fine), with your server as the next hop.
  • For your own range, only while its RPKI record (ROA) is valid.
  • A few more routes than you listed at most. Past that, the session restarts.

Anything else is refused and counted on the page. Your server may send traffic from what it announces, and nothing else.

5Your own IP range

You need:

  • An AS number, and an IPv4 range of /24 or larger or an IPv6 range of /48 or larger.
  • A ROA at your registry saying your AS may announce the range, with a max length equal to the range's length.
  • A route object (route or route6) with your AS as origin, in RADB or your registry's database.
  • A letter of authorization (PDF) signed by the range's holder, saying Entity Hosting (AS32819) may announce it.

Add the range on the BGP page with the letter. We check the ROA and the route object right away, then review it. After that we ask our upstream providers to accept it, which can take a few business days. The page shows each step.

Then add or change a session that uses your AS and announces the range. We check the ROA again every day. If it stops being valid, we stop announcing the range until it's fixed, and send you an event.

6Limits

  • One IPv4 and one IPv6 session per server, up to 20 per account.
  • Up to 32 addresses or ranges per session.
  • Up to 10 of your own ranges per account. Ask us if you need more.
  • California for now.

7API and AI assistants

Everything here is also in the API (/bgp), the eh bgp command and the AI assistant tools. Sessions going up or down and changes to your range send events (bgp.*) to your webhooks.