Every few months we get the same ticket: a customer already holds their own IPv4 allocation — sometimes inherited from a legacy ASN, sometimes assigned directly by RIPE — and they're tired of renting IP space from whatever provider they're colocating with. They want to announce their own block from a network they can actually work with. This is a byoip hosting walkthrough written from the NOC side of that request: the paperwork RIPE and our routing team actually check, how the BGP session against AS60982 gets built, and which dedicated server tier makes sense to sit behind it.
What BYOIP Means on Our Network
Bring-your-own-IP is exactly what it sounds like: instead of taking IP space from our pool, you announce a prefix you already control through our autonomous system. We operate our own network under AS60982 — we are not reselling someone else's upstream allocation — which means we can accept your announcement, filter it properly, and hand it to our upstream transit carrier ourselves rather than asking a third party to originate it for you. That distinction matters more than it sounds: a reseller network often can't offer BGP sessions at all, because they don't control the AS the traffic actually rides on.
Full program details live on our BYOIP page, and BYOIP is picked as an order option when you configure a dedicated server. This post is the step-by-step version for people who want to understand what happens before they order.
Do You Qualify? Minimum Prefix and RIR Status
Before you order, check the basics:
- You must be the registered resource holder (or an authorized subdelegate) in RIPE, ARIN, or the relevant RIR — not just a downstream lessee.
- Minimum announceable block is a /24 for IPv4. Smaller fragments generally won't propagate cleanly through upstream filters regardless of whose network they're on. AS60982 announces IPv4 only, so IPv6 BYOIP is not offered.
- The prefix needs to be free of conflicting existing announcements — if another network is already originating it, that has to be withdrawn first.
If your block is smaller than a /24 and was never meant to be announced independently, BYOIP usually isn't the right fit — that's a case for standard allocated IPs instead, which is worth flagging before you start the RIR paperwork below.
The Paperwork: LOA, IRR, and RIPE Authorization
This is the part that trips people up, not the BGP config. A byoip setup guide that skips the compliance side isn't complete, so here's the sequence we actually walk customers through:
- Letter of Authorization (LOA) — a signed document confirming you authorize AS60982 to announce your prefix. It needs to be signed by whoever is listed as the resource holder in the RIR database, not just a technical contact.
- IRR route object — a route object registered in the appropriate Internet Routing Registry for your prefix, naming the origin AS: AS60982 if we announce it for you, or your own ASN if you bring one. Without this, many upstream networks will filter your announcement even after we accept it on our side.
- RIPE database updates — if your allocation is RIPE-managed, the maintainer object needs updating to reflect the new origin AS, and abuse-c/admin-c contacts should be current since RIPE and our own abuse desk will both reference them.
You create the ROA and route object in your own RIR account; we check them against the LOA before the prefix goes live. For the exact objects and a worked RIPE example, see BYOIP paperwork: LOA, ROA and route objects in the RIPE database.
Setting Up the Announcement or BGP Session on AS60982
There are two ways in, both chosen at checkout when you configure the dedicated server, and neither costs extra:
- Own /24 subnet — no ASN needed. We originate your /24 from AS60982 once the LOA and the ROA or route object check out.
- Own ASN + /24 subnet — we set up an eBGP session between your ASN and AS60982 on your dedicated server, and you originate the prefix yourself.
If you bring your own ASN, the session is a fairly standard eBGP setup:
- The session runs over your dedicated server's uplink; we exchange the session parameters — our AS60982 side and your ASN.
- You configure your router to originate the prefix and establish the session; we apply inbound and outbound filters matching the IRR object registered in the step above, so the session only accepts what's actually authorized.
- Once the session is up and the route is being accepted, check propagation from outside — a public looking glass or bgp.tools shows whether the prefix is visible beyond our network, not just locally.
Nothing is announced until the paperwork matches the prefix — that's a deliberate tradeoff between speed and not letting a misconfigured announcement leak somewhere it shouldn't. AS60982 reaches the internet through IP transit from an upstream carrier; more on how it is connected on the network page.
Which Dedicated Server to Pair It With
A BYOIP announcement needs to sit on hardware that can actually carry the route and the traffic behind it — this isn't something we offer on VPS plans. It's a dedicated server play. Sizing depends mostly on what you're running behind the prefix (a small NAT/routing box versus a full multi-service platform), but here's the range:
| Tier | Spec | Starting Price | Port Speed |
|---|---|---|---|
| Entry | Dual Xeon E5-2630 v3, 16c/32t, 128GB RAM | from €209/mo | 1–20 Gbps |
| Top-end | Dual EPYC 9754, 256c/512t, 1TB RAM | from €1,519/mo | 1–200 Gbps |
Every dedicated server ships with one usable IPv4 address (a /31) regardless of BYOIP status, and /29, /28 and /27 subnets are add-ons — that address stays yours for management access even after your own prefix is announced. Full specs and configurator are on the dedicated servers page.
RPKI, ROAs, and Keeping the Route Clean
We support RPKI and expect a valid ROA (Route Origin Authorization) for prefixes announced through AS60982. If you haven't created one yet, it's created against your resource holder account with your RIR and lists the origin AS — AS60982, or your own ASN — as valid — this is separate from the IRR route object and increasingly required by upstream networks doing RPKI validation. Getting this right before go-live avoids the awkward situation where your prefix is technically announced but gets dropped by validating peers anyway.
Common Mistakes We See
- LOA signed by the wrong contact. If the signer doesn't match the RIR-listed resource holder, the request stalls until it's re-signed.
- No IRR object, or one pointing at the old origin AS. The session comes up but the route doesn't propagate past the first hop.
- Announcing a fragment smaller than a /24. Even if we accept it locally, expect spotty visibility upstream.
- Treating BYOIP as a VPS feature. It's a dedicated server product — size hardware accordingly before you order.
How Noded Can Help
We built the BYOIP process the way we'd want to use it ourselves: no ASN required for a plain /24 announcement, no extra charge for either option, and nothing goes live until the LOA and the ROA or route object match. Once your prefix is announced it gets the same always-on Layer 3/4 DDoS protection as every other range on our network, at no extra cost. Pair your announcement with one of our dedicated servers in 11 countries, from the entry 16c/32t/128GB Xeon box up to dual EPYC 9754 configurations, all on our own AS60982. If you're ready to bring your own IP block over, read the BYOIP page and pick “Own /24 subnet” or “Own ASN + /24 subnet” when you configure a dedicated server.
FAQ
What is the minimum IP block size for BYOIP?
A /24 for IPv4. Smaller announcements are generally filtered by upstream networks regardless of which provider carries them. IPv6 BYOIP is not offered, because AS60982 announces IPv4 only.
Do I need my own ASN to bring my own IP range?
No. Without an ASN, pick “Own /24 subnet” and we announce your /24 under AS60982. If you have an ASN, pick “Own ASN + /24 subnet” and we set up a BGP session between your ASN and AS60982 on your dedicated server.
Can I run BYOIP on a VPS instead of a dedicated server?
No, BYOIP and BGP sessions are order options on dedicated servers only. A VPS gets one free IPv4, and extra IPv4 addresses can be added at checkout.
Is BGP available on every dedicated server?
Yes, as an order option. Pick “Own ASN + /24 subnet” when you configure the server; the session is turned up once your LOA and ROA or route object match the prefix.
Does RPKI affect whether my announced prefix is accepted?
We expect a valid ROA listing the origin AS — AS60982, or your own ASN — as authorized. Without one, some validating upstream peers may drop the route even though our own network accepts it.