Onboarding IP space to Cloudflare previously required a request through the account team, which then involved addressing and network engineering plus whichever team owned the service the prefix would be used with — CDN, Magic Transit, Spectrum or Egress. Customers without primary ownership of a prefix also had to work with their legal teams and possibly another organization to obtain a Letter of Agency (LOA) through layers of approvals. The process was manual and could take up to 4–6 weeks.
The self-serve BYOIP API changes that: customers can now onboard and set up their BYOIP prefixes themselves. Cloudflare automates the bureaucratic side using RPKI, the Resource Public Key Infrastructure, and continues to generate LOAs on customers' behalf based on the guarantees of the new ownership validation process, so customer routes keep being accepted across the Internet.
Self-serve onboarding is initially limited to BYOIP prefixes originated from Cloudflare's ASN AS 13335, because reliance on widely available ROA objects is sufficient there. Artifacts such as the ASP Path Authorisation (ASPA) object still have limited deployment, so the narrower scope keeps the automated path safe for the Internet while covering most BYOIP customers.
The release sits alongside the earlier update enabling multiple services on a single BYOIP prefix, and Cloudflare frames both as steps toward a fuller IPAM platform.
From manual review to RPKI-backed validation
BYOIP was first launched in 2020 to let customers bring their own IP space to Cloudflare for control and configurability: traffic destined to an onboarded prefix is routed to Cloudflare's edge for processing, across Layer 7 services, Spectrum or Magic Transit.
Under the existing flow, a customer supplies an LOA and an IRR record matching the prefix and ASN, and a Cloudflare engineer reviews it manually. That approach has two weaknesses. A document-based LOA is only as secure as the reviewer's diligence — a fraudulent or inaccurate document that slips through can mean a hijacked prefix or ASN. It is also slow: leased space requires supporting documentation showing a clear chain of authorization back to the original assignment or allocation, and gathering that paperwork plus waiting for review can add weeks before a prefix is deployed.
Two checks: intent and ownership
Self-serve replaces the review with a two-step process: an RPKI ROA to confirm intent, and a modification to IRR or reverse DNS records to confirm ownership. The result is faster onboarding with no human intervention, and ownership checks more rigorous than a scanned document, though not entirely foolproof.
The ownership half draws on the registry system. RIRs distribute and manage Internet number resources, allocating space originally assigned by IANA to LIRs such as ISPs according to policies that consider legal documentation, registry records, technical contacts and BGP information; end users obtain addresses from an LIR or sometimes directly from an RIR. The IRR is separate and records routing rather than assignment; RIR-operated IRR instances can tie publication rights to the organizations holding the corresponding addresses, which makes modifying such a record a good ownership signal. A customer who prefers not to use IRR validation can instead modify reverse DNS: managing rDNS for a prefix — a PTR record or a security TXT record — requires permission from the allocating entity, demonstrated either through the IP owner's authenticated portal or by that owner delegating authority to a third-party DNS provider via an NS record for the reverse zone.
Either way, Cloudflare issues a unique, single-use validation token that must be placed in the content of the relevant record. The system looks for the token as evidence the request comes from someone authorized to make the modification. An IRR route object carrying a token, for the documentation-only address 192.0.2.0/24:
% whois -h rr.arin.net 192.0.2.0/24
route: 192.0.2.0/24
origin: AS13335
descr: Example Company, Inc.
cf-validation: 9477b6c3-4344-4ceb-85c4-6463e7d2453f
admin-c: ADMIN2521-ARIN
tech-c: ADMIN2521-ARIN
tech-c: CLOUD146-ARIN
mnt-by: MNT-CLOUD14
created: 2025-07-29T10:52:27Z
last-modified: 2025-07-29T10:52:27Z
source: ARIN
A reverse domain lookup over the same address:
% dig cf-validation.2.0.192.in-addr.arpa TXT
; <<>> DiG 9.10.6 <<>> cf-validation.2.0.192.in-addr.arpa TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16686
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;cf-validation.2.0.192.in-addr.arpa. IN TXT
;; ANSWER SECTION:
cf-validation.2.0.192.in-addr.arpa. 300 IN TXT "b2f8af96-d32d-4c46-a886-f97d925d7977"
;; Query time: 35 msec
;; SERVER: 127.0.2.2#53(127.0.2.2)
;; WHEN: Fri Oct 24 10:43:52 EDT 2025
;; MSG SIZE rcvd: 150
For the intent half, a ROA is a cryptographically signed document stating which ASN may originate a prefix — a notarized contract in digital form, which relying parties validate against RPKI. The customer creates a ROA naming Cloudflare's ASN (AS13335) as an authorized originator and has it signed, often through a hosted RPKI system in an RIR portal; Cloudflare's systems then detect the signed authorization and routing intent is confirmed.
Cloudflare contrasts this with BYOIP offerings elsewhere that require self-signed certificates and manual RDAP record changes. Its combination of IRR or reverse DNS TXT records with RPKI is intended to feel familiar and straightforward to network operators.
LOAs without the paperwork
Although the self-serve flow removes the LOA from the customer's side, many operators still rely on LOAs when accepting prefixes from other networks. To keep prefixes accepted by adjacent networks, Cloudflare generates a document on the customer's behalf describing the checks performed and confirming the valid ROAs authorizing its origination.

Preventing blackholes with a default service binding
The design had to balance flexibility against the risk of a prefix being advertised with nothing bound to serve its traffic, which would blackhole it. Self-serve therefore requires a default service binding covering the entire onboarded prefix. Customers can layer further service bindings on top — placing CDN over a default Spectrum binding, for example — via multiple service bindings, but a prefix is never advertised without at least one binding.

Documentation and roadmap
Instructions for onboarding, advertising and adding services to prefixes through the API are in the developer docs; Cloudflare notes that onboardings can be complex and points customers to its professional services team as an alternative. Self-serve BYOIP in the dashboard and self-serve offboarding are planned for the months ahead.



