How to Use BYOIP

This guide explains how a Customer can use BYOIP (Bring Your Own IP) after ordering an IPv4 block on the InterLIR Marketplace (successful Order, active lease contract).

BYOIP lets you announce leased space inside a cloud or CDN instead of using only provider-assigned addresses. For terminology and provider docs, see the BYOIP (Bring Your Own IP) glossary entry.

1. Prerequisites

An active subscription / order for the IP-Block
Access to your cloud provider’s BYOIP onboarding flow (AWS, Google Cloud, Azure, OVHcloud, IBM Cloud, Vultr)
A verification token (or equivalent) issued by the provider — you will paste this into InterLIR as described below

2. Create an Assignment Request

Start from your order and create an Assignment Request (AR).

👉 Step-by-step UI and form fields: How to Send an Assignment Request.

3. Insert the BYOIP verification token

While creating the Assignment Request:

Locate the DESCR field (description / registry-facing text, depending on RIR workflow).
Paste your cloud provider’s BYOIP verification token exactly as provided — character for character, including any header/footer lines.

Example format (your provider may differ):

-----BEGIN TOKEN-----
<your-token>
-----END TOKEN-----

Important: The token must appear exactly as your provider supplied it.

If the provider still rejects the token or says it is invalid, that is resolved with their support (format, expiry, and validation rules are provider-specific).

See the FAQ: What should I do if my BYOIP verification token does not work or is not accepted?.

4. Submit and wait for approval

Submit the Assignment Request through the portal.
Wait for approval from the InterLIR team.

5. Verification and provider setup

After approval:

The token can be reflected in WHOIS / RIR records as appropriate to your workflow. RIR WHOIS is usually updated within about 24 hours; see the FAQ: How quickly is WHOIS updated at the RIR?.
The cloud provider validates control of the range.
You complete remaining BYOIP steps in the provider’s console/API (VPC attachment, BGP session, regions, etc.).

InterLIR’s role for routing/registry (route objects, RPKI / ROA, WHOIS updates, token placement where applicable) is aligned with our standard Assignment Request pipeline; you remain responsible for finishing BYOIP inside the cloud account.

Result

After successful verification at the provider:

The IP block can be used inside that cloud environment.
Traffic is routed via the provider’s network using your prefix.
You keep continuity of addressing and IP reputation where the range history matters.

Responsibilities

InterLIR (via AR workflow)	You (customer)
Registry alignment: route objects, RPKI / ROA, WHOIS updates where applicable	Completing BYOIP in the cloud provider: regions, subnets, quotas, BGP to the provider ASN, attachments
Placement of verification token as agreed in AR	Monitoring provider onboarding status and support tickets