RIPE NCC LIR sponsorship
A clear view of the application process, what you receive, and where SKNK's responsibilities end and yours begin.
Provide your applicant, service-use, billing, peer, and RIPE application details and upload the required evidence before moving on. Review the full terms and final tax-inclusive price.
Pay the confirmed amount through Stripe after all required information has been entered. The order and uploaded materials are saved together.
After payment, sign the complete English agreement with SKNK through DocuSeal. Once both signatures and the audit record are archived, SKNK handles review and RIPE NCC submission; follow progress through your private status link.
Confirm before ordering
The standard service covers the published route/route6 and PA-prefix ROA responsibilities for the covered standard product. Registry records, technical changes, and support can be added through a written Order.
RIPE NCC operates the database. Customers maintain their own Access, organisation, contact, and maintainer records; SKNK provides setup guidance, handles the sponsoring-LIR side of the application and resource-registration coordination, and maintains the covered prefix's route/route6 object.
SKNK prepares, submits, and follows up on the application. RIPE NCC independently decides under its policies whether to make the assignment, which is made to the approved End User.
The standard service includes creating and continuously maintaining the covered prefix's IRR route/route6 object. AS-SET follows the actual filtering need and available maintainer authority; IRR work for other resources follows each resource's scope.
Customers choose upstreams, configure and operate BGP, and announce the prefix with the authorized origin ASN. SKNK does not provide BGP configuration, transit, or managed routing.
For a PA /48 from SKNK's LIR address space, SKNK controls RPKI authority and creates, maintains, or withdraws the ROA. Contact SKNK before changing the intended origin ASN; customers cannot modify this ROA themselves in the RIPE Portal.
Reverse DNS, Geofeed, location records, Anycast, multiple origins, technical changes, implementation coordination, and support can be agreed for the applicable resource and operating model.
Tell us the upstream's IRR source, exact-match, and Origin ASN requirements before the route is announced. We will confirm the covered prefix, resource authorization, and any custom registry, technical-change, or support scope in the Order.
