Add Your Own ASN (BYOASN)

Bring an existing ASN onto the platform so that Zenlayer advertises your prefixes from that AS instead of from a Zenlayer ASN. The ASN doesn't have to be registered to you — it can be one you lease or are otherwise authorized to use. What the platform checks is control over the ASN, proven by an export declaration in its aut-num object at the RIR — no ticket and no manual review.

Prerequisites

• The ASN is a public ASN and is not already in use on the platform.

• The aut-num object of the ASN can be updated at the RIR that manages it (ARIN, RIPE NCC, APNIC, and so on). Only the party the ASN is registered to, or the maintainer listed on the object, can make that update. If the ASN is registered to someone else — a leased ASN, or one held by a parent company or an upstream provider — send them the export declaration from Step 2 and ask them to add it on your behalf.

Procedures

Step 1: Get a Verification Code

1. Go to Elastic Compute > IP Pool > ASN and click + BYOASN.

2. Enter the ASN. Optionally expand More Settings to set resource group and tags.

3. Click Get verification code.

The ASN is rejected at this point if it isn't a valid public ASN, or if it is already in use on the platform. Enter a different ASN and try again.

Step 2: Add the Export Declaration to the aut-num Object

Copy the export declaration generated for you in the dialog. It looks like this:

export: to AS62610 action community .= {62610:<verification code>}; announce AS<the ASN>

AS62610 and 62610: are Zenlayer's ASN — leave them as they are. Take the verification code and the ASN from the declaration shown in the console rather than retyping the line: any difference from what the console generated makes the check fail.

The declaration is a standard RPSL export: attribute, and an aut-num object accepts more than one of them. Adding it doesn't replace or disturb the routing policies already on the object.

Then add the line at the RIR that manages the ASN. If the ASN is held by someone else, this is the point to hand the line over to them — everything below is done by whoever holds the credentials for the object.

ARIN

ARIN keeps aut-num objects in the ARIN Internet Routing Registry (IRR), managed from ARIN Online.

1. Sign in to ARIN Online with an account linked to the Org ID the ASN is registered to.

2. From the main menu, select Routing Security > Manage IRR, then choose that Org ID.

3. Select aut-num in the navigation bar.

   • If an aut-num object already exists for the ASN, select it and click Edit.

   • If not, click Create Object, set Maintained By to the Org ID, and select the ASN. An aut-num object covers one ASN only.

4. In the Export field, enter everything after export: in the declaration:

   to AS62610 action community .= {62610:<verification code>}; announce AS<the ASN>

   Leave the existing Import, Export, and other policy entries as they are.

5. Click Review, then Submit.

The same object can also be submitted through ARIN's email templates or its IRR RESTful API.

RIPE NCC

1. Sign in to RIPE Database Webupdates with a RIPE NCC Access account. Updating the object also requires the credentials of the mntner listed in its mnt-by attribute — either an SSO account associated with that maintainer, or the maintainer password.

2. Search for the ASN (for example, AS64500) with the object type set to aut-num.

3. In the query results, use the update button on the object to open it in Webupdates.

4. Add the declaration as an export: attribute:

   • In field mode, add export from the list of optional attributes — the form shows mandatory attributes only until you add one — and paste in the value.

   • Or switch to the text area and paste the whole export: … line into the object.

5. Click Submit.

APNIC

1. Sign in to MyAPNIC.

2. Go to Resources > Whois updates.

3. Open the aut-num object of the ASN for editing.

4. Add the whole export: … line to the object, leaving the existing import: and export: lines in place.

5. Submit the object.

APNIC protects some attributes of a delegated ASN (as-name, descr, country, and org) with its own maintainer, but export: isn't one of them — you can add it yourself. MyAPNIC is the recommended way to update Whois objects; updates by email to [e-mail] are being phased out.

For an ASN managed by another RIR, such as LACNIC or AFRINIC, add the same export: line to its aut-num object through that RIR's member portal.

Step 3: Confirm the Verification

Return to the console and click Verification completed, or click Verify later and close the dialog.

Either way, the platform keeps checking for the declaration for the next 3 days. Verification is not instant — RIR changes take time to publish, so a check that runs immediately after the object is saved may not see it yet.

The verification code expires after 3 days. If the ASN hasn't been verified by then, generate a new code and add the new export declaration.

Result

Once the declaration is detected, the ASN is added to your account and becomes selectable as an origin ASN.

If the dialog reports that no declaration was found, the line either hasn't published yet or doesn't match. Check the aut-num object against the declaration in the console, then click Re-verify.

What to Do Next

Use the ASN as the origin ASN when you advertise BYOIP with your own prefixes.

If the party holding the ASN can't update the aut-num object, contact us with a Letter of Authorization (LOA) for the ASN instead.