By Savvas Bout, Founder of Prefixx. Last updated 18 November 2026.
advertising IPv4 on as6206 : In the moment your address space, newly acquired by a broker or leased for a CDN edge node, brought to a bare-metal server with your own space.
To announce IPv4 smoothly more than just setting up a BGP session is required.
This guide will go through the various layers in sequence.
Prefixx create the LOA, ROA and IRR objects as part of their service, so you can read this guide to find out how to do it yourself or to hand over to them.
As6206 information and who operates it
AS6206 is a bare-metal network provider for Prefixx within the AS6206 Netrouting network. Prefixx is a brokerage that sources, reviews and transfers IP space for its customers. Netrouting is the network operator for this IP space.
What is as6206, who owns it, and how is it in use?
An ASN is a unique number assigned to an organization that allows it to announce IP address prefixes using the Border Gateway Protocol (BGP).
Why the originating ASN matters for your USA announcement
The originating ASN of a block announcement is placed in the BGP path. The reputation of an announcing ASN, its RPKI validity and IRR consistency all relate to this single number. Announcing from a clean ASN early on in the life of a block helps ensure deliverability from day one.
What is BYOIP and how do you use it vs leasing an IP address?
BYOIP allows you to bring your own IP block and announce it from your own host. Leasing is completely different: you use IP addresses of someone else and pay for them under a usage agreement, but you don’t transfer any ownership. We can assist you with bringing your BYOIP to our bare metal servers on Netrouting. Our team prepares the LOA, RPKI ROA and IRR route objects for you. There are no any additional per-IP surcharges.
Three critical documents must be in place before anything can happen.
How BGP announcements work: information on customer-owned blocks
Announcing a customer-owned IPv4 block on a hosting network requires 3 authorization documents.
What documents do I need to announce my IPv4 block on a partner network?
You need an LOA, an RPKI ROA, and an IRR route object. The LOA authorizes the hosting ASN to originate a given prefix for you. The ROA then cryptographically binds a given prefix to a given ASN. Finally, the IRR route object carries the same information as above in the typical routing registry that many ISP networks still individually query today.
| Document | What it does | What breaks without it |
|---|---|---|
| LOA | Authorizes the originating ASN in writing | Hosting network may refuse to announce |
| RPKI ROA | Cryptographic origin validation | RPKI-enforcing peers drop the route as invalid |
| IRR route object | Policy-based routing registry entry | Older filter policies reject the prefix |
Prefixx and as6206 ISP
Prefixx will prepare all 3 documents for you. BYOIP on bare metal server s under AS6206 is natively supported with no additional charge per IP. We’ll set up the LOA, ROA and IRR objects for you and your announced block will be announcing correctly from the get go. Below is more in-depth information about the 3 documents and what you need to do to prepare them correctly.
Documentation required before a block goes live in various countries

Before announcing an IPv4 block on AS6206, 3 documents must be created.
The three required documents for most countries
- LOA (Letter of Authorization), This is a document provided by the RIR-registered holder of the IP range to announce the IP range on their behalf. Upstream networks and Netrouting require this document to add a route.
- RPKI ROA, cryptographically signed object listing an IP prefix with an ASN to which the IP prefix belongs. RIR trust anchor must be used for the relevant RIR. Why is this important?
- IRR route object. A route or route6 record in the relevant IRR database that a router uses to block BGP announcements prior to RPKI validation completing.
Note: A missing or mismatched ROA causes BGP peers to mark the announcement as Invalid and drop it network-wide.
What is an RPKI ROA and why does it matter for BGP announcements?
RPKI ROA (Route Origin Authorization), signed certificate issued by appropriate trust anchor for RIR that states which ASN is allowed to announce given prefix.
Without a valid ROA, announcements from the BGP peer running origin validation will be treated as Invalid or Unknown.
How Prefixx handles location for you
Our team completes the LOA, signs the ROA under the correct RIR trust anchor, and creates the IRR route object for registration. We handle all of the RIR portal interactions required for provisioning your block of IP addresses. After your block of IP addresses has been provisioned and the block is “live”, we then address the issue of having up-to-date geolocation databases for where your traffic originates.
How to use BYOIP on as6206 through the Prefixx ecosystem
We start by establishing the required LOA, RPKI ROA and IRR route object for your IPv4 block. We provide the necessary paperwork to announce IPv4 on AS6206 on our bare-metal setup. As usual, no per-IP surcharge applies. We also offer Cloud BYOIP services for customers with IPv4 blocks who want to announce them on AWS, GCP, Azure, OCI or Cloudflare.
- Source a vetted block from our marketplace or bring your own IP space.
- We handle all routing paperwork including LOA, ROA and IRR objects created by our consultants.
- BYOIP natively included on AS6206 bare metal, no charge for IPs in addition to port cost.
- We provide white-glove service for geolocation, rDNS and reputation monitoring for your organization.
- Inter-RIR transfers between ARIN, RIPE NCC, APNIC and LACNIC are supported.
Every step is human-in-the-loop. No automated provisioning, no self-serve guesswork. If your network needs a clean, routable block announced through a reputable ASN, explore our BYOIP service or reach out to compare options.
Key points about announcing IPv4 on as6206 by location

AS6206 is a Netrouting ASN, not a Prefixx one. When announcing an IP block from within your organization using this ASN, peers and upstreams will see traffic sourced from the Netrouting network. AS number geolocation typically follows the announcing ASN until it’s overridden by a geofeed. The LOA, RPKI ROA and IRR objects required for BYOIP of your prefix are prepared by Prefixx.
When all the necessary papers are in order, announcing an IPv4 block on AS6206 is a trivial task.
Geolocation updates are not automatic and are typically updated in geofeeds published as RFC 8805 compliant files that are submitted to providers like MaxMind, IP2Location, DB-IP and ipinfo.io.
If you have a block ready to announce, or you are still sourcing one, the Prefixx team prepares every routing document and manages the full BYOIP process on your behalf. Contact Prefixx to get your block live on AS6206 without the guesswork.
Contact us to discuss your IPv4 needs today
No hidden fees, free consult. A broker replies within one business day.