Leaseweb BYOIP: your own IP addresses through IP Announcement

You create a ROA and a route object for the Leaseweb ASN of your data center, and send the request with a signed letter of authorization. Leaseweb's short name for the service is IPAN.

What Leaseweb accepts

From Leaseweb's documentation, on the day we checked:

• Size. A /24 or larger for IPv4, a /48 or larger for IPv6. In racks, Leaseweb can split the space across racks in one data center "to as small as /26 IPv4 per rack".
• Registries. Its letter of authorization terms name every regional registry; its ROA instructions cover the RIPE NCC, ARIN and APNIC, with RADB for route objects.
• PA, PI or legacy. Not mentioned. You prove that you own the block or may route it.
• Who originates. Only Leaseweb: "IP announcement is only available out of the Leaseweb ASNs, advertising the prefixes under your own ASN is not available."
• Where. NL, DE, US, UK or APAC, chosen in the request.
• Products. Dedicated servers, dedicated racks, colocation racks, Elastic Compute, VMware Single Tenant vSphere, VMware HCI and VMware vCloud. Public Cloud, VPS and shared colocation units "do not (yet)" support it.
• Price. None in the knowledge base. Leaseweb's service terms (we read the version for Leaseweb Singapore, dated September 2026) list a one-off setup fee and a fixed monthly fee. The first delivery covers up to 20 prefixes; later changes are charged as Advanced Support.
• Timing. Not published.
• Compliance. "Per September 2026, Leaseweb will only accept prefixes that are compliant": a valid route object and ROA.

Before you start

A ROA for the right Leaseweb ASN. Each data center has its own:

Set the maximum length to the most specific prefix Leaseweb will announce: equal to the prefix if it is announced whole, /24 if Leaseweb announces /24s out of a /22 (RPKI and ROAs).

A route object with Leaseweb's maintainer, and that ASN as origin. There is no token: Leaseweb asks for "mnt-routes delegated to Leaseweb", and names its maintainers, LEASEWEB-NL-MNT, LEASEWEB-DE-MNT and LEASEWEB-UK-MNT, for the RIPE Database and RADB alike.

A signed letter of authorization that proves you own the block or may route it. If you are not the holder, the holder signs it, authorizing you or Leaseweb to announce the block.

The details Leaseweb asks for: the prefixes, the original registry, the location, and whether Leaseweb should handle reverse DNS. For racks, also a network description, the router and gateway addresses (it suggests .252, .253 and .254), and, for a /23 or larger, one subnet or several /24s.

Step by step

01Pick the data center and find its ASN in the table above.

02Create the ROA in your registry's portal. At the RIPE NCC: my.ripe.net, the RPKI dashboard, New ROA, with the prefix, the Leaseweb ASN and the maximum length.

03Create the route object. In the RIPE Database, with your maintainer and Leaseweb's:

route:   203.0.113.0/24
origin:  AS60781
mnt-by:  YOUR-MNT
mnt-by:  LEASEWEB-NL-MNT
source:  RIPE

04Check both from outside. Leaseweb points to NLNOG's IRR Explorer (irrexplorer.nlnog.net) and Arelion's looking glass (lg.twelve99.net): the route object must show as active, and the RPKI status as Valid. RIPEstat gives the same answer:

curl "https://stat.ripe.net/data/rpki-validation/data.json?resource=60781&prefix=203.0.113.0/24"

05Send the request with the details and the letter of authorization. Leaseweb's pages do not name a channel for the first request; its service terms route later changes through a ticket in the Customer Portal.

06Use the addresses. In racks, the block is listed under the rack service in the Customer Portal. In shared racks, it appears as Floating IPs, and Floating IP definitions, which are static routes, send a single /32 or a subnet to one of your servers.

Mistakes that cost a day

• Your own ASN in the ROA. Leaseweb originates the route, so a ROA naming only your ASN makes its announcement invalid. Leaseweb stops announcing a prefix if "the missing or invalid records are not corrected within 24 hours of notice".
• The ASN of another site. A ROA for AS60781 does not cover a block announced from Frankfurt. A block moved between data centers needs a ROA and a route object for the new site's ASN.
• Planning a split. For a /23 or larger, Leaseweb aggregates the announcement and does "not permit de-aggregation".
• Asking piecemeal. After the first delivery, each announcement or withdrawal is a paid Advanced Support request, so put every prefix in the first one.
• Two pages, two answers. Leaseweb's older IPv4 guidelines still call IP Announcement "only available for complete racks"; the IP Announcement page, updated in August 2026, lists more. Canada is in the ASN table but not among the announcement locations, so ask before you plan on Montreal.

If you lease the block

Leaseweb takes space you do not own, with a letter of authorization from the actual owner that "authorizes you or Leaseweb to announce the IP blocks". It does not ask for the block to be registered in your name, or for you to be an LIR, and announcing the block "does not transfer title or IP ownership". The holder does the registry side: the ROA for the Leaseweb ASN, and the route object with Leaseweb's maintainer.

Where RTM Networks fits

We lease /24s and larger from our own RIPE NCC address space, and sell blocks in the RIPE NCC, ARIN and APNIC regions. For space leased from us, we create the ROA for the Leaseweb ASN of your data center and the route object with Leaseweb's maintainer, and sign the letter of authorization (lease IPv4). Leaseweb's Public Cloud and VPS take no announced space, and IP Announcement starts at a /24. For either case, we announce the block ourselves and deliver it to your server over GRE or WireGuard, in any size down to a single address (GRE and WireGuard tunnels). More providers are in our BYOIP guides.