# Register a Route Object in the IRR

This chapter describes how to register a route object in the Internet Routing Registry (IRR).\
Registering a route object allows network operators and upstream providers to validate BGP announcements for your IP prefix.

## Prerequisites

Before registering a route object, ensure that:

* You have administrative control of your **IP prefix**.
* Prepare your ASN (Autonomous System Number) that will announce the IP block, and ASN of Zenlayer elastic compute service is “`62610`”.
* You have access to the corresponding **IRR maintainer (mntner) account**.
* It is recommended to [publish a **ROA in RPKI**](/welcome/elastic-compute/get-started/manage-networking/advertise-byoip/register-roa-rpki-with-rir.md) as well.

## Procedures

{% stepper %}
{% step %}

#### Identify the Correct IRR Database

<table><thead><tr><th width="300.4644775390625">Registry</th><th>IRR Database</th></tr></thead><tbody><tr><td>RIPE region</td><td>RIPE Database</td></tr><tr><td>APNIC region</td><td>APNIC IRR</td></tr><tr><td>ARIN region</td><td>ARIN IRR</td></tr><tr><td>Other operators</td><td>RADB</td></tr></tbody></table>

In general:

* European resources → RIPE IRR
* Asia-Pacific resources → APNIC IRR
* North American resources → ARIN IRR
  {% endstep %}

{% step %}

#### Create a Route Object

IRR supports two route object types:

<table><thead><tr><th width="261.771240234375">Object Type</th><th>Usage</th></tr></thead><tbody><tr><td>route</td><td>IPv4 prefixes</td></tr><tr><td>route6</td><td>IPv6 prefixes</td></tr></tbody></table>

* **Example: IPv4 Route Object**<br>

  ```
  route:      203.0.113.0/24
  origin:     AS62610
  descr:      Example Network
  mnt-by:     MAINT-EXAMPLE
  changed:    noc@example.com
  source:     APNIC
  ```
* **Example: IPv6 Route Object**<br>

  ```
  route6:     2001:db8::/32
  origin:     AS62610
  descr:      Example Network IPv6
  mnt-by:     MAINT-EXAMPLE
  changed:    noc@example.com
  source:     RIPE
  ```

Field descriptions:

<table><thead><tr><th width="254.2427978515625">Field</th><th>Description</th></tr></thead><tbody><tr><td>route/route6</td><td>The IPv4/IPv6 prefix</td></tr><tr><td>origin</td><td>The ASN originating the prefix</td></tr><tr><td>descr</td><td>Description of the network</td></tr><tr><td>mnt-by</td><td>Maintainer responsible for the object</td></tr><tr><td>changed</td><td>Contact email</td></tr><tr><td>source</td><td>IRR database</td></tr></tbody></table>
{% endstep %}

{% step %}

#### Submit the Route Object

You're recommended to submit the route object using Web Portal.

1. Log in to the web portal of your registry:
   * RIPE NCC (RIPE Database Webupdates): <https://apps.db.ripe.net/db-web-ui/>
   * APNIC (MyAPNIC): <https://my.apnic.net/>
   * ARIN IRR Portal: <https://account.arin.net/>
2. Navigate to **Create Object**.
3. Select **route** or **route6**.
4. Fill in the required fields.
5. Submit the object.
   {% endstep %}

{% step %}

#### Verify the Route Object

After submission, verify that the route object is visible in the IRR database.

Example query:

```
whois -h whois.radb.net 203.0.113.0/24
```

Expected output:

```
route:      203.0.113.0/24
origin:     AS62610
source:     APNIC
```

{% endstep %}

{% step %}

#### Ensure Consistency with RPKI

For reliable route propagation, ensure that the IRR route object matches the corresponding ROA in RPKI.

The following attributes must be consistent:

| Attribute  | IRR | RPKI |
| ---------- | --- | ---- |
| Prefix     | ✓   | ✓    |
| Origin ASN | ✓   | ✓    |

If the information is inconsistent, your route advertisement may be rejected by upstream providers.
{% endstep %}
{% endstepper %}

## What to Do Next

After registering the corresponding route object and [registering ROA/RPKI](/welcome/elastic-compute/get-started/manage-networking/advertise-byoip/register-roa-rpki-with-rir.md), you can go to zenConsole to [advertise BYOIP](/welcome/elastic-compute/get-started/manage-networking/advertise-byoip.md). We will validate the RPKI/ROA and corresponding route object before activating BYOIP.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.console.zenlayer.com/welcome/elastic-compute/get-started/manage-networking/advertise-byoip/register-a-route-object-in-the-irr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.