By Savvas Bout, Founder of Prefixx. Last updated 18 November 2026.
The choice of origin AS when acquiring IPv4 addresses (whether purchasing them or leasing them ) is one of the biggest decisions with lasting impact.
If wrong, your announced prefixes may not propagate perfectly, RPKI ROAs may not match up, and your traffic will be black-holed by reputation systems before a single packet even makes it to your destination. But getting it right the first time means that your block of addresses will be perfectly reachible, verifiable, and operating perfectly from the word go.
When deciding on announce policy, there are more variables than most engineers care to admit: do you own the ASN or are you borrowing it, how do your upstream peers validate origin, what do the IRR records say, and does your ROA actually cover the exact prefix length you intend to announce.
Each of these variables interact with each other to produce a complex system where a single mis-match can take days to diagnose and result in route leaks , RPKI invalids or silent black-holing.
We examine each of the key variables in turn, ASN ownership vs. third party origination, ROA scope and max-length, IRR hygiene, and white-glove transfer support. We start with the most fundamental question of all: whose ASN is that of the originating ASN for a given prefix? Is it yours, or that of a third party?
Frequently asked questions
What is an origin as?
An origin AS (Autonomous System) is the BGP autonomous system number announced as the source of a specific IP prefix in the global routing table. When a router receives a BGP route, the rightmost ASN in the AS_PATH attribute identifies the origin AS. It tells the internet which network is the authoritative source for that block of addresses. Choosing your origin AS means deciding which ASN will appear in that position for your prefix.
How does choosing your origin as work?
You configure your router or your upstream provider to originate your IP prefix under a specific ASN in BGP. That ASN is then propagated across the internet through BGP route announcements. If you use RPKI, a Route Origin Authorization (ROA) must be created that explicitly authorizes that ASN to announce your prefix. Any mismatch between the ROA and the announced origin ASN causes the route to be marked RPKI-invalid and dropped by validating networks.
What are the benefits of choosing your origin as carefully?
A correctly chosen and consistently used origin AS improves routing security, RPKI validity, and your prefix's reputation across the internet. It prevents route hijacks by ensuring only authorized ASNs can legitimately announce your space. It also keeps your IRR route objects and RPKI ROAs consistent, which reduces the risk of your traffic being filtered by upstream providers. For leased or purchased blocks, a clean origin AS history avoids inherited reputation problems.
What should I look for when choosing an origin as?
Look for an ASN with a clean routing history and no prior association with spam, abuse, or hijacking incidents. Confirm that the ASN is registered in the relevant IRR databases with accurate route objects, and that RPKI ROAs can be issued or updated to authorize it for your prefix.
If you are using leased space, verify that the lessor will create the ROA authorizing your ASN specifically. Prefixx prepares the LOA, RPKI ROA, and IRR route objects as part of its white-glove service, so the paperwork matches your chosen origin AS from day one.
How do I choose the right origin as provider?
Choose a provider that handles the full routing paperwork stack: LOA, RPKI ROA, and IRR route objects aligned to your specific ASN. Confirm they support BGP monitoring so you can detect unauthorized announcements after deployment.
If you plan to deploy on bare metal infrastructure , look for native BYOIP and BYOASN support with no per-IP surcharge. Prefixx manages all of this end to end, including BYOIP deployment onto Netrouting bare metal and support for cloud BYOIP programs across AWS, GCP, Azure, OCI, and Cloudflare .
The way your Internet traffic is seen depends on your chosen origin AS. Its stability, its RPKI validity, IRR consistency as well as its general reputation all depend on it. Choose your AS for origin carefully before you announce any prefixes at all. Mistakes with origin AS can be very expensive to correct later.
There are two key points to understand about AS originates. First, the AS that you originate from must match the AS number listed in your published ROA and IRR route objects. This ensures that your routes are not dropped by downstreams and route servers. Second, if you are bringing your own IP block to a hosting environment, make sure that your host natively supports BYOIP as opposed to it being a features that was afterthoughted in and not thoroughly implemented.
If you need help sourcing an ASN, preparing your LOA, ROA and IRR objects, or deploying BYOIP onto bare metal, Prefixx handles all of it. Reach out and a senior consultant will walk through your setup.
Contact us to discuss your IPv4 needs today
No hidden fees, free consult. A broker replies within one business day.