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 7371a5706fd2650..3b8563b4b059fef 100644 --- a/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx +++ b/src/content/docs/byoip/concepts/irr-entries/best-practices.mdx @@ -72,7 +72,7 @@ Verify your Internet Routing Registry (IRR) entries to ensure that the IP prefix Each IRR entry record must include the following information: * **Route**: Each IP prefix Cloudflare advertises for you. -* **Origin ASN**: Your ASN, or if you do not have your own ASN, the Cloudflare ASN (`AS209242`). +* **Origin ASN**: Your ASN, or if you do not have your own ASN, the Cloudflare ASN (AS13335). * **Source**: The name of the routing registry, for example, AFRINIC, APNIC, ARIN, RADB, RIPE, or NTT. Add or update IRR entries when they meet any of these criteria: @@ -109,7 +109,7 @@ To verify your prefix and ASN route, use the tools and methods outlined on the t ASN for the
subnet prefix IRR Explorer - Search for the ASN, for example AS209242. + Search for the ASN, for example AS13335. List of prefixes, source, and any associated errors. @@ -155,6 +155,6 @@ 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. +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. ::: diff --git a/src/content/docs/byoip/concepts/loa.mdx b/src/content/docs/byoip/concepts/loa.mdx index f5be5f76cad056e..9482664c9db63fa 100644 --- a/src/content/docs/byoip/concepts/loa.mdx +++ b/src/content/docs/byoip/concepts/loa.mdx @@ -11,16 +11,16 @@ head: A Letter of Agency (LOA) - sometimes referred to as a Letter of Authorization - is a document that authorizes Cloudflare to announce a prefix(es) on behalf of another entity. The LOA is required by Cloudflare's transit providers so they can accept the routes Cloudflare advertises on behalf of another entity. -The letter must contain both the prefixes you are authorizing Cloudflare to announce and which ASN they will be announced under. Cloudflare can announce a prefix under your ASN or you can use Cloudflare's ASN, which is AS 209242. +The letter must contain both the prefixes you are authorizing Cloudflare to announce and which ASN they will be announced under. Cloudflare can announce a prefix under your ASN or you can use Cloudflare's ASN, which is AS13335. + +:::note +Current customers who are still using Cloudflare's AS209242 can continue using this same ASN. No further change is required. +::: Cloudflare accepts digital signatures on an LOA, as long as it is clear who is signing the LOA. :::note[Note] - - An LOA is a formal document which should be on company letterhead and contain a wet signature. The Letter of Agency must be a PDF. Transit providers may reject the LOA if it is in a JPG or PNG format. - - ::: You can use the below template when creating an LOA document. diff --git a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx index 40794657f3984d2..2146172f2406068 100644 --- a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx +++ b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx @@ -16,23 +16,27 @@ List all prefixes and the [autonomous systems (ASNs)](https://www.cloudflare.com - Internet Routing Registry entries and Letters of Agency (LOA) must match the prefixes and originating prefixes you submit to Cloudflare. - When using contiguous prefixes, specify aggregate prefixes where possible. - When using Route Origin Authorizations (ROAs) to sign routes for [resource public key infrastructure (RPKI)](https://tools.ietf.org/html/rfc8210), the prefix and originating ASN must match the onboarding submission. -- If you do not own an ASN, you can use the Cloudflare Customer ASN (AS209242). +- If you do not own an ASN, you can use the Cloudflare Customer ASN (AS13335). - Prefixes using BGP-controlled advertisements cannot be used in conjunction with dynamic advertisement (via dashboard/API). Please specify your preferred on-demand advertisement method during the prefix onboarding.
| Prefix | Originating AS | | ----------------- | -------------- | -| `103.21.244.0/23` | AS209242 | +| `103.21.244.0/23` | AS13335 | | `131.0.72.0/22` | AS395747 | | `103.21.245.0/24` | AS395747 |
-:::note[Note] +## Cloudflare ASN vs. your own ASN + When customers supply their own ASN, Cloudflare prepends the main Cloudflare ASN (AS13335) to the BGP `AS_PATH`. For example, if the customer ASN is AS64496, anyone directly peering with Cloudflare sees the path as `13335 64496`. -If you do not have an ASN or do not want to bring your ASN to Cloudflare, you can use the Cloudflare Customer ASN (AS209242). In this case, the path becomes `13335 209242`. +If you do not have an ASN or do not want to bring your ASN to Cloudflare, you can use the Cloudflare Customer ASN (AS13335). + +:::note +Current customers who are still using Cloudflare's AS209242 can continue using this same ASN. No further change is required. ::: ## Add an IP prefix