IPXO automates AWS BYOIP onboarding and adds Cloudflare to assign flow
IPXO launched end-to-end AWS BYOIP automation on 5 November 2026 and added Cloudflare BYOIP to its portal assign flow on 7 October without a 12-month lease requirement.
CloudFormation links and Cloudflare's Addressing API now drive IPXO's two automated cloud workflows, detailed in a 16 November product update: end-to-end AWS BYOIP onboarding (live since 5 November 2026) and direct Cloudflare BYOIP integration in the IPXO assign flow (live since 7 October 2026).
What changed
Both automated workflows apply to /24 or larger subnets registered with RIPE NCC or ARIN, and neither requires a Letter of Authorization (LOA).
- AWS BYOIP (live 5 November 2026): IPXO's earlier January 2026 integration still required support staff to link accounts manually. Since 5 November, selecting AWS BYOIP in the IPXO Portal generates a CloudFormation quick-create link for a scoped, time-limited IAM role (
AssumeRolewith External ID, 1-hour STS session), after which IPXO publishes the RDAP X.509 authorization certificate, checks ROAs forAS16509andAS14618, and provisions and advertises the prefix for EC2 (regional) or AWS Global Accelerator. IPXO reports onboarding execution takes 15 to 30 minutes once registry records are ready, with routing propagation adding one to two hours; previously authorized AWS accounts are remembered for later assignments. - Cloudflare BYOIP (live 7 October 2026): Selecting Cloudflare in the assign flow binds a leased subnet to the customer's own Cloudflare Enterprise account (with BYOIP enabled by Cloudflare) for CDN or Spectrum (
AS13335) using the customer's Account ID and a pre-scoped API token. IPXO verifies that the ROA authorizesAS13335only, adds the prefix via Cloudflare's Addressing API, publishes the registry ownership token, and triggers Cloudflare validation and service binding. The previous 12-month lease commitment requirement no longer applies.
IPXO charges no separate BYOIP provisioning fee. On the Free plan, ROAs are metered at 10,000 tokens per authorized network (20,000 tokens for AWS's two ASNs; 10,000 tokens for Cloudflare's AS13335); on the paid Starter plan, ROAs are included.
Why it matters for BYOIP teams
Manual cloud BYOIP onboarding often stalls on mismatched RPKI ROAs, registry X.509 or validation-token placement, and ticket handoffs between an address lessor and the cloud operator. Removing the manual account-linking step on AWS and dropping the 12-month minimum lease commitment on Cloudflare lowers setup friction for shorter-term or multi-region deployments using leased RIPE NCC or ARIN space.
Teams using subnets registered with APNIC, LACNIC, or AFRINIC, or targeting Google Cloud, Microsoft Azure, or IBM Cloud, still follow documented manual ticket flows.
What to check
- Confirm your target RIR (
RIPE NCCorARIN) and cloud prerequisite before leasing: AWS requires Elastic IP or Global Accelerator compatibility, while Cloudflare requires an Enterprise account with BYOIP enabled by your Cloudflare account manager. - Review our updated IPXO IP Leasing Overview, AWS BYOIP Integration Overview, and Cloudflare BYOIP Integration Overview for step-by-step details.
- Remove a prefix from your AWS or Cloudflare account before terminating a lease, as IPXO does not request account permissions to deprovision live cloud resources automatically.
Sources
- BYOIP update: AWS automation and Cloudflare integration
IPXO · published 16 Nov 2026 · checked 17 Nov 2026
- AWS BYOIP with IPXO
IPXO · checked 17 Nov 2026
- Cloudflare BYOIP with IPXO
IPXO · checked 17 Nov 2026