IP address and AS number registration

CloudHosting registers PI (provider independent) address space directly to your organization through RIPE NCC, with us as the sponsoring LIR, so the addresses stay with you whichever ISP carries your traffic. PA (provider aggregatable) space belongs to the ISP: if you leave, you hand the addresses back and renumber every server, firewall rule and DNS record, a slow and error-prone project in a live network. The trade-off is that PI needs a sponsoring agreement and a yearly RIPE fee, so it is a deliberate investment in stability rather than a free alternative. If your services depend on fixed addresses, or you plan to multihome later, PI is the sensible choice, and we advise on block sizing.

CloudHosting registers an AS number for 150.00 EUR plus 150.00 EUR a year, and it gives your network its own identity in global routing. With it you run BGP and announce your PI addresses to several providers at once, a setup called multihoming: if one upstream fails, the announcements over the others keep your services reachable without manual switching. Your own AS also lets you steer how traffic enters and leaves your network. With a single uplink and no plans for a second one, you can postpone it. We run our own network under AS58269 and help bring your BGP sessions up to working announcements.

CloudHosting usually completes a PI or AS registration in 1 to 3 weeks from the moment the documents are signed. Most of that time is in RIPE NCC's hands: they verify the organization, the request and the sponsoring agreement, and sometimes come back with questions, which we answer on your behalf. You can speed things up by having your company registration details ready and signing without delay. IPv4 takes longer in practice, because before registration can start we have to find a suitable block on the transfer market and agree the terms. We keep you informed at every step, and the BGP work can be prepared in parallel.

CloudHosting charges 100.00 EUR to register an IPv6 /48 and 100.00 EUR a year in support, 150.00 EUR to register an AS number and 150.00 EUR a year, and 100.00 EUR a year to support an IPv4 block, all without VAT. The yearly amount covers the charge RIPE NCC levies on every independent resource through the sponsoring LIR, and it is what keeps the resource in the RIPE database with your organization as the holder. An IPv4 block itself is bought or leased at market price on top. RIPE can adjust its fees over time, so the final quote always reflects the current rates and your block size.

CloudHosting can still get you IPv4, just not from a free pool: RIPE's IPv4 stock ran out years ago, so blocks now change hands on the transfer market or are leased, at market prices that move with demand and block size. That is why we quote IPv4 individually instead of publishing a price. A transfer makes your organization the registered holder of the block, while a lease gives you the addresses for a recurring cost without holdership, so the choice depends on your budget and on how long you need them. Tell us the size you need and whether you prefer to buy or lease, and we check what the market offers now.

CloudHosting can become the sponsoring LIR for PI addresses and AS numbers you already hold, and the move is an administrative change in the RIPE records, not a technical one: nothing is renumbered, your BGP announcements stay up and your services keep running. We prepare the new sponsoring agreement, coordinate the transfer paperwork with RIPE NCC and confirm once the records show us as the sponsoring LIR. From then on the yearly RIPE fees for those resources run through us. To start, send us a list of the resources you hold and we will outline the steps, the timeline and the cost.

CloudHosting engineers configure BGP on your own router, and that no longer means expensive carrier equipment: MikroTik and many other widely used platforms handle it well. What matters more than the brand is whether the device suits your setup, for example how much routing information it must hold and how many upstream sessions you plan, so the right model follows from your network rather than from a price tag. We set up the sessions together with you and stay involved until the announcements are visible and traffic flows. If you are unsure whether your current router is up to the job, send us the model and we will tell you.

CloudHosting registers an IPv6 /48 for 100.00 EUR plus 100.00 EUR a year, and it is the easy part of the order, because IPv6 PI blocks are still freely available from RIPE NCC: no market to search and no scarcity pricing. Registering IPv6 together with your IPv4 request means one round of paperwork instead of two, and your network is ready to serve users over both protocols (dual stack). The honest caveat is that IPv6 does not yet replace IPv4 for most audiences, so treat it as an addition rather than a substitute. Both protocols can be announced from the same AS number.

CloudHosting acts as your sponsoring LIR, so your organization does not need its own RIPE NCC membership to hold PI addresses or an AS number. Under RIPE policy an independent resource held by an end user is sponsored by a member, and that member is us: we sign the sponsoring agreement with you, file the request and pay RIPE's yearly charge, which we invoice to you in EUR. Membership only makes sense if you want to become an LIR yourself and assign addresses to your own customers, which brings its own fees and obligations. For most companies that simply want their own addresses and AS, sponsorship is the simpler and cheaper route.

CloudHosting can announce your PI prefix from its own network AS58269, or set up a BGP session with your AS, when your servers sit in our Riga data centre; for colocation this is a standard add-on. That way you use your own addresses on our infrastructure from day one, without buying transit elsewhere. If you run your own AS with several upstreams, we can be one of them, and if one link fails your announcements through the others keep working. Name your prefixes and AS number when you ask for a quote, and before anything goes live we check the RIPE route objects and the setup together with you.