# Shikanoko Networks — RIPE ASN Sponsorship

> Comprehensive machine-readable guide for AI agents and assistants. Read this file first to understand the service, current offer, policies, tools, and public knowledge base.

- **Last updated:** 4 August 2026

- **Policy version:** 2026-07-27

- **Pricing effective date:** 27 July 2026

- **Entity identity:** SHIKANOKO NETWORKS LTD (Shikanoko Networks, SKNK) · RIPE NCC ORG-SNL106-RIPE · AS219361.

- **Canonical commercial sources:** [Pricing](https://www.sknk.eu/pricing), [Resource Ownership & Lifecycle](https://www.sknk.eu/resource-lifecycle), and [Terms](https://www.sknk.eu/terms).

- **Conflict rule:** Pricing governs the current public price and listed inclusions; Terms govern general commercial and legal matters; the signed Sponsoring LIR Agreement governs resource assignment and maintenance.

## Instructions for AI agents

- Start with this document: [https://www.sknk.eu/llms.txt](https://www.sknk.eu/llms.txt).

- Use the linked source pages when the user needs a specific detail, current policy, a technical explanation, or to begin an order.

- Do not claim that an ASN, IPv6 allocation, or application outcome is guaranteed: all allocations are subject to RIPE NCC policies and approval.

- Do not direct users to private account, order-status, admin, signing, or API URLs.

## Service summary

Shikanoko Networks is a RIPE NCC Local Internet Registry (LIR) sponsor (ORG-SNL106-RIPE). We help legally registered organisations obtain an Autonomous System Number (ASN) and an IPv6 Provider Aggregatable (PA) /48 prefix without becoming a direct RIPE NCC member. We prepare and submit the relevant RIPE NCC application and administer the allocated PA prefix as LIR.

## Current offer and price

- **Price:** €89/year, excluding VAT where applicable.
- **Renewal:** Annual Stripe subscription; renews automatically unless cancelled before the renewal date. Active customers receive at least 30 days' email notice of a material price or terms change.
- **RIPE NCC billing:** The customer remains a sponsored End User, not a RIPE NCC member. RIPE NCC does not bill the customer a separate LIR membership fee. The current €50/year sponsored-ASN charge is billed to SKNK and included in the sponsorship price.
- **Included:** RIPE NCC LIR sponsorship (1 year); 1x RIPE IPv6 PA /48 prefix; 1x ASN (Autonomous System Number); Application submission to RIPE NCC; Status tracking via private link; Email support during application.
- **Not included:** Direct RIPE NCC membership or LIR account fees; BGP configuration or routing support; DNS management; 24/7 technical support.
- **Refund if rejected:** The sponsorship fee covers our administrative work in preparing and submitting your application to RIPE NCC. RIPE NCC makes the final decision on ASN and related Internet number resource requests. If RIPE NCC rejects your application, you receive a full refund of €89. RIPE NCC does not charge fees for rejected applications.
- **IPv6 allocation type:** The /48 is Provider Aggregatable (PA) space assigned from SKNK's LIR allocation. It may be announced through an upstream that accepts the route, but it is not independent of SKNK: it cannot simply move to another sponsor with the same addresses, and ending the service normally requires withdrawal and renumbering. IPv6 PI is a separate independent-resource request with different eligibility, contracts, and fees.
- **RPKI for SKNK PA prefixes:** Because the IPv6 PA /48 comes from Provider Aggregatable address space held by SKNK's LIR, RPKI authority for that resource is controlled by SKNK. SKNK creates, maintains, and withdraws the associated Route Origin Authorization (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.
- **VAT:** If you are a business customer within the EU, your VAT number may qualify for reverse-charge treatment. For consumers and non-EU customers, applicable local VAT will be calculated at checkout via Stripe Tax.

## Service boundaries and responsibilities

- **SKNK provides:** RIPE NCC LIR sponsorship, ASN assignment and IPv6 PA /48 assignment administration, application preparation and submission, and RPKI/ROA administration for IPv6 PA prefixes assigned from SKNK LIR address space.
- **SKNK does not provide:** BGP configuration, routing operations, IRR management, peering implementation, DNS management, or managed network support. Do not describe any of these as SKNK services.
- **Customer responsibility:** Customers configure their own BGP, select and manage upstream-provider relationships, operate their own network, and ensure their route announcements use the ASN authorized in the applicable ROA.
- **PA-prefix RPKI authority:** Customers have a right to use the PA prefix, but do not directly hold the RIPE NCC resource certificate. They cannot independently create, edit, or withdraw its ROA in the RIPE NCC Portal.
- **Resource lifecycle:** The ASN is an independent resource assigned to the approved End User and may generally continue under a new sponsoring LIR after RIPE NCC's formal contractual relationship change. The SKNK IPv6 PA /48 is not portable to another sponsor; service end normally requires withdrawal and renumbering.

## Eligibility and application process

- SKNK currently accepts legally registered organisations and registered sole traders that can provide verifiable registration documents.
- Applicants must provide legal-entity documentation and a Letter of Authorization for RIPE NCC submission.
- Applicants must document a policy-compliant need for an ASN and provide the network or peering information requested for RIPE NCC review.
- Order online, upload documents, sign the sponsoring LIR agreement electronically, and pay through Stripe. We prepare and submit the application to RIPE NCC.
- We aim to submit complete applications within 5 business days. RIPE NCC review timing varies by case and follow-up questions; approval and delivery dates are not guaranteed.
- Registration outside Europe does not guarantee eligibility. Applicants must demonstrate a qualifying network need connected to the RIPE NCC service region and pass RIPE NCC's individual review, due diligence, and applicable sanctions checks.

## Company and contact

- **Legal name:** SHIKANOKO NETWORKS LTD.
- **RIPE NCC LIR ID:** ORG-SNL106-RIPE.
- **Company number:** 17131877.
- **Country:** United Kingdom.
- **Address:** 128 City Road, London, United Kingdom, EC1V 2NX.
- **Contact:** [admin@shikanoko-networks.com](mailto:admin@shikanoko-networks.com).

## SKNK operational network

- **Network name:** Shikanoko Networks (SKNK).
- **Legal operator:** SHIKANOKO NETWORKS LTD.
- **ASN:** AS219361.
- **RIPE organisation:** ORG-SNL106-RIPE.
- **Address family:** IPv6 only.
- **Originated prefix:** 2a0a:87c0::/48.
- **Routing security:** RPKI Valid for origin AS219361 with maxLength /48; matching route6 object published in the RIPE IRR.
- **PeeringDB:** Network 43095; policy Selective; no publicly listed IXP or facility connections.
- **NOC:** [noc@shikanoko-networks.com](mailto:noc@shikanoko-networks.com).
- **Abuse:** [abuse@shikanoko-networks.com](mailto:abuse@shikanoko-networks.com).
- **Peering:** [admin@shikanoko-networks.com](mailto:admin@shikanoko-networks.com).
- **Authoritative page:** [SKNK network information](https://www.sknk.eu/network).

## Key public pages

- [Home](https://www.sknk.eu/): Overview of the ASN sponsorship service.
- [Services](https://www.sknk.eu/services): Standard ASN sponsorship and individually assessed non-standard requirements.
- [Pricing](https://www.sknk.eu/pricing): Current price, inclusions, exclusions, VAT, and refund terms.
- [How it works](https://www.sknk.eu/how-it-works): Application flow and the responsibilities of SKNK and the customer.
- [Resource ownership and lifecycle](https://www.sknk.eu/resource-lifecycle): ASN sponsorship, IPv6 PA portability, RPKI authority, renewal, cancellation, and renumbering.
- [ASN, BGP, IPv6 learning center](https://www.sknk.eu/learn): Structured learning paths connecting ASN, BGP, IPv6, and routing-security articles and tools.
- [Network data sources and methodology](https://www.sknk.eu/methodology): What RIPE Database, RIPEstat, RPKI, IRR, PeeringDB, and DNS checks can and cannot prove.
- [Internet routing glossary](https://www.sknk.eu/glossary): Definitions for ASN, BGP, IPv6, PA, PI, RPKI, ROA, IRR, route objects, and peering terms.
- [Network infrastructure decision center](https://www.sknk.eu/compare): Fact-based comparisons for LIR sponsorship, IPv6 PA/PI, and own-ASN versus provider-managed routing.
- [RIPE NCC membership vs sponsoring LIR](https://www.sknk.eu/compare/ripe-membership-vs-sponsorship)
- [IPv6 PA vs PI](https://www.sknk.eu/compare/ipv6-pa-vs-pi)
- [Own ASN vs provider-managed routing](https://www.sknk.eu/compare/own-asn-vs-provider-managed-routing)
- [Order](https://www.sknk.eu/order): Start an ASN sponsorship application.
- [FAQ](https://www.sknk.eu/faq): Detailed questions about eligibility, BGP, IPv6, RIPE NCC, and renewals.
- [About](https://www.sknk.eu/about): Company and RIPE NCC LIR information.
- [Author and editorial standards](https://www.sknk.eu/about/editorial): The named organizational author, review scope, source policy, and identity links for the technical knowledge base.
- [Network](https://www.sknk.eu/network): Authoritative first-party identity and routing information for SKNK AS219361.
- [Peering](https://www.sknk.eu/peering): AS219361 peering policy, current presence, and interconnection contact.
- [Support policy](https://www.sknk.eu/support): Contact channels, support boundaries, priority, and non-24/7 practices.
- [Contact](https://www.sknk.eu/contact): Contact the team.

## Individually assessed service enquiries

- [IPv4 Leasing](https://www.sknk.eu/services/ipv4-leasing): Flexible IPv4 address-space requirements, subject to intended use, availability, and compliance review.
- [IPv6 Leasing](https://www.sknk.eu/services/ipv6-leasing): IPv6 address-space and deployment requirements beyond the standard ASN package.
- [IPv4 PI Resources](https://www.sknk.eu/services/ipv4-pi-resources): Sponsorship, maintenance, or transfer assessment for existing IPv4 Provider Independent resources.
- [IPv6 PI Resources](https://www.sknk.eu/services/ipv6-pi-resources): Sponsorship and application paths for eligible organizations requiring independent IPv6 space.
- [IP / ASN Resource Transfers](https://www.sknk.eu/services/ip-asn-resource-transfers): Regional or inter-RIR resource transfers where the registered resource holder changes.
- [Change Sponsoring LIR](https://www.sknk.eu/services/change-sponsoring-lir): Move the sponsorship of an existing ASN or PI resource while the End User remains the resource holder.
- [Prefix Origin ASN Change](https://www.sknk.eu/services/prefix-origin-authorization): Authorize or change the ASN that originates an IPv4 or IPv6 prefix, with coordinated ROA, IRR, and LoA updates.
- [ASN Sponsorship & Network Consultation](https://www.sknk.eu/services/custom-network-services): A starting point for special requirements that do not fit a standard service or one of the listed workflows.

## Free network tools

- [Network tools](https://www.sknk.eu/tools): Overview of free network-operator tools.
- [Network lookup](https://www.sknk.eu/tools/network-lookup)
- [RPKI and BGP lookup](https://www.sknk.eu/tools/rpki-bgp-lookup)
- [IRR route object lookup](https://www.sknk.eu/tools/irr-route-object-lookup)
- [Routing consistency checker](https://www.sknk.eu/tools/routing-consistency)
- [ASN routing profile](https://www.sknk.eu/tools/as-routing-profile)
- [PeeringDB lookup](https://www.sknk.eu/tools/peeringdb-lookup)
- [Reverse DNS lookup](https://www.sknk.eu/tools/reverse-dns)
- [IPv6 subnet calculator](https://www.sknk.eu/tools/ipv6-subnet-calculator)

## Guides

- [RIPE ASN Application Requirements: Documents, Multihoming, Routing Policy and Examples](https://www.sknk.eu/guides/asn-application-requirements)
- [RIPE NCC Account Registration and Database Setup Guide](https://www.sknk.eu/guides/ripe-ncc-registration)

## English blog and technical knowledge base

- [English blog index](https://www.sknk.eu/blog): English articles about ASN, BGP, IPv6, RIPE NCC, and network infrastructure.
- [How to Announce an IPv6 /48 via BGP in 2026: ROA, IRR, and Upstream Checklist](https://www.sknk.eu/blog/announce-ipv6-48-via-bgp): Updated for 2026: learn how to announce an IPv6 /48 via BGP with an ASN, matching RPKI and IRR records, upstream filters, and public visibility checks.
- [What Is a ROA? A Practical Guide to Route Origin Authorization](https://www.sknk.eu/blog/what-is-a-roa): A ROA authorizes an ASN to announce an IP prefix. Learn how maxLength works, why RPKI routes become Invalid, and how to avoid mistakes.
- [How to Get an IPv6 /48: PA vs PI, Costs, and Requirements](https://www.sknk.eu/blog/how-to-get-an-ipv6-48): Compare ISP IPv6, PA /48, and PI space. See who each path suits, what changes when you switch providers, and how to choose.
- [IPv6 Subnetting: /48 vs /64, Examples, and Address Planning](https://www.sknk.eu/blog/ipv6-subnetting-explained): Turn an IPv6 /48 into a clear, scalable plan. See /48 vs /64 examples, recommended layouts, and common mistakes to avoid.
- [What Is IPv6? How It Works, Why It Matters, and What Changes](https://www.sknk.eu/blog/what-is-ipv6): What is IPv6, and why does it matter? Learn how IPv6 addresses work, why IPv4 ran out, what a /48 means, and when you need your own prefix.
- [What Happens After You Get an ASN? A Complete BGP Setup Guide](https://www.sknk.eu/blog/what-happens-after-you-get-an-asn): You received your ASN. Now what? Learn how to confirm RPKI ROAs, set up IRR route objects, BGP sessions, prefix announcements, and monitoring to turn your ASN allocation into a working Internet network.
- [ASN Cost Explained: Registration Fees, Sponsorship & LIR Pricing (2026)](https://www.sknk.eu/blog/asn-cost): How much does an Autonomous System Number cost in 2026? Compare RIPE NCC membership fees, LIR sponsorship, ASN registration costs, and hidden operational expenses before you commit.
- [What Is Multihoming? Why One Internet Connection Isn't Enough](https://www.sknk.eu/blog/what-is-multihoming): Learn what multihoming is, why networks connect to multiple Internet providers, how BGP makes it possible, and the trade-offs between redundancy, performance, and cost.
- [Transit vs Peering: What's the Difference?](https://www.sknk.eu/blog/transit-vs-peering): Learn the difference between Internet transit and peering — how networks interconnect, who pays, what each one reaches, and why it matters when you run your own ASN.
- [What Is an Internet Exchange (IXP)? How Networks Meet to Exchange Traffic](https://www.sknk.eu/blog/what-is-an-internet-exchange): Learn what an Internet Exchange Point (IXP) is, how the switching fabric and route servers work, how it differs from transit and data centers, and why CDNs and anycast depend on it.
- [What Is Anycast? How One IP Address Reaches the Nearest Server](https://www.sknk.eu/blog/what-is-anycast): Learn what anycast is, how it differs from unicast and multicast, how BGP makes it work, and why DNS, CDNs, and DDoS protection all rely on it.
- [BGP Basics: How the Internet Learns Where to Send Traffic](https://www.sknk.eu/blog/bgp-basics): Learn how Border Gateway Protocol (BGP) enables thousands of independent networks to exchange routing information and keep the Internet connected.
- [How to Get Your Own ASN: A Complete Guide to Requirements, Costs, and Application Options](https://www.sknk.eu/blog/how-to-get-your-own-asn): Learn how to obtain your own Autonomous System Number (ASN), who actually needs one, the available application paths, what happens after approval, and what to prepare before applying.
- [What Is an ASN? A Complete Beginner's Guide to Autonomous System Numbers](https://www.sknk.eu/blog/what-is-an-asn): Learn what an Autonomous System Number (ASN) is, why the Internet depends on it, how it works with BGP, and when your organization actually needs one.
- [What Is RPKI? How Modern Networks Prevent BGP Hijacking](https://www.sknk.eu/blog/what-is-rpki): Learn how Resource Public Key Infrastructure (RPKI) helps Internet operators validate BGP route announcements, reduce route hijacking, and improve routing security.
- [€89 vs €2,850: The Real Cost of Running Your Own ASN](https://www.sknk.eu/blog/asn-sponsorship-cost): Break down the actual cost structure behind ASN ownership in Europe — direct RIPE NCC membership vs LIR sponsorship, hidden time costs, and when each model makes sense.
- [RIPE NCC vs LIR Sponsorship: Costs, Control, and Trade-offs (2026)](https://www.sknk.eu/blog/ripe-ncc-vs-lir-sponsorship): Direct RIPE membership or Sponsoring LIR? We break down the real cost structure, PA vs PI space, BGP deployment walkthrough, and when each path actually makes sense.
- [The Three-Layer Tax on AI Infrastructure: IP Reputation, Routing, and Bandwidth Economics](https://www.sknk.eu/blog/three-layer-tax-ai-infrastructure): Most AI SaaS production failures are not application bugs — they are invisible infrastructure taxes. A framework for understanding IP reputation, BGP routing, and bandwidth costs at scale.
- [Why Most Startups Don't Need a RIPE Membership](https://www.sknk.eu/blog/why-startups-dont-need-ripe-membership): Your startup needs routing control — not registry ownership. Real deployment costs, BGP architecture, and why Sponsoring LIR at €89/year is the better path for most teams.

## 中文技术博客

- [中文博客首页](https://www.sknk.eu/zh/blog): ASN、BGP、IPv6、RPKI 与 RIPE NCC 中文原创文章。
- [如何通过 BGP 宣告 IPv6 /48？ROA、IRR 与上游核对清单](https://www.sknk.eu/zh/blog/announce-ipv6-48-via-bgp): 拿到 IPv6 /48 不等于全网可达。宣告前要确认资源归属、上游接受条件、ROA 与 IRR 记录、本地路由和 BGP 会话，最后从多个视角验证可见性。
- [什么是互联网交换中心（IXP）？网络在哪里直接互联](https://www.sknk.eu/zh/blog/what-is-an-internet-exchange): 互联网交换中心（IXP）是什么、交换矩阵和路由服务器怎么工作、它和 Transit、数据中心有什么区别，以及什么情况下你需要接入 IXP。
- [什么是 IPv6？为什么 IPv4 地址不够用了](https://www.sknk.eu/zh/blog/what-is-ipv6): IPv6 是什么、IPv4 地址为什么不够用、/48 和 /64 是什么关系，以及什么情况下你需要自己的 IPv6 前缀。
- [BGP 是怎么工作的？Prefix、AS_PATH 和路由策略基础](https://www.sknk.eu/zh/blog/bgp-basics): 用网络运营视角解释 BGP 如何交换 Prefix、Origin ASN、AS_PATH 与 Next Hop，路由器如何按策略选路，以及为什么 Session 正常不等于路由正确。
- [IPv6 /48 怎么划分？/64、/56、/127 与 VLAN 地址规划](https://www.sknk.eu/zh/blog/ipv6-subnetting-explained): 从一个 IPv6 /48 出发，说明如何按地区、环境和业务划分 /64，/56 适合什么场景，点对点链路何时使用 /127，以及如何避免后期重编址。
- [Transit、Peering、IXP 和 Tunnel 有什么区别？](https://www.sknk.eu/zh/blog/transit-vs-peering): 解释 Internet Transit、公开与私有 Peering、IXP、Route Server 和 Tunnel 的作用、可达范围、费用与适用场景，帮助自建网络选择上游。
- [拿到 ASN 之后怎么上线？从资源登记到 BGP 可见的完整清单](https://www.sknk.eu/zh/blog/what-happens-after-you-get-an-asn): ASN 获批只是开始。本文按实际顺序说明如何确认资源、准备上游、配置 IRR 与 ROA、建立 BGP Session、发布前缀并验证公网可达性。
- [什么是 IRR Route Object？route、route6、RPKI 和 ROA 怎么配合](https://www.sknk.eu/zh/blog/what-is-an-irr-route-object): 解释 IRR、RPSL、route、route6、aut-num 与 AS-SET 的作用，以及 IRR 和 RPKI 为什么不能互相替代，如何避免上游过滤错误。
- [什么是 Multihoming？申请 ASN 前为什么要确认多上游](https://www.sknk.eu/zh/blog/what-is-multihoming): 解释 Multihoming 如何通过多个外部网络提高韧性，RIPE ASN 申请为什么要求独立路由策略，以及双线路、双 Transit 和实际故障隔离的区别。
- [提交 ASN 申请前，需要确认的 12 个问题](https://www.sknk.eu/zh/blog/asn-application-checklist): 一份面向网络负责人和采购人员的 ASN 申请前检查清单，覆盖申请资格、上游 BGP、IPv6 属性、费用、ROA、合同、退出流程和上线责任。
- [ASN 一年多少钱？申请费、Sponsorship 和隐藏成本一次算清](https://www.sknk.eu/zh/blog/asn-cost): ASN 本身不是可以买下的商品。本文拆解 RIPE NCC 直接会员、Sponsoring LIR、IPv6、BGP Transit、设备和运维成本，帮助网络团队做完整预算。
- [如何选择 Sponsoring LIR？别只比较年费](https://www.sknk.eu/zh/blog/how-to-choose-a-sponsoring-lir): 选择 ASN Sponsoring LIR 时，应比较资质、资源属性、申请能力、ROA 权限、退出流程、服务边界和真实总成本，而不是只看首页报价。
- [IPv6 /48 怎么选？PA、PI 和运营商地址的区别](https://www.sknk.eu/zh/blog/how-to-get-an-ipv6-48): IPv6 /48 并不只有一种来源。本文比较运营商分配、Sponsoring LIR 的 PA 地址和 IPv6 PI 地址，说明 BGP 宣告、RPKI、可携带性和重新编号风险。
- [如何申请自己的 ASN？条件、材料和完整流程](https://www.sknk.eu/zh/blog/how-to-get-your-own-asn): 面向中国公司和网络团队的 ASN 申请指南：判断是否需要 ASN、选择 RIR 或 Sponsoring LIR、准备网络理由和主体材料，以及获批后的 BGP、RPKI 和 IRR 工作。
- [什么是 ROA？Prefix、Origin ASN 和 maxLength 怎么填](https://www.sknk.eu/zh/blog/what-is-a-roa): ROA 用于授权某个 ASN 宣告指定 IP 前缀。本文通过 IPv4、IPv6 和多 Origin 场景解释 Prefix、Origin ASN、maxLength、Invalid 路由及上线检查方法。
- [什么是 ASN？从网络身份到 BGP 路由，一篇讲明白](https://www.sknk.eu/zh/blog/what-is-an-asn): ASN 是自治系统在互联网中的唯一编号。本文用网络运营场景解释 ASN、IP 地址、BGP、公共 ASN 与私有 ASN 的区别，以及什么情况下需要申请自己的 ASN。
- [什么是 RPKI？它如何降低错误路由和劫持风险](https://www.sknk.eu/zh/blog/what-is-rpki): RPKI 为 IP 前缀和起源 ASN 建立可验证的授权关系。本文解释 ROA、ROV、Valid、Invalid、NotFound，以及 RPKI 能做什么、不能做什么。

## Frequently asked questions

### 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?

Possibly. Registration outside Europe does not by itself guarantee eligibility. The applicant must demonstrate a qualifying network need connected to the RIPE NCC service region and pass RIPE NCC's individual review, due diligence, and applicable sanctions checks. 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.

## Policies and machine-readable resources

- [Terms of service](https://www.sknk.eu/terms)
- [Privacy policy](https://www.sknk.eu/privacy)
- [Acceptable use policy](https://www.sknk.eu/acceptable-use)
- [Support policy](https://www.sknk.eu/support)
- [XML sitemap](https://www.sknk.eu/sitemap.xml): Complete list of indexable pages.
- [English Atom feed](https://www.sknk.eu/feed.xml): Recent English blog articles.
- [中文 Atom feed](https://www.sknk.eu/zh/feed.xml): 最新中文技术文章。
- [robots.txt](https://www.sknk.eu/robots.txt): Crawler directives.