Shikanoko Networks (SKNK)

Before you order

Before You Apply for a RIPE ASN

Do not start with the order form. First make sure your network has a real need for an independent ASN: an external routing policy of its own and two genuine BGP relationships—live or credibly planned—that you can explain. Then prepare the company documents and RPSL.

Check my application readiness

This page helps you find obvious gaps. It is not a RIPE NCC decision and it does not replace identity, ownership, or sanctions checks.

Four things RIPE needs to understand

RIPE is looking for a network that genuinely needs an independent external routing policy—not a company that simply wants an ASN. Be ready to explain these four things before you order.

01

Independent external routing policy

A new ASN is for a new external routing policy that an existing ASN cannot meet.

Prepare

Keep it concrete. Say what you need to decide yourself: for example, multi-site failover, announcing prefixes to different neighbours, or different policy for real commercial and technical relationships.

02

Multihomed network

The network must be multihomed to qualify for an ASN.

Prepare

Explain how the same network will use two external BGP relationships. Do not split one relationship into two entries or describe an unarranged future relationship as live.

03

Two verifiable BGP neighbours

At least two peering partners' ASNs and contact details, including email, must be provided.

Prepare

For each neighbour, give a location, the peer ASN, a working NOC or technical email, and one sentence saying whether it is transit or relevant peering.

04

A real RPSL policy

The new ASN's routing policy must be provided in RPSL.

Prepare

For every neighbour, state import (what you accept) and export (what you announce). The policy must describe the actual plan, not a copied template.

Documents to have ready

Start with the evidence that proves the applicant, the contacts, and the network use. We ask for anything else only when the case needs it. Do not upload sensitive files on this public page.

Required by Shikanoko Networks

Who is applying

A company registration document or equivalent registered-sole-trader evidence. The legal name, registration number, and registered address must match the application.

Required by Shikanoko Networks

Who can sign and answer questions

An authorised signatory, administrative and technical contacts, and a working email address. We may ask for evidence of signing authority where needed.

Provided if requested

How the network will use the resources

A short explanation of where the network runs, why it needs an independent policy, and how the two neighbours connect to it.

Set up after ordering, during review

RIPE Database records

After placing your order, while the RIPE NCC application is under review, customers create and control their own RIPE NCC Access account plus organisation, role/person, and maintainer objects.

Read the RIPE NCC setup guide

Your two BGP neighbours

The order form asks for two BGP neighbours. They can be transit or peering that is genuinely relevant to your network. What matters is that the relationship is real, contactable, and consistent with the RPSL policy.

01

Where it connects

The planned datacentre, cloud region, or network location—ideally a named facility and city.

02

Which network it is

The ASN of the real external operator. Do not use your own ASN or a placeholder.

03

How to reach them

A working NOC or technical email that can confirm the relationship. A generic sales inbox is usually not enough for BGP context.

Put the real relationship into RPSL

import is what you accept from a neighbour; export is what you announce to it. The example shows the smallest two-neighbour structure with documentation ASNs. It is not a ready-made configuration.

RPSLAS64496 / AS64497 / AS64498
aut-num:        AS64496
as-name:        EXAMPLE-NET

import:         from AS64497 accept ANY
export:         to AS64497 announce AS64496

import:         from AS64498 accept ANY
export:         to AS64498 announce AS64496

Note: The example shows syntax and relationship only. Before applying, replace the ASNs, filters, and announcement objects with the real policy. RPSL is not router configuration and does not replace an upstream's enablement or filters.

This is usually a good fit

  • A hosting, cloud, or enterprise network using two real external BGP relationships for failover or traffic engineering.
  • A network that needs its own ASN to express different policy to transit providers or relevant peers.
  • A network with identifiable infrastructure, a real prefix-use plan, and people ready to operate BGP.

This is usually not enough on its own

  • One provider connection with no real second BGP relationship or multihoming plan.
  • Wanting an ASN for ownership, marketing, IP reputation, or broad compliance claims without an independent routing need.
  • A private-only network, private VLAN, or a case a private ASN can handle.
  • A plan that cannot say who will accept BGP, which prefixes will be announced, or when the relationship will exist.

Outside the RIPE NCC service region? Show the network connection

This is not a universal RIPE ASN rule. But if the applicant entity or individual's main base is outside the service region, we strongly recommend evidence that the network is deployed—or will be deployed—inside it.

  • Service evidence: a customer-BGP-capable VPS, dedicated server, cloud-network service, colocation rack, port, or cross-connect.
  • Linkage: the provider, city, service type, and the applicant or a verifiable account connection.
  • Continuity: at least three months of service remaining from submission. Use a contract, renewal commitment, or evidence that the service remains valid.

Practical note: A bill can show only a past billing period. A valid contract or renewal commitment plus a recent bill gives a clearer picture of an ongoing network connection. Submit this only through the secure application flow when requested.

Sanctions: do not apply if a sanctioned party benefits, owns, or controls

Do not apply if the applicant, beneficiary, or controlling party is subject to applicable sanctions.

What usually holds an application up

  1. 1

    The company name, address, signatory, and documents do not match.

  2. 2

    One or both BGP neighbours lack an ASN, location, or working NOC email—or they are not two real external relationships.

  3. 3

    The stated use says only 'we need BGP' and never explains the routing policy, announcement plan, or deployment.

  4. 4

    The RPSL import/export lines are unclear or conflict with the neighbours and stated use.

  5. 5

    An outside-region case does not show a real network connection to the RIPE NCC service region.

  6. 6

    Sanctions, ownership, or authority information leaves a potential match unresolved.

Before you order

Check the basics

Answers stay in this browser. This page does not upload company, billing, identity, or sanctions-screening material.

Basics0 / 6
Check each statement you can stand behind
Where is the applicant based?

Answer for the applicant entity's incorporation or an individual's main base. Outside-region applicants can continue, but should prepare evidence of a real in-region deployment.

Check the RIPE NCC service region first

Use this only to choose “in-region” or “outside-region”. The current RIPE NCC map and country/RIR list remain the reference.

Entity outside, network inside? Select “outside-region”, then prepare the in-region deployment evidence.

Open the RIPE NCC official service-region map
Sanctions declaration

This declaration does not replace Shikanoko Networks' screening against EU, UK, and other applicable sanctions sources.

A positive result means only that you checked the basics on this page. It is not RIPE NCC approval and does not bypass Shikanoko Networks' document, identity, ownership, or sanctions screening.

Answer the questions to see the next step.

Frequently asked questions

Do I need two upstream providers?

Not necessarily. The important point is two external BGP relationships and multihoming. They may be transit or relevant peering; describe the actual design.

Can I apply with one VPS?

Usually not on the strength of one VPS alone. First confirm a real second BGP relationship and who will accept your announcement, then assess whether you are ready.

Does Shikanoko Networks provide upstreams or configure BGP?

No. Shikanoko Networks provides LIR sponsorship, ASN and IPv6 PA /48 application administration, and PA-prefix ROA administration. Customers choose upstreams and operate their own BGP.

Can the IPv6 /48 move to another sponsor?

SKNK provides an IPv6 PA /48 from its LIR address space. It is not PI and does not move with an ASN sponsorship relationship; ending the service normally requires withdrawal and renumbering.

Does a Ready result mean that RIPE NCC will approve me?

No. The tool only finds common gaps. Final eligibility, due diligence, and RIPE NCC review are all case-specific.

If you can explain it clearly, you can apply

First confirm that the upstream or peering relationships exist, or are genuinely arranged. Then use the secure order flow to submit the applicant evidence.

Start ASN + IPv6 application

What we do, and what you do

Keeping the application separate from network operations makes the process clearer.

  • Shikanoko Networks: LIR sponsorship, ASN and IPv6 PA /48 application administration, and PA-prefix ROA management.
  • Customer: upstream and peer relationships, BGP configuration and operations, IRR, DNS, and actual route reachability.
  • ASN, IPv6, route propagation, approval, and delivery time are not guaranteed. Every application is subject to policy and individual review.

Sources

This guide is based on the public sources below. We review it when policies or list sources change.