Frequently Asked Questions
Everything you need to know about Shikanoko Networks (SKNK) — ASN sponsorship, BGP, IPv6, and more.
Commercial and resource-lifecycle content reviewed 27 July 2026.
What is Shikanoko Networks?
Shikanoko Networks is a service that allows you to obtain your own Autonomous System Number (ASN) and a /48 IPv6 prefix without needing to be a direct RIPE NCC member. We act as your Local Internet Registry (LIR) sponsor and handle the application process on your behalf.
Who needs an ASN?
An organization may need an ASN when it operates a distinct external routing policy, connects to multiple upstream networks, or participates in BGP peering. Having an ASN does not by itself make an accompanying PA prefix provider-independent.
Do I need to be a RIPE NCC member?
No. SKNK is the RIPE NCC member and acts as your sponsoring LIR; you remain a sponsored End User. RIPE NCC therefore does not bill you a direct LIR membership fee. Your ASN and the SKNK PA /48 have different ownership and portability rules, explained on our Resource Lifecycle page.
What documents do I need to provide?
We require verifiable organization or registered sole-trader documents appropriate to the applicant, plus the agreements and authorization needed for submission. We confirm the exact document list after reviewing the case.
How long does the process take?
Once we receive a complete order and all required documents, we aim to review and submit it to RIPE NCC within 5 business days. RIPE NCC then performs its own review, and timing varies by case and follow-up questions. We keep you updated via your personalized tracking link; no delivery date or approval is guaranteed.
What happens after RIPE NCC approves my application?
You will receive the ASN and SKNK IPv6 PA /48 details. You can then configure them with an upstream that agrees to accept the ASN and /48. We provide the resource details, but BGP configuration and network operation remain your responsibility.
Is there any ongoing fee?
The current sponsorship fee is EUR 89/year and renews automatically through Stripe unless you cancel before renewal. You remain a sponsored End User, not a RIPE NCC member, so RIPE NCC does not bill you the EUR 1,800 LIR membership fee. RIPE NCC's current annual EUR 50 sponsored-ASN charge is billed to SKNK and included in the EUR 89 price. We will give active customers at least 30 days' email notice of a material price or terms change.
What if my application is rejected?
If RIPE NCC rejects your application, you receive a full refund of €89. No fees are charged by RIPE NCC for rejected applications.
Can I transfer my ASN to another LIR later?
The ASN is an independent resource assigned to the End User. You can generally keep it when changing to another sponsoring LIR, subject to completing RIPE NCC's contractual relationship change process. That is different from transferring the ASN to another organization. The SKNK IPv6 PA /48 is not an independent resource and does not move with the ASN; changing sponsor or ending service normally requires a new prefix and renumbering.
Is the IPv6 prefix PA or PI?
The /48 is Provider Aggregatable (PA) space assigned from SKNK's LIR allocation. It can be used for BGP when your chosen upstream accepts the prefix, but RIPE NCC does not guarantee global routability. Unlike PI space, the PA /48 is not independent of SKNK, customers cannot manage its RIPE resource certificate or ROA, and ending the service normally requires withdrawal and renumbering. IPv6 PI is a separate resource request and is not an automatic upgrade of the same addresses.
What is included in the /48 IPv6 prefix?
A /48 contains 65,536 possible /64 subnets. How many you should use, and whether the assignment fits your network, depends on your address plan, end sites, upstream policy, and the applicable RIPE requirements.
Can I apply for an ASN as an individual or sole trader?
SKNK currently accepts legally registered organizations and registered sole traders that can provide verifiable registration documents. RIPE NCC policy may allow natural persons in some resource processes, but that does not mean every applicant or every SKNK service is eligible. Contact us before ordering if you do not have a registered business.
Is this service legitimate and RIPE NCC compliant?
Absolutely. Shikanoko Networks is a registered RIPE NCC LIR (SHIKANOKO NETWORKS LTD, Company Number 17131877, ORG-SNL106-RIPE). All ASN and IPv6 allocations are made in full compliance with RIPE NCC policies and procedures. You can verify our LIR status directly on the RIPE NCC website. We do not use gray-market or unauthorized methods — this is a legitimate, compliant LIR sponsorship service.
How does the self-service application process work?
Our self-service ASN application process is straightforward: (1) Fill in the online order form with your company and network details, (2) Upload your company registration documents, (3) Sign the Sponsoring LIR Agreement electronically, (4) Complete payment via Stripe (EUR 89/year), (5) We aim to review complete documents and submit the application to RIPE NCC within 5 business days. Track progress through your personal status link; SKNK or RIPE NCC may request clarification, and neither approval nor a delivery date is guaranteed.
Can I use my ASN for BGP on a VPS or dedicated server?
Yes, if the specific provider and plan support customer BGP and accept your ASN and IPv6 /48 announcement. Confirm its prefix-length, RPKI, IRR, and peering requirements before ordering. You arrange the BGP relationship and operate the routing; SKNK provides the ASN and IPv6 PA resource.
Can I apply if my company is outside Europe?
Yes, a company outside Europe can apply, but RIPE NCC reviews the actual network on a case-by-case basis. When the applicant is outside the RIPE NCC service region, the ASN must be used on active network infrastructure (an active network element) within the RIPE NCC service region. Explain what network will use the ASN, where it is deployed, and how it connects to external networks, and prepare IP Transit, BGP connectivity, or colocation documentation. Organizations operating only outside the RIPE NCC service region should normally contact the RIR responsible for their country. Ask us to review your case before ordering.
Do I need to configure RPKI?
RPKI (Resource Public Key Infrastructure) uses Route Origin Authorizations (ROAs) to cryptographically verify that an ASN is authorized to originate an IP prefix. Because an IPv6 PA /48 comes from Provider Aggregatable address space held by SKNK's LIR, SKNK controls RPKI authority for that resource and creates, maintains, and withdraws its ROA. Customers have a right to use the prefix, but do not directly hold the RIPE NCC resource certificate and cannot independently manage its ROA in the RIPE NCC Portal. You remain responsible for configuring your own BGP announcements to match the authorized origin ASN.
How does Shikanoko Networks compare to other LIR sponsors?
We take a compliance-first, transparent approach. Shikanoko Networks is a directly registered RIPE NCC LIR (ORG-SNL106-RIPE), and applications remain subject to RIPE NCC policy and approval. Our self-service platform gives you a private tracking link with status updates. The EUR 89 annual price includes the listed ASN sponsorship, IPv6 PA /48, submission handling, and current RIPE NCC sponsored-ASN charge; BGP and network operations are not included. Read our detailed comparison: Sponsorship vs Direct LIR vs Resellers →
Does SKNK configure BGP or operate my network?
No. SKNK provides LIR sponsorship, ASN assignment, an IPv6 PA /48 assignment, and the related RIPE NCC application process. You are responsible for your own BGP configuration, upstream relationships, routing policy, and network operation.
Who manages RPKI for the IPv6 PA /48 prefix?
Because an IPv6 PA /48 comes from Provider Aggregatable address space held by SKNK's LIR, SKNK controls RPKI authority for that resource. SKNK creates, maintains, and withdraws the associated ROA. Customers have a right to use the prefix, but do not directly hold the RIPE NCC resource certificate and therefore cannot independently manage its ROA in the RIPE NCC Portal.