From dbfda605ae82fb7bc9dc67d67c876386c2600d6f Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 5 Nov 2025 12:34:07 +0000 Subject: [PATCH 1/3] AI-assisted-first pass --- .../concepts/irr-entries/best-practices.mdx | 70 +++++++++---------- 1 file changed, 32 insertions(+), 38 deletions(-) diff --git a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx index 0dff981184ac2d..9f775683120dc3 100644 --- a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx +++ b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx @@ -5,7 +5,7 @@ sidebar: order: 7 --- -import { GlossaryTooltip } from "~/components"; +import { Details, GlossaryTooltip } from "~/components"; You must keep your Internet Routing Registry (IRR) entries up to date so that it is public information that Cloudflare has permission to advertise your prefix or prefixes, and to ensure that your traffic can be properly routed on the internet. @@ -62,47 +62,39 @@ Add or update IRR entries when they meet any of these criteria: * The entry is incomplete or inaccurate — for example, when the route object does not show the correct origin. * The entry is complete but requires updating — for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit. -### IRR entry verification methods +### Verification methods -To verify your prefix and ASN route, use the tools and methods outlined on the table below: +## IRR Explorer - Subnet prefix verification - +Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which ASN is associated with a subnet prefix. - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Data to verifyToolMethodOutput
Subnet prefix IP
for the ASN		IRR ExplorerSearch for the subnet prefix IP, for example, 162.211.156.0/24.List of ASN numbers, source (route registry), and any associated errors.
ASN for the
subnet prefix		IRR ExplorerSearch for the ASN, for example AS13335.List of prefixes, source, and any associated errors.
Your origin ASN
and routing data		WHOIS lookup -

In a terminal, use this `whois` command, substituting your network prefix for network-prefix:

-

`whois -h rr.ntt.net network-prefix`

-

The host `rr.ntt.net` is the primary server for the Global IP network.

- 		IRR route, origin, and source information.
+**Method:** Search for the subnet prefix IP, for example, `162.211.156.0/24`. -#### WHOIS output +**Output:** List of ASN numbers, source (route registry), and any associated errors. + +## IRR Explorer - ASN verification + +Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are associated with an ASN. + +**Method:** Search for the ASN, for example `AS13335`. + +**Output:** List of prefixes, source, and any associated errors. + +## WHOIS lookup + +Use WHOIS lookup to verify your origin ASN and routing data. + +**Method:** In a terminal, use this `whois` command, substituting your network prefix for *network-prefix*: + +```sh +whois -h rr.ntt.net network-prefix +``` + +The host `rr.ntt.net` is the primary server for the Global IP network. + +**Output:** IRR route, origin, and source information. + +
The `` in the WHOIS output shows the correct IRR entry information for the specified network. In this example, the network prefix is `1.1.1.0/24`, and the output includes the route, origin ASN, and route registry, which in this example is APNIC: @@ -135,3 +127,5 @@ source: APNIC WHOIS output also shows the RPKI entry information for prefix IP addresses. When your WHOIS output only contains an RPKI entry, you must add the IRR entry. ::: + +
From 91a0540f19d5b1c694d998a0ad3dc7159bbaa2cc Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 5 Nov 2025 12:38:24 +0000 Subject: [PATCH 2/3] Remove extra h3, correct h-level, and move note outside Details --- .../byoip/concepts/irr-entries/best-practices.mdx | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx index 9f775683120dc3..d314f6f9827936 100644 --- a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx +++ b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx @@ -62,9 +62,7 @@ Add or update IRR entries when they meet any of these criteria: * The entry is incomplete or inaccurate — for example, when the route object does not show the correct origin. * The entry is complete but requires updating — for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit. -### Verification methods - -## IRR Explorer - Subnet prefix verification +### Subnet prefix verification Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which ASN is associated with a subnet prefix. @@ -72,7 +70,7 @@ Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which ASN is associa **Output:** List of ASN numbers, source (route registry), and any associated errors. -## IRR Explorer - ASN verification +### ASN verification Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are associated with an ASN. @@ -80,7 +78,7 @@ Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are a **Output:** List of prefixes, source, and any associated errors. -## WHOIS lookup +### WHOIS lookup Use WHOIS lookup to verify your origin ASN and routing data. @@ -122,10 +120,10 @@ last-modified: 2018-03-16T16:58:06Z source: APNIC ``` + + :::note WHOIS output also shows the RPKI entry information for prefix IP addresses. When your WHOIS output only contains an RPKI entry, you must add the IRR entry. -::: - - +::: \ No newline at end of file From e328b4326030aa451a42d0d24a18ad8a8a53d4a5 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 5 Nov 2025 14:07:28 +0000 Subject: [PATCH 3/3] Replace HTML table by markdown --- .../concepts/irr-entries/best-practices.mdx | 43 ++++--------------- 1 file changed, 9 insertions(+), 34 deletions(-) diff --git a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx index d314f6f9827936..7d47685984b3f1 100644 --- a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx +++ b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx @@ -15,36 +15,13 @@ You can add or update an IRR entry by following the directions of your routing r The recommended registries are AFRINIC, APNIC, ARIN, LACNIC, and RIPE. Refer to the table below for more information. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Route registryURL
AFRINIChttps://afrinic.net/internet-routing-registry#guide
APNIChttps://www.apnic.net/manage-ip/apnic-services/routing-registry/
ARINhttps://www.arin.net/resources/manage/irr/quickstart/
LACNIChttps://lacnic.zendesk.com/hc/articles/360038667154-What-are-a-route-and-a-route-6-objects
RIPEhttps://www.ripe.net/manage-ips-and-asns/db/support/managing-route-objects-in-the-irr
+| Route registry | URL | +| -------------- | --- | +| AFRINIC | [https://afrinic.net/internet-routing-registry#guide](https://afrinic.net/internet-routing-registry#guide) | +| APNIC | [https://www.apnic.net/manage-ip/apnic-services/routing-registry/](https://www.apnic.net/manage-ip/apnic-services/routing-registry/) | +| ARIN | [https://www.arin.net/resources/manage/irr/quickstart/](https://www.arin.net/resources/manage/irr/quickstart/) | +| LACNIC | [https://lacnic.zendesk.com/hc/articles/360038667154-What-are-a-route-and-a-route-6-objects](https://lacnic.zendesk.com/hc/articles/360038667154-What-are-a-route-and-a-route-6-objects) | +| RIPE | [https://www.ripe.net/manage-ips-and-asns/db/support/managing-route-objects-in-the-irr](https://www.ripe.net/manage-ips-and-asns/db/support/managing-route-objects-in-the-irr) | ## Verify an IRR entry @@ -82,14 +59,12 @@ Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are a Use WHOIS lookup to verify your origin ASN and routing data. -**Method:** In a terminal, use this `whois` command, substituting your network prefix for *network-prefix*: +**Method:** In a terminal, use the following `whois` command, replacing `` with your network prefix. The host `rr.ntt.net` is the primary server for the Global IP network. ```sh -whois -h rr.ntt.net network-prefix +whois -h rr.ntt.net ``` -The host `rr.ntt.net` is the primary server for the Global IP network. - **Output:** IRR route, origin, and source information.