One checklist for the full application
What Do You Need to Apply for a RIPE ASN?
Enter applicant, contact, peer and RIPE technical details in the same order form, then upload evidence. Review the terms and tax-inclusive price, pay, and complete both signatures before SKNK prepares the application.
SKNK prepares and submits the request. RIPE NCC reviews each case independently, so complete documents do not guarantee approval or a delivery date.
Prepare these 6 groups of information
Work through the list once. Case-specific items may not be uploaded with the first order, but you must be able to provide them when requested.
Applicant evidence
What to prepare
A company provides a registration certificate or equivalent legal document. An individual provides a valid Passport or National ID card. Names and addresses must match the application.
When it is used
Upload with the order
Applicant details
What to prepare
Applicant type, legal name, country of registration, registration number, and registered address. Individuals do not need company registration details.
When it is used
Enter on the order form
Contact details
What to prepare
Authorised signatory's full name, job title, email address, telephone country code, and number. We may ask for proof of signing authority.
When it is used
Enter on the order form
Two BGP neighbours
What to prepare
For each neighbour: connection location, peer ASN, and a working NOC or technical email. They must be two genuine, independent external BGP relationships.
When it is used
Enter on the order form
Network use and routing policy
What to prepare
Explain where the ASN will be used, why you need an independent policy, what prefix you plan to announce, how both neighbours connect, and the matching RPSL import/export policy.
When it is used
Enter on the order form
In-region deployment evidence
What to prepare
If the applicant is outside the RIPE NCC service region, prepare evidence of an in-region active network element, such as IP Transit, a BGP session, colocation, or a BGP-enabled server.
When it is used
Case-specific
From order to RIPE application: follow these 3 steps
All order details are completed on one page. After payment and both signatures, SKNK uses the saved information to prepare and submit the RIPE NCC application.
Enter the application details
Enter applicant, contact, peer and RIPE technical details, then upload PDF evidence in one order form.
- Choose individual, company, organisation or sole trader and enter the matching legal and registration details.
- Enter the authorised contact's name, job title, email, and phone number.
- Enter two peers with their ASNs, interconnection locations and NOC emails.
- Enter the RIPE technical identifiers and network plan in the same order form.
- Enter actual service-use and billing locations; the same address only needs to be entered once.
- Upload applicant evidence as a PDF, up to 10 MB. The file is saved with this application.
- Describe the service use and complete the security check. Review the complete terms and your application in the next step.
Pay, then both parties sign
Review complete terms and the final tax-inclusive price before payment. An English agreement is then generated for both parties to sign.
- Check the applicant name, address, signatory, and contact details in the agreement.
- Pay €89/year through Stripe; VAT is added where applicable.
- After payment, the customer and company sign through DocuSeal. The agreement forms when both parties have signed.
- Follow signing progress in your order; complete signed documents and audit records become available after archiving.
Current sequence: complete all details and upload → accept terms and confirm the final price → Stripe payment → both parties sign → SKNK prepares the application and RIPE NCC reviews it.
SKNK prepares the application while RIPE NCC reviews it
After both parties sign, SKNK uses the saved order details to prepare ASN + IPv6 /48. RIPE NCC reviews each case independently.
- Follow payment, signing, review and delivery status in your order.
- SKNK checks the RIPE technical details saved with the order.
- RIPE NCC independently decides whether to approve the ASN.
- SKNK emails you when review and delivery are complete.
RIPE Database setup and order details
Complete steps 1–6 in the RIPE NCC registration guide, then enter the identifiers below in the RIPE technical details section of the same order form; these details are saved with the applicant, peer and evidence information.
- 01Organisation ID, for example ORG-XXXX-RIPE
- 02Your Maintainer name (mnt-by)
- 03admin-c handle
- 04tech-c handle
- 05abuse-c handle for a role with abuse-mailbox
- 06Your preferred AS name (as-name), for example YOURCOMPANY-AS
- 07Confirmation that the organisation contains mnt-ref: lir-uk-shikanoko-1-MNT
Do not send a RIPE NCC password, SSO login, API key, or maintainer credentials. We need only the object names and handles listed above.
The network must also meet these conditions
Applicant evidence establishes identity. ASN eligibility also depends on a genuine need for an independent external routing policy.
Independent external routing policy
Current RIPE policy requires the new ASN to have its own external routing policy.
State what you need to control: multi-site failover, prefix announcements to different neighbours, or different policy for real transit and peering relationships.
Multihomed network
Current RIPE policy requires the network to be multihomed.
Explain how the same network uses two external BGP relationships. Do not split one relationship into two entries or describe an unarranged relationship as live.
Two verifiable neighbours
The request must identify the external BGP neighbours.
For each one, provide a specific location, peer ASN, working NOC/technical email, and whether it is transit or relevant peering.
RPSL that matches the plan
The request must include the routing policy in RPSL.
Write an import and export rule for each neighbour. Use examples only for syntax; never submit documentation ASNs as your real plan.
How to describe the two BGP neighbours
Answer three questions for each neighbour. Example: Equinix AM5, Amsterdam; AS1299 (Arelion); and a NOC address that can verify the relationship.
Where does it connect?
Give the facility, cloud region, or city. Europe, Asia, or Cloud alone is not specific enough.
Which network is it?
Give the real operator and ASN, and say whether it is transit or relevant peering.
Who can verify it?
Provide a working NOC or technical email that can verify the relationship in the RIPE technical details section of the order form.
Use the RPSL example only to understand the format
Import states what you accept from a neighbour. Export states what you announce to it.
aut-num: ASNEW
as-name: EXAMPLE-NET
import: from AS64497 accept ANY
export: to AS64497 announce ASNEW
import: from AS64498 accept ANY
export: to AS64498 announce ASNEWNote: AS64497 and AS64498 are documentation ASNs; ASNEW is the RIPE request placeholder. Replace the neighbour ASNs, filters, and announcement objects with the real policy, and do not manually replace ASNEW with a specific number.
Five common reasons we ask for more information
- 1
The company name, address, signatory, and evidence do not match.
- 2
A BGP neighbour is missing an ASN, connection location, or working NOC email.
- 3
The two neighbour entries describe the same external relationship.
- 4
The network purpose says only “we need BGP” and gives no deployment or announcement plan.
- 5
An outside-region applicant has no evidence of real network deployment in the RIPE service region.
Applicant outside the RIPE region? Prepare in-region evidence
The ASN must be used on an active network element inside the RIPE NCC service region. Identify the deployment location, provider, connection type, and service period.
- Suitable evidence may include an IP Transit agreement, BGP session or connectivity agreement, colocation contract, BGP-enabled dedicated server, or similar deployment material.
- The material should ideally identify the provider, peer ASN, city or facility, service type, applicant or verifiable account, and service period.
A BGP VPS can be relevant if the service explicitly includes a BGP session, permits announcements with your ASN, and shows the location and service period. Keep the service valid for at least three months from submission; a current agreement or renewal commitment plus a recent invoice is stronger than an old invoice alone.
Ownership and sanctions information must be accurate
Do not place an order if the applicant, beneficiary, or controlling party is subject to applicable sanctions. Contact us first if a similar name or ownership relationship remains unclear.
Before you order
Check before ordering
Tick off the documents and network conditions. Answers stay in this browser and no files are uploaded here.
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.
Questions customers ask most often
Do I need two upstream providers?
Current RIPE policy requires multihoming. You need two genuine external BGP relationships. They may be transit or peering that is genuinely relevant to your network, but one relationship cannot be split into two entries.
Can I apply with one VPS?
An ordinary VPS does not usually prove multihoming or an independent routing policy. A BGP VPS that supports your own ASN, provides a BGP session, and identifies the location and service period can support one relationship or in-region deployment. You still need a genuine second relationship.
What should a company or individual upload?
A company uploads a registration certificate or equivalent legal document. An individual uploads a valid Passport or National ID card. The order form accepts PDF files up to 10 MB.
Will SKNK register my RIPE account or keep my password?
No. You create and control your RIPE NCC Access account, organisation, contacts, and maintainer. SKNK needs only the object names and handles, never a password, SSO login, API key, or maintainer credential.
Does Shikanoko Networks provide upstreams or configure BGP?
The standard service does not include upstream selection or customer-side BGP configuration. SKNK handles Sponsoring LIR preparation and submission, plus resource-side records, the matching IRR route/route6 object, and the ROA for the SKNK IPv6 PA /48. AS-SET follows the actual filtering need and maintainer authority; the customer operates the network.
Does passing the checklist guarantee approval?
No. The checklist covers common requirements. SKNK still reviews documents, identity, ownership, and sanctions information, while RIPE NCC makes the final case-specific decision.
Ready? Submit the application online
Complete the RIPE Database setup first, then enter the Organisation, Maintainer, contact handles, as-name and two peer details in one order form. After payment and signing, SKNK uses the saved details to prepare the application.
Start the ASN + IPv6 applicationWho handles each part
Application administration and network operations are separate responsibilities.
- SKNK: Sponsoring LIR application preparation and submission, resource-side records for the SKNK IPv6 PA /48, and its PA ROA.
- Customer: RIPE NCC Access, organisation, contacts, and maintainer; upstream relationships, BGP configuration, and day-to-day operation.
- RIPE NCC: independent review and the final ASN assignment decision.
Official references
This page combines the public sources below with the current SKNK order flow.